Closed Bug 1935255 Opened 9 months ago Closed 4 months ago

Callout container and its secondary buttons on the Firefox View Discoverability panel are missing proper HCM treatments

Categories

(Firefox :: Messaging System, defect, P1)

defect
Points:
3

Tracking

()

VERIFIED FIXED
140 Branch
Iteration:
139.2 - Apr 14 - Apr 25
Accessibility Severity s3
Tracking Status
firefox-esr128 --- unaffected
firefox133 --- unaffected
firefox134 --- unaffected
firefox135 --- wontfix
firefox138 --- wontfix
firefox139 --- verified
firefox140 --- verified

People

(Reporter: ayeddi, Assigned: nsauermann)

References

(Blocks 1 open bug, Regression)

Details

(Keywords: access, regression)

Attachments

(3 files, 1 obsolete file)

The FX_VIEW_DISCOVERABILITY_ALL_USERS panel includes the following issues with the High Contrast themes on Windows that may resolve in some themes not providing an expected, readable experience for the text of the container and missing an expecting indication that both Dismiss and V buttons are, in fact, active UI elements that could be clicked (access-S3-level issues)

Observed in Release for the "Didn't mean to close that tab?" alertdialog treatment after closing a few tabs in a row.

Recommendation is to follow the HCM secondary button pattern (Figma reference, requires SSO to access) and HCM media queries for forced-colors mode by:

  1. Secondary buttons:
    1. Adding 1px border to each Dismiss and V secondary buttons - use ButtonText color (the background of buttons should be ButtonFace)
    2. Ensure hover styling is provided for both secondary buttons - use SelectedItem for the background and SelectedItemText for the border and label text (color pair)
    3. :active state would get the hover styling combo with ButtonText used for the border alone
  2. The callout container is using button treatments for its static text elements:
    1. use Canvas for the background of the container
    2. use CanvasText for the foreground color of the container (its headings text)
Summary: Callout container and its secondary buttons on the Firefox View Discoverability panel are missing proper HCM threatments → Callout container and its secondary buttons on the Firefox View Discoverability panel are missing proper HCM treatments

Set release status flags based on info from the regressing bug 1923726

:pdahiya, since you are the author of the regressor, bug 1923726, could you take a look? Also, could you set the severity field?

For more information, please visit BugBot documentation.

Flags: needinfo?(pdahiya)
See Also: → 1919598

Looks like picked by bot as regression due to added test message. This message is seen via Nimbus Rollout but there is patch linked to bug 1919598 in flight that's going to land in default. NI @nsauermann to weigh in before landing by default Thanks

Flags: needinfo?(nsauermann)

Thanks for flagging Anna & Punam - I'll look into this in my in-progress patch 1919598 to land the experience in m-c.

Flags: needinfo?(nsauermann)
Assignee: nobody → nsauermann
Depends on: 1919598
No longer regressed by: 1923726
See Also: 1919598

On 2nd thought, might make sense to tackle this one on it's own since it's specific to the submenu component rather than the message itself.

Blocks: 1868494
No longer depends on: 1919598
Regressions: 1868494
See Also: → 1868494
Blocks: 1919598
No longer blocks: 1868494
Severity: -- → S3
Iteration: --- → 135.2 - Dec 9 - Dec 20
Points: --- → 3
Priority: -- → P1
Regressed by: 1868494
No longer regressions: 1868494
Iteration: 135.2 - Dec 9 - Dec 20 → 135.3 - Dec 23 - Jan 3
Iteration: 135.3 - Dec 23 - Jan 3 → 136.1 - Jan 6 - Jan 17
Iteration: 136.1 - Jan 6 - Jan 17 → 136.2 - Jan 20 - Jan 31
Iteration: 136.2 - Jan 20 - Jan 31 → 137.1 - Feb 3 - Feb 14
Iteration: 137.1 - Feb 3 - Feb 14 → 137.2 - Feb 17 - Feb 28
Iteration: 137.2 - Feb 17 - Feb 28 → 138.1 - Mar 3 - Mar 14
Iteration: 138.1 - Mar 3 - Mar 14 → 138.2 - Mar 17 - Mar 28
Blocks: 1955039
Iteration: 138.2 - Mar 17 - Mar 28 → 139.1 - Mar 31 - Apr 11
Iteration: 139.1 - Mar 31 - Apr 11 → 139.2 - Apr 14 - Apr 25

