[webkit-dev] Changes to window.focus/window.blur controlled by a setting?

Eric Seidel eric at webkit.org
Mon May 21 11:17:20 PDT 2012


So the goal (FF's goal) is to guilt the site into not using pop-ups
anymore? Since they don't want to take you away from their content (as
pop-unders allow them to do?)

My first thought was that we might as well just nuke/block the pop-up
if it calls blur() (and log to the console somewhere).  But perhaps we
can try that in a year if this fails to produce results. :)

On Mon, May 21, 2012 at 4:17 AM, Jochen Eisinger <jochen at chromium.org> wrote:
>
>
> On Mon, May 21, 2012 at 1:16 PM, Eric Seidel <eseidel at google.com> wrote:
>>
>> So this would just make pop-unders turn into pop-overs correct?
>
>
> Correct. Keep in mind that at this point, our logic already decided that
> it's ok for the page to show a popup
>
> -jochen
>
>>
>>
>> On Mon, May 21, 2012 at 2:17 AM, Jochen Eisinger <jochen at chromium.org>
>> wrote:
>> > Hey,
>> >
>> > in https://bugs.webkit.org/show_bug.cgi?id=86969 I'm changing
>> > window.focus
>> > and window.blur to match Firefox's behavior: window.blur does nothing,
>> > and
>> > window.focus only works when invoked from the window that actually
>> > opened
>> > the former.
>> >
>> > The goal is to thwart so-called pop unders.
>> >
>> > Does any port want to have this new behavior configurable by e.g. a
>> > setting?
>> >
>> > Feel free to directly comment on the bug.
>> >
>> > best
>> > -jochen
>> >
>> > _______________________________________________
>> > webkit-dev mailing list
>> > webkit-dev at lists.webkit.org
>> > http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
>> >
>
>


More information about the webkit-dev mailing list