Plotly Express not rendering in Firefox but fine in Safari

[Geophph]

Using a basic example of plotly express i see no output in firefox but is fine in Safari. Any ideas why this may occur?

import plotly.express as px
import pandas as pd

# Create a sample dataframe
df = pd.DataFrame({
'x': range(10),
'y': [2, 3, 5, 7, 11, 13, 17, 19, 23, 29]
})

# Create a scatter plot
fig = px.scatter(df, x='x', y='y', title='Sample Scatter Plot')

fig.show(renderer='databricks')

[parthSundarka]

Hi @Geophph ,

I tried to reproduce this quickly on Firefox and it seems to be working for me. I used a serverless compute and I am on Firefox version 134.0 (aarch64)

Could you check if updating the Firefox version resolves your issue? If the browser version is up to date, Could you share more details about the compute type being used here, which may be causing the issue?

[Geophph]

Thanks for the quick response! I am on the same version of firefox as you. The compute is a cluster on 13.3 runtime - what other details might be relevant?

[Geophph]

I guess maybe this is a Firefox / Mac (M2) issue for me. If I take the window and drag from my laptop to external monitor, it forces some sort of redraw in the browser and the graph appears. Conversely, if I start the plot on my external (no graph shows) then drag to the laptop it also triggers a re-render of sorts and the graph then appears. So i'm not sure it's related to compute, but also unclear to me how to fix.

[parthSundarka · Accepted solution]

I can confirm that this re-rendering does happen. Initially, it is a black screen, but resizing the browser window renders the graph properly. I initially thought it was blank because of the window size and did not think of the re-render scenario. It happens with almost every graph type in Plotly, too.

Further, I tried it in the non-databricks environment on Firefox, and it seemed to be working. If you are looking for a fix for Firefox without having to resize, I suggest reaching out to Databricks Support so that they can reach out to the Engineering team and check on getting a fix for this as this is reproducible in all DBR versions.

The current Workaround would be to resize the window once the workflow is run to see the visualisation.

Do let me know if you have any queries. If not, can we mark this as an accepted solution?

[Geophph]

I will do so! Thanks for your help in looking into this!