Closed Bug 1702954 Opened 3 years ago Closed 1 year ago

There is no hover highlight when using a high contrast theme in the about:preferences page

Categories

(Firefox :: Theme, defect)

Desktop
Windows 10
defect

Tracking

()

RESOLVED WORKSFORME
Tracking Status
firefox87 --- affected
firefox88 --- affected
firefox89 --- affected

People

(Reporter: cbaica, Unassigned)

Details

Affected versions

  • Fx89.0a1
  • Fx88.0b7

Affected platforms

  • Windows 10

Steps to reproduce

  1. Set a High Contrast theme in the OS.
  2. Launch Firefox and enable proton.
  3. Navigate to about:preferences.
  4. Hover over a section on the left e.g. "Search".

Expected result

  • There is a hover highlight animation.

Actual result

  • There is no hover highlight.

Regression range

  • This might be a really old regression, but proton hover design is new and we might want to try and fix some of it for high contrast theme.

Additional notes

  • This issue occurs for builds without proton enabled.
  • The issue does not occur on macOS platforms.
  • The issue occurs with any of the 4 high contrast themes available in Windows 10.
  • The issue also occurs in the about:addons page with the Extensions, Themes, Plugins and Recommendations sections.
  • The issue also occurs in the about:telemetry page for any section on the left side that is selected.
  • There is no indication when a certain section is selected.
Summary: There is no hover highlight and no selection highlight when using a high contrast theme in the about:preferences page → There is no hover highlight when using a high contrast theme in the about:preferences page
Has Regression Range: --- → no
Has STR: --- → yes
QA Whiteboard: [qa-regression-triage]

This issue no longer occurs on windows 10. I've attempted to find the fix responsible but the changes are quite old so exact results could not be provided:
Tested mozilla-central build: 2021-05-10 (verdict: b)
Tested mozilla-central build: 2021-05-11 (verdict: g)

Status: NEW → RESOLVED
Closed: 1 year ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.