On Mon, May 21, 2012 at 12:21 PM, Jochen Eisinger <joc...@chromium.org>wrote:
> > > On Mon, May 21, 2012 at 9:16 PM, Andrew Wilson <atwil...@google.com>wrote: > >> >> >> On Mon, May 21, 2012 at 2:17 AM, Jochen Eisinger <joc...@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. >>> >> >> The new behavior you describe will break notifications, since many pages >> will want to bring themselves to the front when someone clicks on their >> notification, and your patch prevents this. I suspect that the Firefox >> behavior will need to change when they add support for notifications. >> >> I still think that a superior change would be to prevent applications >> from calling window.focus() or window.blur() in the context of a user >> gesture once they've opened a new window. This would address popunders, >> while still allowing notifications to work. >> > > The web page could just use setTimeout your restriction to work around > this, no? > No, because the setTimeout() callback would be executed outside the context of a user gesture. > > -jochen > > >> >>> >>> 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@lists.webkit.org >>> http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev >>> >>> >> >
_______________________________________________ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
