"Underline Links" Doesn't
Categories
(Firefox :: Settings UI, defect)
Tracking
()
People
(Reporter: erwinm, Unassigned)
Details
Attachments
(2 files)
Steps to reproduce:
Firefox preferences include an option to "Underline Links."
Actual results:
This option does not work. I've tried with "Always" and "Never" override page colors, and it doesn't apply either way.
Expected results:
This should work. Unless users pick contrasting lnk and text colors, and always override site colors, it can be hard to diustinguish these without the underline.
Mozregression doesn't work with older versions, but this has been broken since at least 2016.
Comment 1•2 years ago
|
||
Could you please provide some of the websites you noticed this issue on?
For example using mozilla.org websites I noticed that all the links are underlined.
Thanks.
Yes. All websites. I've attached screenshots to show this in my current profile, and using Mozregression without specifying my profile.
As it is, the only way to see which text is a link is to use a contrasting color, and always override site colors. Which often hides other parts of the site.
Comment 5•2 years ago
|
||
Firefox preferences include an option to "Underline Links."
Please (always) provide clear steps where to find this, so it's more likely that everyone talks about the same thing.
Open about:preferences.
Search "colors",
Click on "manage colors."
Check whether "underline links" is checked. If not, check it.
P.S. I understand that the default setting is to only underline links on mouseover.
But mousing around worsens rsi, and since many sites have added elements which flash or animate on mouseover, it triggers migraines and risks seizures.
And Firefox doesn't underline then, either.
"Underline Links" should underline them, and without requiring mouseover/
Comment 8•2 years ago
|
||
The Bugbug bot thinks this bug should belong to the 'Firefox::Settings UI' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.
Comment 9•2 years ago
|
||
Duping this to bug 1664278. We can continue the conversation over there, particularly about potential accessibility needs and existing workarounds.
Description
•