Ben Bucksch wrote:
> Mitchell Stoltz wrote:
>
>> What if you could turn the blocking on for the current site via the
>> context menu? Would that be convenient enough?
>
>
> No. Also, as soon as I am on the site, it is too late to stop anything
> in the onload handler.
Well, you won't be scarred for life by seeing one popup ad. You find a
site with popup ads, you block window.open for that site.
>
>> I'm worried about making "disallow window.open except on user click"
>> the default, because I think even that might break a significant
>> number of legitimate uses. It could be a pref that applies to all
>> sites, though.
>
>
> Yes, I can understand that. One effect that's wanted here is that
> popup-ads are ignored, and Netscape probably has no interest in that.
> Also, I agree, it might break sites. It is an advanced protection
> offered to the user, something that Mozilla and Netscape 6 usually turn
> on on request only. (Beonex Communicator is a different matter.)
Don't worry about what Netscape wants. This is a Mozilla forum. Netscape
may or may not take any particular feature, but that's no reason not to
work on it. Anyway, as Jesse says, we can sell it to Netscape as a
protection against denial-of-service :)
What people seem to be arguing for is a heuristic for distinguishing a
popup ad from a new window that we actually want to see. Before we go further,
let's try to define that heuristic. Doe it necessarily involve a user
click? You could still have a site opening popups or pop-unders every
time the user clicks on a link or form field. What's the gain?
-Mitch
