.NET IntelliSense .context menu options are not highlighted when using system High Contrast Theme at docs.microsoft.com
Categories
(Core :: Layout, defect, P3)
Tracking
()
Accessibility Severity | s2 |
People
(Reporter: rbucata, Unassigned)
References
(Blocks 1 open bug, )
Details
(Keywords: access)
Environment:
Operating system: Windows 10 x64 PRO
Firefox version: :Firefox Nightly 101.0a1 (2022-04-27) (64-bit)
Preconditions:
Set the High Contrast
option to ON from Windows (shortcut: Left Alt+Left Shift+PrintScreen)
Steps to reproduce:
- Navigate to: https://docs.microsoft.com/en-us/learn/modules/csharp-write-first/5-solution
- Type a function into the .NET editor (e.g. Console).
- Navigate the newly opened list using the keyboard arrows.
- Observe the result.
Expected behavior:
The text of the context menu options is highlighted.
Actual behavior:
The text of the context menu options is not highlighted
Notes:
- Reproducible regardless of the status of ETP.
- Reproducible on the latest build of Firefox Nightly.
- Works as expected using Edge.
- Reproducible on other pages with a built-in .NET editor
Reporter | ||
Updated•2 years ago
|
Updated•2 years ago
|
Updated•2 years ago
|
Comment 1•2 years ago
|
||
The severity field for this bug is set to S3. However, the accessibility severity is higher, [access-s2].
:dholbert, could you consider increasing the severity?
For more information, please visit auto_nag documentation.
Updated•2 years ago
|
Updated•2 years ago
|
Updated•1 year ago
|
Updated•7 months ago
|
Comment 2•6 months ago
|
||
JFTR, I looked into this to determine if we should track this as a WebCompat bug or not. In my tests, I realized that Edge is the only browser doing some hover/focus highlighting here. Chrome follows Firefox and doesn't highlight anything.
We still should keep this open as the Edge behavior makes much more sense for people who need a high-contrast theme, but I'm not going to add a WebCompat tracking label here for now, as technically, Edge is the odd one out. :/
Comment 3•6 months ago
|
||
Yeah, this is basically the same as bug 1766846, where they're using an edge-specific media query.
Description
•