Closed Bug 434153 Opened 17 years ago Closed 9 years ago

Malware and web forgery bar should be like popup blocked bar

Categories

(Firefox :: Theme, defect)

x86
Windows XP
defect
Not set
trivial

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: nightstalkerz, Unassigned)

References

Details

(Whiteboard: [may be fixed by 423744])

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9pre) Gecko/2008051606 Minefield/3.0pre Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9pre) Gecko/2008051606 Minefield/3.0pre The popup blocked bar does not have a border on all 4 sides whereas the malware and web forgery bar does. Both of these bars should only have a border at the bottom like the popup blocked bar. Reproducible: Always Steps to Reproduce: 1. Go to http://www.mozilla.com/firefox/its-a-trap.html 2. Go to http://www.mozilla.com/firefox/its-an-attack.html 3. Go to a site with popups 4. Look at the bars Actual Results: Malware and web forgery bars have a 3d border around them. Expected Results: There should only be a border on the bottom like the popup blocked bar.
You are right, in a sense, so I'm confirming this bug. Though, I think the border *is* around the popup blocker bar, the top and left colors match the background, so you can't see the border; but you can see it when you have the malware/phishing bar (because it's a red background). It would be nicer/more consistent if there were *only* a bottom border on both bars (it would behave more like top bar, and less like a floating bar)
Status: UNCONFIRMED → NEW
Ever confirmed: true
The patch in that bug 423744 that didn't make the 3.0 boat would've addressed the issue in this bug. *debates between marking bug 423744 as a dependency or marking this bug as a dupe of bug 423744*
Version: unspecified → Trunk
Depends on: 423744
Whiteboard: [may be fixed by 423744]
We no longer use notification bars and use interstitial/error pages instead. Marking WFM.
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.