- From: Ian Hickson <ian@hixie.ch>
- Date: Fri, 12 Jun 2009 00:21:41 +0000 (UTC)
- To: Simon Pieters <simonp@opera.com>
- Cc: public-html <public-html@w3.org>
On Wed, 27 May 2009, Simon Pieters wrote: > > We're considering making the browser eat mouse and keyboard events when > the user uses the browser's controls for <video controls> and <audio > controls>. This is in order to side-step the issue about what should > happen when the author does .preventDefault, and also to be able to do > <a href><video controls> and make the link not be followed when the user > clicks play. (Even with <a href><video> the controls can be available if > scripting is disabled or the user makes them available from the context > menu.) > > Thus we suggest that no events be fired when the user uses the native > controls. > > This would also mean that <video controls> and <audio controls> don't > need to be "interactive content" wrt content models. Do other implementors have any opinions on this? -- Ian Hickson U+1047E )\._.,--....,'``. fL http://ln.hixie.ch/ U+263A /, _.. \ _\ ;`._ ,. Things that are impossible just take longer. `._.-(,_..'--(,_..'`-.;.'
Received on Friday, 12 June 2009 00:22:14 UTC