I noticed that my dash app was rendering poorly, but after doing cross browser testing (using Chrome and IE) , I noticed that this is only isolated to firefox. In the gif below, firefox is on left and chrome is on right. You can notice that when I switch the state to "Alabama" one of the graphs get stuck in an awkward transition and those that are stuck are still showing old data. This varies between selections sometimes being more than one graph/bar that is affected.

You can play around with my test tool which is up on heroku, albeit it is on a free tier so it will require some bootup if it went to sleep: https://pay-rate-rangefinder-demo.herokuapp.com/
Interesting, I see that issue as well. I also notice that if I hover over some of the bars, the shaded regions in the bar chart will disappear

I've never seen this before though, I wonder if it's another issue related to Firefox 64.0 (we've seen a few in the last couple of days)
This example is using plotly.js 1.43.1
@mbkupfer Could you please tell us which version of FF you're using. Thank you.
@etpinard
Firefox 64.0 (64-bit)
Wow. Another FF64 + mac bug. :rage:
I'm actually seeing this on my windows and ubuntu machines so I wouldn't say this is specific to macs.
Ok. If someone would like to help, the next step would be to put to together a minimal codepen displaying this bug. Thanks!
This example: https://codepen.io/etpinard/pen/pbxkNb I found in plotly's documentation demonstrates this rendering issue. It's also on a line graph so it shows that this could be a broader issue and not just for bar charts.

Yikes. That's bad. I'm not sure what we can do here.
The next step would be to see if a similar bug has been filed on:
Not sure if a bug has been found/filed at: https://bugzilla.mozilla.org/buglist.cgi?quicksearch=svg
If not, then I'm happy to take the lead on this. Let me know.
@mbkupfer thanks for the reply!
I haven't been able to find a similar report on bugzilla, but I only searched for a few minutes.
If you're willing to make a reproducible example for the FF team, yes please, go for it! Thank you very much!
@etpinard: this filed bug looks very similar: https://bugzilla.mozilla.org/show_bug.cgi?id=1517458
Looks like there has been recent activity as well, but I'm not to savvy with bugzilla conventions so the last comment is greek to me.
Thanks very much @mbkupfer - that indeed looks like the same problem.
Looks like this was fixed! Should be making it into FF66. Based on their wiki this should be released 19 March 2019.
The beta will be out 29 Jan 2019 so we can start testing around then, unless you want to build the nightly build yourself. I've done this before and it takes a looong time to setup the entire environment so might just wait till Beta is released.
Fixed in FireFox 65 & 66.
Closing.
Most helpful comment
Looks like this was fixed! Should be making it into FF66. Based on their wiki this should be released 19 March 2019.
The beta will be out 29 Jan 2019 so we can start testing around then, unless you want to build the nightly build yourself. I've done this before and it takes a looong time to setup the entire environment so might just wait till Beta is released.