the version 91.0.1 for imac is having troubles with the appearance
Categories
(Core :: Layout, defect)
Tracking
()
People
(Reporter: andiecallejasr, Unassigned)
Details
Attachments
(1 file)
1002.14 KB,
image/png
|
Details |
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:91.0) Gecko/20100101 Firefox/91.0
Steps to reproduce:
My browser is set to update automatically. Last week, I think tuesday or friday I opened the browser as usually and everything was looking weird. The themes weren't working, and the browser looked like it was made in the 80's. I tried deleting all the add-ons, cookies and preferences, getting it back to the default configuration and I even deleted everything related to Firefox, restart my iMac and installed everything again from scratch. I even check if it was something with the configuration of mi iOS or some accessibility feature, but everything is the same as before the update.
Actual results:
Nothing happened, the browser still looks ugly, its hard to use like this because there's a lot of black lines, black boxes everywhere, the links look weird, the pages aren't loading like they should so I'm using safari and chrome now.
Expected results:
Firefox should look like it did before the 91.0.1 update. I'm attaching screenshots of the issues I'm describing, hopefully you can tell me how to fix it so I can continue to use your awesome browser.
Comment 1•3 years ago
|
||
The Bugbug bot thinks this bug should belong to the 'Toolkit::Application Update' component, and is moving the bug to that component. Please revert this change in case you think the bot is wrong.
Comment 2•3 years ago
|
||
Sorry this went untouched for so long. I don't think this is an Application Update bug. I'll try to find a better component for it.
Comment 3•3 years ago
|
||
This is because you had the "increase contrast" setting on your OS and we tried to honor it. However it can cause confusion if you're not aware of the Firefox "Color" settings so we made back "don't honor high contrast themes" the default in bug 1726606.
Description
•