- From: <bugzilla@jessica.w3.org>
- Date: Fri, 15 Jul 2011 19:42:25 +0000
- To: public-html-bugzilla@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=13273 --- Comment #8 from Shelley Powers <shelleyp@burningbird.net> 2011-07-15 19:42:25 UTC --- And further in the same text is the following: "Even when the attribute is absent, however, user agents may provide controls to affect playback of the media resource (e.g. play, pause, seeking, and volume controls), but such features should not interfere with the page's normal rendering. For example, such features could be exposed in the media element's context menu." So does this mean that if the controls attribute is missing and scripting is disabled that providing this functionality in the context menu is sufficient? But the context menu isn't necessarily what I would think of when reading "expose a user interface". Is that why other browsers don't provide the control UI? Because they expose this functionality (always) in the Context menu? -- Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug.
Received on Friday, 15 July 2011 19:42:29 UTC