Closed
Bug 1900240
Opened 2 years ago
Closed 2 years ago
Home and newtab small link text colour issue with wallpaper
Categories
(Firefox :: New Tab Page, defect, P1)
Firefox
New Tab Page
Tracking
()
VERIFIED
FIXED
128 Branch
| Tracking | Status | |
|---|---|---|
| firefox-esr115 | --- | unaffected |
| firefox126 | --- | unaffected |
| firefox127 | --- | unaffected |
| firefox128 | --- | verified |
People
(Reporter: thecount, Assigned: thecount)
References
(Regression)
Details
(Keywords: regression, Whiteboard: [hnt])
Attachments
(1 external file)
Fairly small issue.
Step to test:
- Set browser.newtabpage.activity-stream.newtabWallpapers.enabled to true
- Set browser.newtabpage.activity-stream.newtabWallpapers.v2.enabled to true
- Set a dark colour wallpaper
- Inspect the "Learn more" link in the pocket section header
- On that element in the inspector, right click, change pseudo class, and select visited
Expected: Nothing should change
Actual: It switching to light mode text colour
Updated•2 years ago
|
| Assignee | ||
Comment 1•2 years ago
|
||
Comment 2•2 years ago
|
||
Set release status flags based on info from the regressing bug 1898818
status-firefox126:
--- → unaffected
status-firefox127:
--- → unaffected
status-firefox128:
--- → affected
status-firefox-esr115:
--- → unaffected
Updated•2 years ago
|
Severity: -- → S3
Priority: -- → P1
Pushed by achurchwell@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/ce473e8ac585
Home and newtab fixing link text colour issue with wallpaper r=home-newtab-reviewers,amy
Comment 4•2 years ago
|
||
| bugherder | ||
Status: NEW → RESOLVED
Closed: 2 years ago
Resolution: --- → FIXED
Target Milestone: --- → 128 Branch
Comment 5•2 years ago
|
||
I have verified that this issue is no longer reproducible using the latest Firefox Nightly 128.0a1 (Build ID: 20240607090815) installed on Windows 10 x64, macOS 14.1.1, and Ubuntu 22.04 x64. I can confirm that the color of the "Learn more" link has not changed after selecting the "visited" option.
Status: RESOLVED → VERIFIED
You need to log in
before you can comment on or make changes to this bug.
Description
•