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.
> 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.)
>>> someone could maintain a list of annoying sites which could be
>>> automatically banned from creating popups.
>>
>> Doomed approach, just like the "child-protecting" site blocker apps.
>
> Doomed why?
Because blacklist are always incomplete up to a point were they offer
neglectable protection, and whitelists are always so incomplete that
they interfere substantially with normal usage. There are just too many
domains out there. Some count that as advantage :).
