Export Error on Microsoft Edge.

[ZJU-Cindy1025]

I'm using plotly==7.0.0 kaleido==1.4.0 choreographer==1.3.0 on Windows 10. And the Chromium Browser is Microsoft Edge. I have tried the codes below to export an image:

import plotly.express as px

fig=px.bar(x=["a", "b", "c"], y=[1, 3, 2])
fig.show()
fig.write_image("fig.png")

The graph can be displayed correctly. However, when exporting the image, the log shows that Wait expired, Browser is being closed by watchdog. and an error occurred as below.

(traceback omitted)
choreographer.browsers._errors.BrowserFailedError: ('The browser seemed to close immediately after starting.', 'You can set the `logging.Logger` level lower to see more output.', 'You may try installing a known working copy of Chrome by running ', '`$ choreo_get_chrome`.It may be your browser auto-updated and will now work upon restart. The browser we tried to start is located at C:\\Program Files (x86)\\Microsoft\\Edge\\Application\\msedge.exe.')

Meanwhile, I have tried the minimal test for choreographer==1.3.0 as code below:

import asyncio
import choreographer as choreo

async def example():
    browser = await choreo.Browser(headless=False)
    await asyncio.sleep(3)

if __name__ == "__main__":
    asyncio.run(example())

The error is the same as above.

Wait expired, Browser is being closed by watchdog.
(traceback omitted)
choreographer.browsers._errors.BrowserFailedError: ('The browser seemed to close immediately after starting.', 'You can set the `logging.Logger` level lower to see more output.', 'You may try installing a known working copy of Chrome by running ', '`$ choreo_get_chrome`.It may be your browser auto-updated and will now work upon restart. The browser we tried to start is located at C:\\Program Files (x86)\\Microsoft\\Edge\\Application\\msedge.exe.')

It can be seen that choreographer causes the error, not plotly or kaleido. Choreographer is not suitable for Microsoft Edge.

Edge Version: 152.0.4191.66.

[robertclaus]

Thank you for reporting this. We're not sure when we would get to this. A workaround for this would likely be installing Chrome separately if possible.