I can't help but have a sinking feeling that this as a result of the wider trend of using only Chromium-based browsers. If they were the ones affected by this issue, I feel like it would get solved almost immediately.
Hell, probably wouldn't have even made it to production.
I assumed they had done something that botched the JavaScript of the site. Maybe some update went badly today, and it manifests differently in Firefox and Chrome?
Anyway, whatever it was either they didn’t test well in Chrome either, or they don’t use the fancy editor themselves.
Good to know. This new editor doesn't work at all for me in Firefox, just a frustrating chaos of random bugs.