Closed
Bug 346132
Opened 18 years ago
Closed 18 years ago
Block Popup Windows By Default
Categories
(Camino Graveyard :: Annoyance Blocking, enhancement)
Tracking
(Not tracked)
RESOLVED
FIXED
Camino1.5
People
(Reporter: bugs, Assigned: froodian)
References
Details
(Keywords: fixed1.8.1, Whiteboard: [string changes in comment 10])
Attachments
(1 file)
3.30 KB,
patch
|
hwaara
:
review+
mikepinkerton
:
superreview+
|
Details | Diff | Splinter Review |
I should not have to edit preferences to make my browser usable. Please, please, please block popups by default!
Pretty much everyone else does this now.
We have some other bugs in the meta that we need to think about when changing the wording on the "first-time" notice.
Blocks: 343938
Assignee | ||
Comment 3•18 years ago
|
||
Wait, so are we getting rid of the "first-time" notice entirely, or just rewording it (perhaps with better button titles than "ok" and "cancel") so that users can choose the "block popups" option easier?
Assignee: nobody → stridey
Oh, hmm. I had thought Firefox blocked the popup but still showed a first-time message while blocking, but I just checked 2.0b1 again and it doesn't.
We really need to get the UI right on the bar, then.
Component: Preferences → Annoyance Blocking
QA Contact: preferences → annoyance.blocking
Assignee | ||
Comment 5•18 years ago
|
||
I've been thinking about this, and I really think we should just keep the first-time warning. It lets users choose what they want to do, which once we have both pop-up blockers, is far from guaranteed.
Comment 6•18 years ago
|
||
(In reply to comment #5)
> I've been thinking about this, and I really think we should just keep the
> first-time warning. It lets users choose what they want to do, which once we
> have both pop-up blockers, is far from guaranteed.
I agree. Is this a simple change? We should turn this on. :)
Assignee | ||
Comment 7•18 years ago
|
||
It's already on now, so very easy. ;) WF (per previous comment and IRC).
Status: NEW → RESOLVED
Closed: 18 years ago
Resolution: --- → WONTFIX
Comment 8•18 years ago
|
||
um. what just happened here?
Status: RESOLVED → REOPENED
Resolution: WONTFIX → ---
Comment 9•18 years ago
|
||
ben's point was that the pref should just start out on (blocking popups). I can't imagine any user ever says "no" to that sheet, so just asking them is lame. We should just do the right thing.
Now that we can unblock popups, it's easy to undo if we get it wrong (which we rarely do). It's not dangerous anymore to block them.
Assignee | ||
Comment 10•18 years ago
|
||
String changes: Remove the entire /* popup blocking */ section.
Attachment #239539 -
Flags: review?(hwaara)
Assignee | ||
Updated•18 years ago
|
Whiteboard: [string changes in comment 10]
Comment 11•18 years ago
|
||
Comment on attachment 239539 [details] [diff] [review]
Does the deed
* Remember to also remove the PopupBlockMsg string.
* Since nothing in our code is now using the browser.popups.showPopupBlocker pref, there's no need to set it to false. We should reuse it later for the actual "put the blocker in the statusbar"-pref.
Attachment #239539 -
Flags: review?(hwaara) → review+
Comment 12•18 years ago
|
||
Another thing that struck me, when I used a vanilla copy of Camino at a friend's house lately, is that Adblocking is off by default.
I'd like to see that on by default as well.
Updated•18 years ago
|
Attachment #239539 -
Flags: superreview?(mikepinkerton)
Comment 13•18 years ago
|
||
(In reply to comment #12)
> Another thing that struck me, when I used a vanilla copy of Camino at a
> friend's house lately, is that Adblocking is off by default.
>
> I'd like to see that on by default as well.
Let's discuss that in another bug.
Comment 14•18 years ago
|
||
bug 353810 filed for comment 12.
Comment 15•18 years ago
|
||
Comment on attachment 239539 [details] [diff] [review]
Does the deed
sr=pink
Attachment #239539 -
Flags: superreview?(mikepinkerton) → superreview+
Assignee | ||
Comment 16•18 years ago
|
||
Checked in on 1.8branch and trunk
Status: REOPENED → RESOLVED
Closed: 18 years ago → 18 years ago
Keywords: fixed1.8.1
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•