Open Bug 1916666 Opened 2 months ago Updated 2 months ago

Rules view filter input "no match" style don't adapt to High Contrast Mode

Categories

(DevTools :: Inspector: Rules, defect, P2)

defect

Tracking

(Accessibility Severity:s2)

Accessibility Severity s2

People

(Reporter: nchevobbe, Unassigned)

References

(Blocks 1 open bug)

Details

(Keywords: no-plan-to-ship)

Attachments

(2 files)

Attached image rules view filter input

See screenshot (I tweaked the base variable colors so it's easier to spot)

Flags: needinfo?(mreschenberg)

Triaging as S2 because UI doesn't adapt to HCM

Accessibility Severity: --- → s2
Flags: needinfo?(mreschenberg)
Severity: -- → S3
Priority: -- → P2

The severity field for this bug is set to S3. However, the accessibility severity is higher, .
:jdescottes, could you consider increasing the severity?

For more information, please visit BugBot documentation.

Flags: needinfo?(jdescottes)

For those bugs it's fine to have a different severity than the accessibility severity

Flags: needinfo?(jdescottes)

Adding a keyword no-plan-to-ship as an ad-hoc flag here. This keyword was meant to exclude specific bugs from the general access-S2 tracking when there are no plans to ship the affected feature. However, we do plan to address and ship this and other HCM-related devtools bugs, which are part of a larger project. This Dev Tools High Contrast Mode support project, tracked by the meta bug 1590215, is ongoing and is tracked by the Dev Tools team separately.

Keywords: no-plan-to-ship

Bug 1916333 fixed most of the issue, now we only need to take care of the "no match" style where we make the icon red

Summary: Rules view filter input colors don't adapt to High Contrast Mode → Rules view filter input "no match" style don't adapt to High Contrast Mode

I'm not sure we can use something like this

You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: