[Win] Duckduckgo search bar is not properly displayed when using High Contrast Theme
Categories
(Firefox :: Theme, defect)
Tracking
()
Accessibility Severity | s3 |
People
(Reporter: rpopovici, Unassigned)
Details
(Keywords: access)
Attachments
(2 files)
[Affected versions]:
Firefox 96.0a1 (2021-11-23) (64-bit)
[Affected platforms]:
Windows 10 x64
[Steps to reproduce]:
- Set High Contrast White (Right-click -> Personalize -> Colors -> High Contrast Settings).
- Launch Firefox with a new profile.
- Make sure that option "System theme" is enabled on Add-ons and themes
- Add Duckduckgo addon on Firefox
- Type something in awesome bar and click Enter.
[Expected result]:
Duckduckgo search bar is properly displayed.
[Actual result]:
Duckduckgo search bar is NOT properly displayed. Please see attachment
this may or not additional info. but since 94.0.2 update, The duckduckgo privacy add-on has been entirely removed from my browser, all default search engines are back, after i disabled them (or so called removed) defaulted to google.
This is MAJOR. Removing privacy aware add-on is one huge thing, but restoring all the tracking search engines is another. I'll be filing my own bug report, but as of first apperances and experiences, this seems a wilful action.
(In reply to Rob N from comment #2)
this may or not additional info. but since 94.0.2 update, The duckduckgo privacy add-on has been entirely removed from my browser, all default search engines are back, after i disabled them (or so called removed) defaulted to google.
This is MAJOR. Removing privacy aware add-on is one huge thing, but restoring all the tracking search engines is another. I'll be filing my own bug report, but as of first apperances and experiences, this seems a wilful action.
I don't have permission to edit or remove my comments. Can somebody remove the text:
"The duckduckgo privacy add-on has been entirely removed from my browser."
"Removing privacy aware add-on is one huge thing, but restoring all the tracking search engines is another. I'll be filing my own bug report, but as of first apperances and experiences, this seems a wilful action.
and replace it with:
"restoring all the removed search engines is something else. and defaulting to google search is very very naughty. "
Comment 5•3 years ago
|
||
Hi Rob, thanks for this report.
EDIT: Originally thought this was a webcompat issue, now I'm not so sure... I can't find any glaring style differences between edge and ff, except our box models are slightly different:
In firefox, the form element has a 0.8px border with a 42.4px height. In edge, the form element has a 1px border with a 42px height.
In both browsers, the style rules say "border:1px;" and "height:42px", so I'm not sure why firefox gets different numbers.
Might also be a red herring 🤷♀️
:emilio could you take a look at this?
Updated•3 years ago
|
Updated•3 years ago
|
Updated•3 years ago
|
Comment 6•3 years ago
|
||
This is not a layout issue. They have a taller input than the container, and for we're painting a background even though they specify background: none
, because background-color: revert
goes back to the UA sheet and chooses the field
background-color.
We revert
for background-color: transparent
, see this comment for context.
So I guess we should figure out how does Edge behave for test-cases like bug 1625036, and consider changing this, but otherwise this is by design to prevent contrast issues.
I believe this is effectively a dupe of bug 1666059.
Updated•3 years ago
|
Updated•1 year ago
|
Description
•