Closed Bug 1632132 Opened 3 years ago Closed 3 years ago

Dark theme - screen reader - previous/next buttons appear disabled due to color scheme picked


(Toolkit :: Reader Mode, defect, P1)

68 Branch



Tracking Status
firefox-esr68 --- wontfix
firefox75 --- wontfix
firefox76 --- wontfix
firefox77 --- verified


(Reporter: cfogel, Assigned: mconley)


(Keywords: regression)


(2 files)

Affected versions

  • 76.0b7, 77.0a1(2020.04.20)

Affected platforms

  • Windows 10, macOS 10.15.3, Ubuntu 18.04;

Steps to reproduce

  1. Launch Firefox and access
  2. Click on the button to trigger the reader mode;
  3. Change the theme for it on Black/Dark;
  4. Click on the Narrate button click on the play button;
  5. Click on Play to start narration;
  6. Click on the Next/Previous button;

Expected result

  • buttons appear as being available;

Actual result

  • due to color setup next/previous buttons appear as being unavailable;

Regression range

  • will check and provide one asap;

Additional notes

  • attached recording to better illustrate the issue;
  • ideally color would be changed to white as well for the 2 buttons, at least once available.
Has Regression Range: --- → yes
Has STR: --- → yes

Recording for it.

Has Regression Range: yes → no

Initially tested the issues on Windows 10 x64 with Firefox 75.0. Updating the status flag as well.

Thanks for the updates @Julien & abodenlosz.

Has Regression Range: no → yes

I suspect this is because these rules:,120-121

are overriding this rule:

The hardcoded values in narrate.css don't seem to be compatible with the dark theme, so it probably makes sense to fallback to using the values defined in aboutReader.css, which automatically adjust between dark and light theme.

Assignee: nobody → mconley
Priority: -- → P1
Pushed by
Fix about:reader narrate back and forward buttons for dark theme. r=ntim
Closed: 3 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla77

Verified the fix with Nightly 77.0a1 (2020-04-26) on Windows 10 x64. Updating the flag to verified.

Also verified on macOS 10.15 and Ubuntu 18.04 x64 with the latest Nightly build.

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