So this would just make pop-unders turn into pop-overs correct?
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,
Resent from the correct account.
On Mon, May 21, 2012 at 4:16 AM, Eric Seidel esei...@google.com wrote:
So this would just make pop-unders turn into pop-overs correct?
On Mon, May 21, 2012 at 2:17 AM, Jochen Eisinger joc...@chromium.org wrote:
Hey,
in
On Mon, May 21, 2012 at 1:16 PM, Eric Seidel esei...@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,
I have a non-specific concern about compatibility here. I think a setting
would be good to allow ports to have bake time if they want it.
- Adele
On May 21, 2012, at 2:17 AM, Jochen Eisinger wrote:
Hey,
in https://bugs.webkit.org/show_bug.cgi?id=86969 I'm changing window.focus
and
On Mon, May 21, 2012 at 8:17 PM, Eric Seidel e...@webkit.org wrote:
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?)
I don't think this changed a lot since FF started to
On Mon, May 21, 2012 at 2:17 AM, Jochen Eisinger joc...@chromium.orgwrote:
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
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
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.orgwrote:
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
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.orgwrote:
Hey,
in https://bugs.webkit.org/show_bug.cgi?id=86969 I'm changing
On Mon, May 21, 2012 at 12:21 PM, Jochen Eisinger joc...@chromium.orgwrote:
On Mon, May 21, 2012 at 9:16 PM, Andrew Wilson atwil...@google.comwrote:
On Mon, May 21, 2012 at 2:17 AM, Jochen Eisinger joc...@chromium.orgwrote:
Hey,
in https://bugs.webkit.org/show_bug.cgi?id=86969 I'm
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
On May 21, 2012, at 12:25 PM, Andrew Wilson atwil...@google.com wrote:
No, because the setTimeout() callback would be executed outside the context
of a user gesture.
This isn't always true. User gesture state is forwarded to the timeout's
callback if the timeout was scheduled in the context
12 matches
Mail list logo
