Closed Bug 1799460 Opened 2 years ago Closed 2 years ago

Some of the toolbar context menu options are not completely displayed in high contrast mode

Categories

(Firefox :: Theme, defect)

Firefox 108
Desktop
Windows
defect

Tracking

()

RESOLVED FIXED
109 Branch
Accessibility Severity s2
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)

Attached video 2022-11-07_16h02_38.mp4

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

  1. Enable high contrast mode.
  2. Launch Firefox and open the toolbar context menu.
  3. 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

Has STR: --- → yes

:emilio do you think you could take a look and see if this was caused by bug 1795199?

Flags: needinfo?(emilio)

Bug 1790616 most likely.

Assignee: nobody → emilio
Regressed by: 1790616

This reduces the weird interactions that can appear on menus.

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

Flags: needinfo?(emilio)
Duplicate of this bug: 1800228

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.

Whiteboard: [access-s2]

Let's use legacy layout in beta in native menupopups to fix this bug.

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
Attachment #9303374 - Flags: approval-mozilla-beta?
Flags: qe-verify+

Comment on attachment 9303374 [details]
Bug 1799460 - Patch for beta. r=Gijs

Approved for 108.0b2

Attachment #9303374 - Flags: approval-mozilla-beta? → approval-mozilla-beta+
QA Whiteboard: [qa-triaged]

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.

Flags: needinfo?(emilio)

Sure.

Severity: S4 → S2
Flags: needinfo?(emilio)

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.

Flags: needinfo?(emilio)

That's expected, proper fix hasn't landed on Nightly yet.

Flags: needinfo?(emilio)
Pushed by ealvarez@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/fa753c8bdf4c Use width rather than min-width to set right/left menu sizes on windows menus. r=Gijs https://hg.mozilla.org/integration/autoland/rev/9da892f98d1b Implement label[value] and start/end cropping with CSS rather than XUL layout. r=Gijs,jfkthame https://hg.mozilla.org/integration/autoland/rev/fd69d6b3aeb8 a11y fixes for my previous changes. r=Jamie
Pushed by emilio@crisal.io: https://hg.mozilla.org/integration/autoland/rev/bcc0928c17b4 Annotate a test as passing in windows/android.
Pushed by ryanvm@gmail.com: https://hg.mozilla.org/integration/autoland/rev/392eeb01c8d5 Annotate a test as passing on Mac also.
Regressions: 1801157
Regressions: 1801162
Regressions: 1801172
Regressions: 1801215

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?

Flags: needinfo?(emilio)

Like we do for the left and so on.

Let's reopen for that.

Status: RESOLVED → REOPENED
Flags: needinfo?(emilio)
Resolution: FIXED → ---
Pushed by ealvarez@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/a8246e46adce Unset width in non-native menu-right. r=desktop-theme-reviewers,dao
Status: REOPENED → RESOLVED
Closed: 2 years ago2 years ago
Resolution: --- → FIXED
Attached image 2022-11-21_12h01_51.png

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).

Flags: needinfo?(emilio)
Regressions: 1801732
Depends on: 1801844

Bug 1801844 should take care of this for good.

Flags: needinfo?(emilio)
Duplicate of this bug: 1802264
Regressions: 1802669
Regressions: 1802508
Regressions: 1802945

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).

(In reply to Catalin Sasca, QA [:csasca] from comment #27)

Created attachment 9307319 [details]
win 7 speed context menu.png

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).

Is this tracked somewhere?

Flags: needinfo?(emilio)
Flags: needinfo?(catalin.sasca)

Pretty sure this was bug 1803773 effectively.

Flags: needinfo?(emilio)

Logged Bug 1800228 initially on this, but was duped. I think the correct one now may be the one Emilio mentioned.

Flags: needinfo?(catalin.sasca)
Regressions: 1806167
Regressions: 1807233
Regressions: 1813025
Regressions: 1815843
Regressions: 1822646
Regressions: 1825762
Accessibility Severity: --- → s2
Whiteboard: [access-s2]
Regressions: 1845895
QA Whiteboard: [qa-triaged]
Flags: qe-verify+
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: