Some of the toolbar context menu options are not completely displayed in high contrast mode
Categories
(Firefox :: Theme, defect)
Tracking
()
Tracking | Status | |
---|---|---|
firefox-esr102 | --- | unaffected |
firefox106 | --- | unaffected |
firefox107 | --- | unaffected |
firefox108 | --- | verified |
firefox109 | --- | fixed |
People
(Reporter: ailea, Assigned: emilio)
References
(Blocks 1 open bug, Regressed 2 open bugs, Regression)
Details
(Keywords: access, regression)
Attachments
(8 files)
1.97 MB,
video/mp4
|
Details | |
48 bytes,
text/x-phabricator-request
|
Details | Review | |
48 bytes,
text/x-phabricator-request
|
Details | Review | |
48 bytes,
text/x-phabricator-request
|
Details | Review | |
48 bytes,
text/x-phabricator-request
|
diannaS
:
approval-mozilla-beta+
|
Details | Review |
48 bytes,
text/x-phabricator-request
|
Details | Review | |
10.06 KB,
image/png
|
Details | |
1.98 MB,
image/png
|
Details |
Found in
- 108.0a1 (2022-11-07)
Affected versions
- 108.0a1 (2022-11-07)
Tested platforms
- Affected platforms: Windows 7, Windows 10
- Unaffected platforms: macOS 12, Ubuntu 20
Steps to reproduce
- Enable high contrast mode.
- Launch Firefox and open the toolbar context menu.
- Go to the Bookmarks Toolbar submenu.
Expected result
- Toolbar context menu items should be displayed correctly.
Actual result
- "Bookmarks Toolbar", "Only Show on New Tab" and "Never Show" options are not completely displayed.
Regression range
- First bad: aa325161aae5e555cab4d44b6662bbe029d26a5d
- Last good: 4ff88d45f59c4357dcc71ddf4ad5344a38f9944d
- Pushlog: https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=2815b08bfbd2f4abecf1e356461c0e2fc36bc025&tochange=fcb08a86da33aafb6527a040f598ce802d2d7a69
- Potentially regressed by: 1795199
Reporter | ||
Updated•2 years ago
|
Comment 1•2 years ago
|
||
:emilio do you think you could take a look and see if this was caused by bug 1795199?
Assignee | ||
Comment 2•2 years ago
|
||
Bug 1790616 most likely.
Assignee | ||
Comment 3•2 years ago
|
||
This reduces the weird interactions that can appear on menus.
Assignee | ||
Comment 4•2 years ago
|
||
This was hitting an interesting difference between XUL and non-XUL layout, when
you set min-width: <something> to something that also has non-default
appearance and imposes a min size.
This should behave consistently in both layout modes.
Depends on D161498
Assignee | ||
Updated•2 years ago
|
Assignee | ||
Comment 6•2 years ago
|
||
The button tweak is needed because now if you have:
<button>
<label value="foo">
</button>
There is a text node for the value (generated content), and the <button>
shouldn't steal it.
I was getting crashes without it because XULButtonAccessible isn't
hypertext (so I wonder if the IsText() code-path can even be reached?)
Setting crop="center" now reframes, so test_label needs to change.
Updated•2 years ago
|
Assignee | ||
Comment 7•2 years ago
|
||
Let's use legacy layout in beta in native menupopups to fix this bug.
Assignee | ||
Comment 8•2 years ago
|
||
Comment on attachment 9303374 [details]
Bug 1799460 - Patch for beta. r=Gijs
Beta/Release Uplift Approval Request
- User impact if declined: comment 0 and duplicate
- Is this code covered by automated tests?: No
- Has the fix been verified in Nightly?: No
- Needs manual test from QE?: Yes
- If yes, steps to reproduce: comment 0 and duplicate bug
- List of other uplifts needed: none
- Risk to taking this patch: Low
- Why is the change risky/not risky? (and alternatives if risky): One-liner to revert to 107's codepath on beta for now.
- String changes made/needed: none
- Is Android affected?: No
Assignee | ||
Updated•2 years ago
|
Comment 9•2 years ago
|
||
Comment on attachment 9303374 [details]
Bug 1799460 - Patch for beta. r=Gijs
Approved for 108.0b2
Comment 10•2 years ago
|
||
bugherder uplift |
Updated•2 years ago
|
Comment 11•2 years ago
|
||
The severity field for this bug is set to S4. However, the accessibility severity is higher, [access-s2].
:emilio, could you consider increasing the severity?
For more information, please visit auto_nag documentation.
Reporter | ||
Comment 13•2 years ago
|
||
Both bugs (this one and its duplicate) are verified - fixed in Beta 108.0b2 on Windows 10 and Windows 7. However, both issues are still reproducible in the latest Nightly 109.0a1 (2022-11-15). @Emilio do you know if these bugs will be also fixed in Nightly 109?
Thanks.
Assignee | ||
Comment 14•2 years ago
|
||
That's expected, proper fix hasn't landed on Nightly yet.
Comment 15•2 years ago
|
||
Comment 16•2 years ago
|
||
Comment 17•2 years ago
|
||
Comment 18•2 years ago
|
||
bugherder |
https://hg.mozilla.org/mozilla-central/rev/fa753c8bdf4c
https://hg.mozilla.org/mozilla-central/rev/9da892f98d1b
https://hg.mozilla.org/mozilla-central/rev/fd69d6b3aeb8
https://hg.mozilla.org/mozilla-central/rev/bcc0928c17b4
https://hg.mozilla.org/mozilla-central/rev/392eeb01c8d5
Reporter | ||
Comment 19•2 years ago
|
||
Re-tested using the latest Nightly build (build id: 20221118094451) on Windows 10 and the issue is still reproducible there. Emilio, could you please take a look over it?
Assignee | ||
Comment 20•2 years ago
|
||
Like we do for the left and so on.
Assignee | ||
Comment 21•2 years ago
|
||
Let's reopen for that.
Comment 22•2 years ago
|
||
Updated•2 years ago
|
Comment 23•2 years ago
|
||
bugherder |
Reporter | ||
Comment 24•2 years ago
|
||
Both issues are still reproducible in the latest Nightly 109.0a1 (build id: 20221121093640), tested on Win10 (see the screenshot) and Win7 (the duplicate bug).
Assignee | ||
Comment 25•2 years ago
|
||
Bug 1801844 should take care of this for good.
Comment 27•2 years ago
•
|
||
Worked on Win 7 and saw that there is still an issue on context menu when selecting the video speed as it is still not looking as it should. Here's an attachment with it on 109.0a1 (2022-12-08).
Comment 28•2 years ago
|
||
(In reply to Catalin Sasca, QA [:csasca] from comment #27)
Created attachment 9307319 [details]
win 7 speed context menu.pngWorked on Win 7 and saw that there is still an issue on context menu when selecting the video speed as it is still not looking as it should. Here's an attachment with it on 109.0a1 (2022-12-08).
Is this tracked somewhere?
Assignee | ||
Comment 29•2 years ago
|
||
Pretty sure this was bug 1803773 effectively.
Comment 30•2 years ago
|
||
Logged Bug 1800228 initially on this, but was duped. I think the correct one now may be the one Emilio mentioned.
Updated•1 year ago
|
Updated•1 year ago
|
Description
•