- From: Rich Tibbett <richt@opera.com>
- Date: Tue, 06 Sep 2011 16:15:15 +0200
- To: Anne van Kesteren <annevk@opera.com>
- CC: www-dom@w3.org, Robin Berjon <robin@berjon.com>, public-device-apis@w3.org
Anne van Kesteren wrote: > On Tue, 06 Sep 2011 13:52:21 +0200, Robin Berjon <robin@berjon.com> wrote: >> [...] > > <input>.click() and window.open() are not events. For window.open() I > believe HTML uses http://www.whatwg.org/C#allowed-to-navigate which is > also used for setting window.location. There might be some other > conditions as well. I think the point is that those conditions are not documented anywhere in the specs even though the UA behavior is generally consistent across implementations. All UAs implement popup blocker functionality so any page-synthesized click cannot open a popup window. Some (but, notably, not all) UAs only allow <input type=file>.click() when the user actively clicks on that file HTML element rather than just being capable of triggering the file picker from code. Some standard terminology/methodology would be useful for referencing this already widely implemented behavior elsewhere.
Received on Tuesday, 6 September 2011 14:16:08 UTC