| MBinder_WMF | |
| Feb 11 2020, 8:08 PM |
| F31608702: Screen Shot 2020-02-11 at 12.03.02 PM.png | |
| Feb 11 2020, 8:08 PM |
| F31608701: Screen Shot 2020-02-11 at 12.02.49 PM.png | |
| Feb 11 2020, 8:08 PM |
| F31608706: Screen Shot 2020-02-11 at 12.06.47 PM.png | |
| Feb 11 2020, 8:08 PM |
Steps to Reproduce:
Actual Results:
Expected Results:
More like
I was unable to reproduce this more than once.
Environment:
Cannot confirm that problem with Firefox 72.0.2 on Fedora 31 - works as expected.
Does the problem still happen if you start Firefox in Safe Mode? (Safe Mode disables add-ons, extensions and themes, hardware acceleration and some JavaScript stuff in order to exclude some possible reasons for problems.) See https://support.mozilla.org/en-US/kb/troubleshoot-firefox-issues-using-safe-mode
I can't even reproduce it in the same environment, much less safe mode. Might have been a one-time blip, something didn't load in some extension and caused it. In any case, if it can't be reproduced, it might not be worth investigating. It was just messy enough the one time that I thought it was worth documenting.
Could not reproduce the error on Firefox 72.0.2 using MacBook Pro Mac OS 10.15.3 either. I suspect it might be a one-time issue that occurred from a browser extension loading incorrectly (as you suggested) or a brief issue with your internet connection.
I'm cool with closing this task, and leave that with whomever triages. We can re-open, as needed. :)