- From: Simon Pieters <simonp@opera.com>
- Date: Wed, 27 May 2009 14:20:09 +0200
- To: public-html <public-html@w3.org>
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. -- Simon Pieters Opera Software
Received on Wednesday, 27 May 2009 12:20:46 UTC