Closed
Bug 358686
Opened 18 years ago
Closed 18 years ago
pop-up blocker message text is confusing
Categories
(Camino Graveyard :: Annoyance Blocking, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
Camino1.5
People
(Reporter: mozilla.org, Assigned: stuart.morgan+bugzilla)
References
Details
(Keywords: fixed1.8.1.1)
Camino 1.1a1
The pop-up blocker message "A pop-up has been blocked for this website" is confusing--the pop-up has been blocked for the user, not for the Web site. It might be less confusing to say just "A pop-up has been blocked."
Also, perhaps it should say "pop-up window" (as it does in the preferences dialog) instead of just "pop-up."
If we do anything here, we need to do it by 1.1b1 at the latest.
"Camino has blocked a pop-up window [on|from] this website."
Assignee | ||
Comment 3•18 years ago
|
||
I don't think adding 'window' is worthwhile, as it makes the text longer without adding any real clarity.
Assignee | ||
Comment 4•18 years ago
|
||
We should also think about s/website/page/ since we've moved other text to say page.
Pink, this just text in a nib, so it doesn't really need a patch. What say you to:
"Camino has blocked a pop-up from this page."
(or alternately, "Camino has blocked a pop-up from this website")?
Comment 5•18 years ago
|
||
that's fine, just be consistent.
Assignee | ||
Comment 6•18 years ago
|
||
Checked in as "Camino has blocked a pop-up from this website." (page didn't quite feel right in that context somehow when I tried it) on trunk and MOZILLA_1_8_BRANCH.
Assignee: nobody → stuart.morgan
Keywords: fixed1.8.1.1
Assignee | ||
Updated•18 years ago
|
Status: NEW → RESOLVED
Closed: 18 years ago
Resolution: --- → FIXED
Clearing since this landed well in advance of b1....
Flags: camino1.1b1?
I'm still getting the old text ("A pop-up has been blocked for this website") with Camino 1.1.a2. Is the new text supposed to appear in that build?
Assignee | ||
Comment 9•18 years ago
|
||
The nib changes got stomped (probably by the wrapping stuff), thanks for noticing. Re-checked in.
You need to log in
before you can comment on or make changes to this bug.
Description
•