Hi Anna! I synced up with Shane about the following:

The callout container is using button treatments for its static text elements:

  • use Canvas for the background of the container
  • use CanvasText for the foreground color of the container (its headings text)

We're using arrowpanel colors:

:is(menupopup, panel):where([type="arrow"]) {
  --panel-background: var(--arrowpanel-background);
  --panel-color: var(--arrowpanel-color);
  --panel-border-color: var(--arrowpanel-border-color);
  --panel-border-radius: var(--arrowpanel-border-radius);
  --panel-padding: var(--arrowpanel-padding);
  --panel-shadow-margin: var(--arrowpanel-shadow-margin);
}

from global-shared.css as our feature callouts are themed. CanvasText is a system color and not theme color and I believe we're re-purposing the same colors other panels in the browser - any concerns with leaving the callout background and foreground as-is?

Flags: needinfo?(ayeddi)
Flags: qe-verify+

Will be landing the split dismiss button changes shortly. Would love to get the button changes uplifted into Fx139 if possible, so I'm adding qe-verify flag and will request uplift once the patch lands.

Will open another patch for the panel changes once I've synced up with the team.

Flags: needinfo?(ayeddi)
Attachment #9484352 - Flags: approval-mozilla-beta?
Duplicate of this bug: 1955039
Pushed by nsauermann@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/431cd644c5fd FC Updates split dismiss button HCM styling and buttons using tokens-shared variables r=omc-reviewers,accessibility-frontend-reviewers,emcminn,ayeddi
Status: NEW → RESOLVED
Closed: 4 months ago
Resolution: --- → FIXED
Target Milestone: --- → 140 Branch

Verified as fixed in our latest Nightly 140.0a1 (2025-04-30)

QA Whiteboard: [qa-ver-needed-c140/b139]
QA Contact: rdoghi

Please fill out the uplift request form on the Beta Phabricator revision when this is ready for Beta uplift.

Flags: needinfo?(nsauermann)

Oh sorry about that Ryan, I thought I did and I can see in the beta phabricator logs mimi updated the uplift request field.Tue, Apr 29, 1:57 PM, may have somehow overwrote the uplift request form. Let me take a look!

edit: Can't see a way to add the uplift form again on the original beta phabricator ticket - drop down option no longer exists, filing another one - sorry about that.

Flags: needinfo?(nsauermann)

Brings Feature Callout hcm and button styling up to sync with tokens-shared, including the missing border states.

Original Revision: https://phabricator.services.mozilla.com/D245474

firefox-beta Uplift Approval Request

  • User impact if declined: Users with HCM enabled will experience unexpected styling for the split dismiss feature callout button. We have a few production messages using that button component.
  • Code covered by automated testing: no
  • Fix verified in Nightly: yes
  • Needs manual QE test: no
  • Steps to reproduce for manual QE testing: Test plan
  • Risk associated with taking this patch: Low
  • Explanation of risk level: Styling fix, which are repurposing existing styling from our tokens that were either outdated or missing.
  • String changes made/needed: N/A
  • Is Android affected?: no
Attachment #9484789 - Flags: approval-mozilla-beta+
Attachment #9484352 - Attachment is obsolete: true
Attachment #9484352 - Flags: approval-mozilla-beta?
Status: RESOLVED → VERIFIED
QA Whiteboard: [qa-ver-needed-c140/b139] → [uplift][qa-ver-done-c140/b139]
Flags: qe-verify+
No longer blocks: 1955039
See Also: 1868494
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: