Closed
Bug 1388983
Opened 8 years ago
Closed 6 years ago
Close (x) button on shield notification bar too light to see
Categories
(Shield :: Heartbeat, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: bugs, Unassigned, NeedInfo)
Details
Attachments
(1 file)
31.33 KB,
image/png
|
Details |
The white [X] button is difficult to see on the light gray background in the marketing messages in Firefox. See attached screenshot.
Reporter | ||
Comment 1•8 years ago
|
||
Expected results: "Close" is arguably the most important UI for web advertisements, even if it's Firefox doing the advertising. It should be just as visible as the "Make a match" or "Give feedback" buttons
Comment 2•8 years ago
|
||
This notification bar is part of SHIELD: https://wiki.mozilla.org/Firefox/Shield/Heartbeat
status-firefox57:
affected → ---
Component: Notifications and Alerts → Heartbeat
Product: Toolkit → Shield
Summary: Close (x) button on marketing prompts too light to see → Close (x) button on shield notification bar too light to see
Version: 57 Branch → unspecified
Comment 3•8 years ago
|
||
jet: Are you still seeing the white X as shown in the screenshot? On Nightly I'm now seeing a small black X:
https://user-images.githubusercontent.com/193106/30085461-661003a6-924b-11e7-91f8-5799a582aeba.png
The smallness and mis-aligned-ness is still an issue, and we have a PR to fix that that should land in mozilla-central before 57 moves out of Nightly: https://github.com/mozilla/normandy/pull/1037
Flags: needinfo?(bugs)
Reporter | ||
Comment 4•8 years ago
|
||
I haven't seen a heartbeat message in a while, but the black X in your screenshot is an improvement. Thanks for fixing this, and the alignment bug.
Flags: needinfo?(bugs)
Comment 5•8 years ago
|
||
Oh yeah, probably should have included how to test this in my comment. :P
In case you still want to verify, https://normandy-mock.dev.mozaws.net/ has instructions on how to set up and run a test case for Shield; any of the "ShowHeartbeat" test cases on that page should work.
I think we can mark this as resolved either way.
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → WORKSFORME
Comment 6•8 years ago
|
||
Gijs reports this as still being broken on 56.0 release candidate builds.
This isn't an issue for 57, as per comment 3.
Matt: We can fix this for 56, but it'd probably require a system add-on update and (short) QA cycle. Thoughts?
Status: RESOLVED → REOPENED
Flags: needinfo?(mgrimes)
Resolution: WORKSFORME → ---
Comment 7•6 years ago
|
||
57 is long gone. Re-closing this.
Status: REOPENED → RESOLVED
Closed: 8 years ago → 6 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•