Bug 21855 Added informative clarification about moving from CREATED to READY state.
authorAdrian Bateman <adrianba@microsoft.com>
Mon, 11 Nov 2013 17:39:27 +0800
changeset 197 cba144274140
parent 196 e94250285fdf
child 198 a1b40b65f10e
Bug 21855 Added informative clarification about moving from CREATED to READY state.
encrypted-media/encrypted-media.html
encrypted-media/encrypted-media.xml
--- a/encrypted-media/encrypted-media.html	Thu Nov 07 15:23:10 2013 -0800
+++ b/encrypted-media/encrypted-media.html	Mon Nov 11 17:39:27 2013 +0800
@@ -437,7 +437,11 @@
               <dd>
                 <ol>
                   <li><p>Let the state of the session be <code><a href="#dom-stateready">READY</a></code>.</p></li>
-                  <li><p><a href="http://www.w3.org/TR/html5/webappapis.html#queue-a-task">queue a task</a> to <a href="http://www.w3.org/TR/html5/webappapis.html#fire-a-simple-event">fire a simple event</a> named <code><a href="#dom-eventready">ready</a></code> at the new object.</p></li>
+                  <li>
+                    <p><a href="http://www.w3.org/TR/html5/webappapis.html#queue-a-task">queue a task</a> to <a href="http://www.w3.org/TR/html5/webappapis.html#fire-a-simple-event">fire a simple event</a> named <code><a href="#dom-eventready">ready</a></code> at the new object.</p>
+                    <p class="non-normative">Note: this step makes it possible for a MediaKeySession to transition from the CREATED state to the READY state.
+                    User agents might do this as an optimization but, even if this is done, all MediaKeySession instances must appear distinct regardless of the underlying implementation.</p>
+                  </li>
                 </ol>
               </dd>
             </dl>
--- a/encrypted-media/encrypted-media.xml	Thu Nov 07 15:23:10 2013 -0800
+++ b/encrypted-media/encrypted-media.xml	Mon Nov 11 17:39:27 2013 +0800
@@ -424,7 +424,11 @@
               <dd>
                 <ol>
                   <li><p>Let the state of the session be <coderef prefix="state">READY</coderef>.</p></li>
-                  <li><p><queue-a-task/> to <fire-a-simple-event/> named <coderef prefix="event">ready</coderef> at the new object.</p></li>
+                  <li>
+                    <p><queue-a-task/> to <fire-a-simple-event/> named <coderef prefix="event">ready</coderef> at the new object.</p>
+                    <p class="non-normative">Note: this step makes it possible for a MediaKeySession to transition from the CREATED state to the READY state.
+                    User agents might do this as an optimization but, even if this is done, all MediaKeySession instances must appear distinct regardless of the underlying implementation.</p>
+                  </li>
                 </ol>
               </dd>
             </dl>