[html5] r5190 - [giow] (0) Ensure <video> controls don't overlap captions.

[whatwg at whatwg.org]

Author: ianh
Date: 2010-07-22 15:44:09 -0700 (Thu, 22 Jul 2010)
New Revision: 5190

Modified:
   complete.html
   index
   source
Log:
[giow] (0) Ensure <video> controls don't overlap captions.

Modified: complete.html
===================================================================
--- complete.html	2010-07-22 20:18:42 UTC (rev 5189)
+++ complete.html	2010-07-22 22:44:09 UTC (rev 5190)
@@ -28927,10 +28927,14 @@
   context menu.</p>
 
   <p>Where possible (specifically, for starting, stopping, pausing,
-  and unpausing playback, for muting or changing the volume of the
-  audio, and for seeking), user interface features exposed by the user
-  agent must be implemented in terms of the DOM API described above,
-  so that, e.g., all the same events fire.</p>
+  and unpausing playback, for seeking,
+<!--TT-->
+  for listing, enabling, and disabling timed tracks,
+<!--TT-->
+  and for muting or changing the volume of the audio), user interface
+  features exposed by the user agent must be implemented in terms of
+  the DOM API described above, so that, e.g., all the same events
+  fire.</p>
 
   <p>The <dfn id=dom-media-controls title=dom-media-controls><code>controls</code></dfn>
   IDL attribute must <a href=#reflect>reflect</a> the content attribute of the
@@ -86608,6 +86612,11 @@
   on top of their <code><a href=#video>video</a></code> element, as defined by the
   relevant rendering rules; for <a href=#websrt>WebSRT</a>, those are the
   <a href=#websrt-cue-text-rendering-rules>WebSRT cue text rendering rules</a> defined below.</p>
+
+  <p>When <a href=#expose-a-user-interface-to-the-user title="expose a user interface to the user">exposing a
+  user interface</a> for a <code><a href=#video>video</a></code> element, user agents
+  should attempt to position controls so as to not overlay any active
+  subtitles or captions.</p>
 <!--TT-->
 
   <p class=note>Resizing <code><a href=#video>video</a></code> and <code><a href=#the-canvas-element>canvas</a></code>

Modified: index
===================================================================
--- index	2010-07-22 20:18:42 UTC (rev 5189)
+++ index	2010-07-22 22:44:09 UTC (rev 5190)
@@ -213,7 +213,7 @@
 
   <header class=head id=head><p><a class=logo href=http://www.whatwg.org/ rel=home><img alt=WHATWG src=/images/logo></a></p>
    <hgroup><h1>HTML5 (including next generation additions still in development)</h1>
-    <h2 class="no-num no-toc">Draft Standard — 21 July 2010</h2>
+    <h2 class="no-num no-toc">Draft Standard — 22 July 2010</h2>
    </hgroup><p>You can take part in this work. <a href=http://www.whatwg.org/mailing-list>Join the working group's discussion list.</a></p>
    <p><strong>Web designers!</strong> We have a <a href=http://blog.whatwg.org/faq/>FAQ</a>, a <a href=http://forums.whatwg.org/>forum</a>, and a <a href=http://www.whatwg.org/mailing-list#help>help mailing list</a> for you!</p>
    <!--<p class="impl"><strong>Implementors!</strong> We have a <a href="http://www.whatwg.org/mailing-list#implementors">mailing list</a> for you too!</p>-->
@@ -28854,10 +28854,14 @@
   context menu.</p>
 
   <p>Where possible (specifically, for starting, stopping, pausing,
-  and unpausing playback, for muting or changing the volume of the
-  audio, and for seeking), user interface features exposed by the user
-  agent must be implemented in terms of the DOM API described above,
-  so that, e.g., all the same events fire.</p>
+  and unpausing playback, for seeking,
+<!--TT-->
+  for listing, enabling, and disabling timed tracks,
+<!--TT-->
+  and for muting or changing the volume of the audio), user interface
+  features exposed by the user agent must be implemented in terms of
+  the DOM API described above, so that, e.g., all the same events
+  fire.</p>
 
   <p>The <dfn id=dom-media-controls title=dom-media-controls><code>controls</code></dfn>
   IDL attribute must <a href=#reflect>reflect</a> the content attribute of the
@@ -79654,6 +79658,11 @@
   on top of their <code><a href=#video>video</a></code> element, as defined by the
   relevant rendering rules; for <a href=#websrt>WebSRT</a>, those are the
   <a href=#websrt-cue-text-rendering-rules>WebSRT cue text rendering rules</a> defined below.</p>
+
+  <p>When <a href=#expose-a-user-interface-to-the-user title="expose a user interface to the user">exposing a
+  user interface</a> for a <code><a href=#video>video</a></code> element, user agents
+  should attempt to position controls so as to not overlay any active
+  subtitles or captions.</p>
 <!--TT-->
 
   <p class=note>Resizing <code><a href=#video>video</a></code> and <code><a href=#the-canvas-element>canvas</a></code>

Modified: source
===================================================================
--- source	2010-07-22 20:18:42 UTC (rev 5189)
+++ source	2010-07-22 22:44:09 UTC (rev 5190)
@@ -31585,10 +31585,14 @@
   context menu.</p>
 
   <p>Where possible (specifically, for starting, stopping, pausing,
-  and unpausing playback, for muting or changing the volume of the
-  audio, and for seeking), user interface features exposed by the user
-  agent must be implemented in terms of the DOM API described above,
-  so that, e.g., all the same events fire.</p>
+  and unpausing playback, for seeking,
+<!--END w3c-html--><!--TT-->
+  for listing, enabling, and disabling timed tracks,
+<!--START w3c-html--><!--TT-->
+  and for muting or changing the volume of the audio), user interface
+  features exposed by the user agent must be implemented in terms of
+  the DOM API described above, so that, e.g., all the same events
+  fire.</p>
 
   <p>The <dfn title="dom-media-controls"><code>controls</code></dfn>
   IDL attribute must <span>reflect</span> the content attribute of the
@@ -98802,6 +98806,11 @@
   on top of their <code>video</code> element, as defined by the
   relevant rendering rules; for <span>WebSRT</span>, those are the
   <span>WebSRT cue text rendering rules</span> defined below.</p>
+
+  <p>When <span title="expose a user interface to the user">exposing a
+  user interface</span> for a <code>video</code> element, user agents
+  should attempt to position controls so as to not overlay any active
+  subtitles or captions.</p>
 <!--START w3c-html--><!--TT-->
 
   <p class="note">Resizing <code>video</code> and <code>canvas</code>