Rules view filter input "no match" style don't adapt to High Contrast Mode
Categories
(DevTools :: Inspector: Rules, defect, P2)
Tracking
(Accessibility Severity:s2, firefox135 fixed)
| Tracking | Status | |
|---|---|---|
| firefox135 | --- | fixed |
People
(Reporter: nchevobbe, Assigned: nchevobbe)
References
(Blocks 1 open bug)
Details
(Keywords: no-plan-to-ship)
Attachments
(3 files)
See screenshot (I tweaked the base variable colors so it's easier to spot)
| Assignee | ||
Updated•1 year ago
|
| Assignee | ||
Comment 1•1 year ago
|
||
Triaging as S2 because UI doesn't adapt to HCM
| Assignee | ||
Updated•1 year ago
|
Comment 2•1 year ago
|
||
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.
Comment 3•1 year ago
|
||
For those bugs it's fine to have a different severity than the accessibility severity
Updated•1 year ago
|
Comment 4•1 year ago
|
||
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.
| Assignee | ||
Comment 5•1 year ago
|
||
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
| Assignee | ||
Comment 6•1 year ago
|
||
I'm not sure we can use something like this
| Assignee | ||
Comment 7•1 year ago
|
||
The HCM guidelines indicate we shouldn't have different colors on the input.
Updated•1 year ago
|
Comment 9•1 year ago
|
||
| bugherder | ||
Description
•