On May 21, 2012, at 12:24 PM, Andrew Wilson <atwil...@google.com> wrote:
> > > On Mon, May 21, 2012 at 12:21 PM, Maciej Stachowiak <m...@apple.com> wrote: > > On May 21, 2012, at 12: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, > > Not necessarily for or against the change, but we could (and probably should) > make notifications do this automatically. Is there any case where clicking a > notifiicatin should not bring the relevant page to the front? > > Yes. For example, in gmail, if you click on an email notification, we open a > new window and display that email. We don't want to bring the parent to the > front in that case. Fair enough. But it seems like we could find some way to handle notifications as a special case without giving windows the ability to alter the stacking order at any time, even if my first proposal is too crude. Cheers, Maciej
_______________________________________________ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
