- From: poot <cvsmail@w3.org>
- Date: Fri, 17 Jun 2011 05:55:19 -0400
- To: public-html-diffs@w3.org
hixie: cvs problem
http://dev.w3.org/cvsweb/html5/spec/Overview.html?r1=1.4949&r2=1.4950&f=h
===================================================================
RCS file: /sources/public/html5/spec/Overview.html,v
retrieving revision 1.4949
retrieving revision 1.4950
diff -u -d -r1.4949 -r1.4950
--- Overview.html 2 Jun 2011 14:59:56 -0000 1.4949
+++ Overview.html 2 Jun 2011 23:49:02 -0000 1.4950
@@ -188,43 +188,7 @@
fieldset > :last-child { margin-bottom: 0; }
fieldset p { margin: 0.5em 0; }
- .stability {
- position: fixed;
- bottom: 0;
- left: 0; right: 0;
- margin: 0 auto 0 auto;
- width: 50%;
- background: maroon; color: yellow;
- -webkit-border-radius: 1em 1em 0 0;
- -moz-border-radius: 1em 1em 0 0;
- border-radius: 1em 1em 0 0;
- -moz-box-shadow: 0 0 1em #500;
- -webkit-box-shadow: 0 0 1em #500;
- box-shadow: 0 0 1em red;
- padding: 0.5em 1em;
- text-align: center;
- }
- .stability strong {
- display: block;
- }
- .stability input {
- appearance: none; margin: 0; border: 0; padding: 0.25em 0.5em; background: transparent; color: black;
- position: absolute; top: -0.5em; right: 0; font: 1.25em sans-serif; text-align: center;
- }
- .stability input:hover {
- color: white;
- text-shadow: 0 0 2px black;
- }
- .stability input:active {
- padding: 0.3em 0.45em 0.2em 0.55em;
- }
- .stability :link, .stability :visited,
- .stability :link:hover, .stability :visited:hover {
- background: transparent;
- color: white;
- }
-
- </style><link href="http://www.w3.org/StyleSheets/TR/W3C-LC" rel="stylesheet" type="text/css"><style type="text/css">
+ </style><link href="http://www.w3.org/StyleSheets/TR/W3C-ED" rel="stylesheet" type="text/css"><style type="text/css">
.applies thead th > * { display: block; }
.applies thead code { display: block; }
@@ -354,15 +318,14 @@
<h1>HTML5</h1>
<h2 class="no-num no-toc" id="a-vocabulary-and-associated-apis-for-html-and-xhtml">A vocabulary and associated APIs for HTML and XHTML</h2>
- <h2 class="no-num no-toc" id="w3c-working-draft-24-may-2011">W3C Working Draft 24 May 2011</h2>
- <dl><dt>This Version:</dt>
- <dd><a href="http://www.w3.org/TR/2011/WD-html5-20110524/">http://www.w3.org/TR/2011/WD-html5-20110524/</a></dd>
- <dt>Latest Published Version:</dt>
+ <h2 class="no-num no-toc" id="editor-s-draft-2-june-2011">Editor's Draft 2 June 2011</h2>
+ <dl><dt>Latest Published Version:</dt>
<dd><a href="http://www.w3.org/TR/html5/">http://www.w3.org/TR/html5/</a></dd>
<dt>Latest Editor's Draft:</dt>
<dd><a class="latest-link" href="http://dev.w3.org/html5/spec/Overview.html">http://dev.w3.org/html5/spec/Overview.html</a></dd>
<dt>Previous Versions:</dt>
+ <dd><a href="http://www.w3.org/TR/2011/WD-html5-20110525/">http://www.w3.org/TR/2011/WD-html5-20110525/</a></dd>
<dd><a href="http://www.w3.org/TR/2011/WD-html5-20110405/">http://www.w3.org/TR/2011/WD-html5-20110405/</a></dd>
<dd><a href="http://www.w3.org/TR/2011/WD-html5-20110113/">http://www.w3.org/TR/2011/WD-html5-20110113/</a></dd>
<dd><a href="http://www.w3.org/TR/2010/WD-html5-20101019/">http://www.w3.org/TR/2010/WD-html5-20101019/</a></dd>
@@ -426,22 +389,23 @@
<p class="note">Please don't use section numbers as these tend to
change rapidly and make your feedback harder to understand.</p>
<script type="text/javascript">
- function checkFeedbackForm(form) {
- if (form.elements.text.value.match(/^ *</)) {
- alert('Please don\'t start your feedback with an angle bracket, instead explain what topic your feedback is about first.');
- return true;
- } else if (form.elements.text.value.match(/ [^ ]+ [^ ]+ [^ ]+ [^ ]+ /)) {
- if (form.elements.text.value.match(/^Please enter your feedback, carefully/)) {
- alert('Please enter your feedback, explaining what is wrong, and without repeating the instructions. Thanks!');
- return true;
- } else if (form.elements.text.value.match(/ [^ ]+ [^ ]+ [^ ]+ [^ ]+ /)) {
- form.action = "http://www.whatwg.org/specs/web-apps/current-work/file-bug.cgi";
- return true;
- } else {
- alert('Please include significantly more detail about exactly what problem you are trying to solve.');
- return false;
- }
- }
+ function checkFeedbackForm(form) {
+ if (form.elements.text.value.match(/^ *</)) {
+ alert('Please don\'t start your feedback with an angle bracket, instead explain what topic your feedback is about first.');
+ return true;
+ } else if (form.elements.text.value.match(/ [^ ]+ [^ ]+ [^ ]+ [^ ]+ /)) {
+ if (form.elements.text.value.match(/^Please enter your feedback, carefully/)) {
+ alert('Please enter your feedback, explaining what is wrong, and without repeating the instructions. Thanks!');
+ return true;
+ } else if (form.elements.text.value.match(/ [^ ]+ [^ ]+ [^ ]+ [^ ]+ /)) {
+ form.action = "http://www.whatwg.org/specs/web-apps/current-work/file-bug.cgi";
+ return true;
+ } else {
+ alert('Please include significantly more detail about exactly what problem you are trying to solve.');
+ return false;
+ }
+ }
+ }
</script><p>
<input onclick="return checkFeedbackForm(form)" type="submit" value="Submit feedback"><small>(Note: Your IP address and user agent will be publicly recorded for spam prevention purposes.)</small>
</p>
@@ -473,22 +437,7 @@
implementing this specification before it eventually reaches the
Candidate Recommendation stage should join the aforementioned
mailing lists and take part in the discussions.<div id="multipage-common">
-
-
- <p class="stability" id="wip"><strong>This is a work in
- progress!</strong> For the latest updates from the HTML WG, possibly
- including important bug fixes, please look at the <a href="http://dev.w3.org/html5/spec/Overview.html">editor's draft</a> instead.
- <input onclick="closeWarning(this.parentNode)" type="button" value="╳⃝"></p>
- <script type="text/javascript">
- function closeWarning(element) {
- element.parentNode.removeChild(element);
- var date = new Date();
- date.setDate(date.getDate()+4);
- document.cookie = 'hide-obsolescence-warning=1; expires=' + date.toGMTString();
- }
- if (getCookie('hide-obsolescence-warning') == '1')
- setTimeout(function () { document.getElementById('wip').parentNode.removeChild(document.getElementById('wip')); }, 2000);
- </script></div><p>The publication of this document by the W3C as a W3C Working
+ </div><p>The publication of this document by the W3C as a W3C Working
Draft does not imply that all of the participants in the W3C HTML
working group endorse the contents of the specification. Indeed, for
any section of the specification, one can usually find many members
@@ -515,7 +464,7 @@
Group</a> is the W3C working group responsible for this
specification's progress along the W3C Recommendation
track.
- This specification is the 24 May 2011 Working Draft.
+ This specification is the 2 June 2011 Editor's Draft.
</p><!-- UNDER NO CIRCUMSTANCES IS THE PRECEDING PARAGRAPH TO BE REMOVED OR EDITED WITHOUT TALKING TO IAN FIRST --><p>Work on this specification is also done at the <a href="http://www.whatwg.org/">WHATWG</a>. The W3C HTML working group
actively pursues convergence with the WHATWG, as required by the <a href="http://www.w3.org/2007/03/HTML-WG-charter">W3C HTML working
group charter</a>.</p><!-- UNDER NO CIRCUMSTANCES IS THE FOLLOWING PARAGRAPH TO BE REMOVED OR EDITED WITHOUT TALKING TO IAN FIRST --><p>This document was produced by a group operating under the <a href="http://www.w3.org/Consortium/Patent-Policy-20040205/">5
@@ -1508,12 +1457,13 @@
the specification under the W3C copyright, while keeping a version
with the less restrictive license on the WHATWG site.<p>Since then, both groups have been working together.</p><p>The <a href="http://www.whatwg.org/specs/web-apps/current-work/">HTML
specification</a> published by the WHATWG is not identical to
- this specification. At the time of this publication, the main
- differences were that the WHATWG version included features not
- included in this W3C version: some features have been omitted, but
- may be considered for future revisions of HTML beyond HTML5; and
- other features were omitted because at the W3C they are published as
- separate specifications.</p><p>A separate document has been published by the W3C HTML working
+ this specification. The main differences are that the WHATWG version
+ includes features not included in this W3C version: some features
+ have been omitted as they are considered part of future revisions of
+ HTML, not HTML5; and other features are omitted because at the W3C
+ they are published as separate specifications. There are also some
+ minor differences. For an exact list of differences, please see the
+ WHATWG specification.</p><p>A separate document has been published by the W3C HTML working
group to document the differences between this specification and the
language described in the HTML4 specification. <a href="#refsHTMLDIFF">[HTMLDIFF]</a><h3 id="design-notes"><span class="secno">1.5 </span>Design notes</h3><p><i>This section is non-normative.</i><p>It must be admitted that many aspects of HTML appear at first
glance to be nonsensical and inconsistent.<p>HTML, its supporting DOM APIs, as well as many of its supporting
@@ -2983,8 +2933,9 @@
required for conforming IDL fragments, as described in the Web IDL
specification. <a href="#refsWEBIDL">[WEBIDL]</a></p>
- <p>The terms <dfn id="supported-property-indices">supported property indices</dfn> and
- <dfn id="supported-property-names">supported property names</dfn> are used as defined in the
+ <p>The terms <dfn id="supported-property-indices">supported property indices</dfn>, <dfn id="supported-property-names">supported
+ property names</dfn>, and <dfn id="dfn-read-only-array" title="dfn-read-only-array">read
+ only</dfn> (when applied to arrays) are used as defined in the
WebIDL specification.</p>
<p id="float-nan">Except where otherwise specified, if an IDL
@@ -3046,11 +2997,20 @@
</dd>
+ <dt>Cookies</dt>
+
+ <dd>
+
+ <p>The following term is defined in the Cookie specification: <a href="#refsCOOKIES">[COOKIES]</a></p>
+
+ <ul class="brief"><li><dfn id="receives-a-set-cookie-string">Receives a set-cookie-string</dfn>
+ </ul></dd>
+
<dt>CORS</dt>
<dd>
- <p>The following terms are defined in the CORS specification:</p>
+ <p>The following terms are defined in the CORS specification: <a href="#refsCORS">[CORS]</a></p>
<ul class="brief"><li><dfn id="cross-origin-request">cross-origin request</dfn>
<li><dfn id="cross-origin-request-status">cross-origin request status</dfn>
@@ -3086,6 +3046,7 @@
</dd>
+
</dl><p>This specification does not <em>require</em> support of any
particular network protocol, style sheet language, scripting
language, or any of the DOM specifications beyond those described
@@ -7812,8 +7773,8 @@
<a href="#origin">origin</a> is not a scheme/host/port tuple, the user agent
must raise a <code><a href="#security_err">SECURITY_ERR</a></code> exception. Otherwise, the
user agent must <a href="#obtain-the-storage-mutex">obtain the storage mutex</a> and then act
- as it would when <span title="receives a
- set-cookie-string">receiving a set-cookie-string</span> for
+ as it would when <a href="#receives-a-set-cookie-string" title="receives a
+ set-cookie-string">receiving a set-cookie-string</a> for
<a href="#the-document-s-address">the document's address</a> via a "non-HTTP" API, consisting
of the new value encoded as UTF-8. <a href="#refsCOOKIES">[COOKIES]</a> <a href="#refsRFC3629">[RFC3629]</a></p>
@@ -8575,7 +8536,7 @@
attribute DOMString <a href="#dom-accesskey" title="dom-accessKey">accessKey</a>;
readonly attribute DOMString <a href="#dom-accesskeylabel" title="dom-accessKeyLabel">accessKeyLabel</a>;
attribute boolean <a href="#dom-draggable" title="dom-draggable">draggable</a>;
- [PutForwards=<a href="#dom-domsettabletokenlist-value" title="dom-DOMSettableTokenList-value">value</a>] attribute <a href="#domsettabletokenlist">DOMSettableTokenList</a> <a href="#dom-dropzone" title="dom-dropzone">dropzone</a>;
+ [PutForwards=<a href="#dom-domsettabletokenlist-value" title="dom-DOMSettableTokenList-value">value</a>] readonly attribute <a href="#domsettabletokenlist">DOMSettableTokenList</a> <a href="#dom-dropzone" title="dom-dropzone">dropzone</a>;
attribute DOMString <a href="#dom-contenteditable" title="dom-contentEditable">contentEditable</a>;
readonly attribute boolean <a href="#dom-iscontenteditable" title="dom-isContentEditable">isContentEditable</a>;
attribute <a href="#htmlmenuelement">HTMLMenuElement</a> <a href="#dom-contextmenu" title="dom-contextMenu">contextMenu</a>;
@@ -12510,8 +12471,8 @@
<li><p><a href="#obtain-the-storage-mutex">Obtain the storage mutex</a>.</li>
- <li><p>Act as if <span title="receives a
- set-cookie-string">receiving a set-cookie-string</span> for
+ <li><p>Act as if <a href="#receives-a-set-cookie-string" title="receives a
+ set-cookie-string">receiving a set-cookie-string</a> for
<a href="#the-document-s-address">the document's address</a> via a "non-HTTP" API,
consisting of the value of the element's <code title="attr-meta-content"><a href="#attr-meta-content">content</a></code> attribute encoded as
UTF-8. <a href="#refsCOOKIES">[COOKIES]</a> <a href="#refsRFC3629">[RFC3629]</a></li>
@@ -21884,10 +21845,11 @@
spaces</a>. This attribute must be present.<p class="note">Dynamically modifying a <code><a href="#the-source-element">source</a></code> element
and its attribute when the element is already inserted in a
<code><a href="#the-video-element">video</a></code> or <code><a href="#the-audio-element">audio</a></code> element will have no
- effect. To change what is playing, either just use the <code title="attr-media-src"><a href="#attr-media-src">src</a></code> attribute on the <a href="#media-element">media
- element</a> directly, or call the <code title="dom-media-load"><a href="#dom-media-load">load()</a></code> method on the <a href="#media-element">media
- element</a> after manipulating the <code><a href="#the-source-element">source</a></code>
- elements.<p>The <dfn id="attr-source-type" title="attr-source-type"><code>type</code></dfn>
+ effect. To change what is playing, just use the <code title="attr-media-src"><a href="#attr-media-src">src</a></code> attribute on the <a href="#media-element">media
+ element</a> directly, possibly making use of the <code title="dom-navigator-canPlayType"><a href="#dom-navigator-canplaytype">canPlayType()</a></code> method to
+ pick from amongst available resources. Generally, manipulating
+ <code><a href="#the-source-element">source</a></code> elements manually after the document has been
+ parsed is an unncessarily complicated approach.<p>The <dfn id="attr-source-type" title="attr-source-type"><code>type</code></dfn>
attribute gives the type of the <a href="#media-resource">media resource</a>, to help
the user agent determine if it can play this <a href="#media-resource">media
resource</a> before fetching it. If specified, its value must be
@@ -23524,8 +23486,9 @@
resource</a>, in seconds, on the <a href="#media-timeline">media timeline</a>. If
no <a href="#media-data">media data</a> is available, then the attributes must
return the Not-a-Number (NaN) value. If the <a href="#media-resource">media
- resource</a> is known to be unbounded (e.g. a streaming radio),
- then the attribute must return the positive Infinity value.</p>
+ resource</a> is not known to be bounded (e.g. streaming radio, or
+ a live event with no announced end time), then the attribute must
+ return the positive Infinity value.</p>
<p>The user agent must determine the duration of the <a href="#media-resource">media
resource</a> before playing any part of the <a href="#media-data">media
@@ -40154,22 +40117,24 @@
child of the element, if any, <a href="#represents">represents</a> the summary or
legend of the details. <span class="impl">If there is no child
<code><a href="#the-summary-element">summary</a></code> element, the user agent should provide its own
- legend (e.g. "Details").</span><p>The <dfn id="attr-details-open" title="attr-details-open"><code>open</code></dfn>
+ legend (e.g. "Details").</span><p>The rest of the element's contents <a href="#represents">represents</a> the
+ additional information or controls.<p>The <dfn id="attr-details-open" title="attr-details-open"><code>open</code></dfn>
content attribute is a <a href="#boolean-attribute">boolean attribute</a>. If present,
- it indicates that the details are to be shown to the user. If the
- attribute is absent, the details are not to be shown.<div class="impl">
+ it indicates that both the summary and the additional information is
+ to be shown to the user. If the attribute is absent, only the
+ summary is to be shown.<div class="impl">
<p>When the element is created, if the attribute is absent, the
- details should be hidden; if the attribute is absent, the details
- should be shown. Subsequently, if the attribute is removed, then the
- details should be hidden; if the attribute is added, the details
- should be shown.</p>
+ additional information should be hidden; if the attribute is absent,
+ that information should be shown. Subsequently, if the attribute is
+ removed, then the information should be hidden; if the attribute is
+ added, the information should be shown.</p>
- <p>The user agent should allow the user to request that the details
- be shown or hidden. To honor a request for the details to be shown,
- the user agent must set the <code title="attr-details-open"><a href="#attr-details-open">open</a></code> attribute on the element to
+ <p>The user agent should allow the user to request that the
+ additional information be shown or hidden. To honor a request for
+ the details to be shown, the user agent must set the <code title="attr-details-open"><a href="#attr-details-open">open</a></code> attribute on the element to
the value <code title="">open</code>. To honor a request for the
- details to be hidden, the user agent must remove the <code title="attr-details-open"><a href="#attr-details-open">open</a></code> attribute from the
+ information to be hidden, the user agent must remove the <code title="attr-details-open"><a href="#attr-details-open">open</a></code> attribute from the
element.</p>
<p>The <dfn id="dom-details-open" title="dom-details-open"><code>open</code></dfn> IDL
@@ -42866,13 +42831,16 @@
<code><a href="#windowproxy">WindowProxy</a></code> object forwards everything to the
<a href="#browsing-context">browsing context</a>'s <a href="#active-document">active document</a>'s
<code><a href="#window">Window</a></code> object.<p class="note">In general, there is a 1-to-1 mapping from the
- <code><a href="#window">Window</a></code> object to the <code><a href="#document">Document</a></code> object. In
- one particular case, a <code><a href="#window">Window</a></code> can be reused for the
- presentation of a second <code><a href="#document">Document</a></code> in the same
- <a href="#browsing-context">browsing context</a>, such that the mapping is then
- 2-to-1. This occurs when a <a href="#browsing-context">browsing context</a> is <a href="#navigate" title="navigate">navigated</a> from the initial
+ <code><a href="#window">Window</a></code> object to the <code><a href="#document">Document</a></code> object.
+ There are two exceptions. First, a <code><a href="#window">Window</a></code> can be reused
+ for the presentation of a second <code><a href="#document">Document</a></code> in the same
+ <a href="#browsing-context">browsing context</a>, such that the mapping is then 2-to-1.
+ This occurs when a <a href="#browsing-context">browsing context</a> is <a href="#navigate" title="navigate">navigated</a> from the initial
<code><a href="#about:blank">about:blank</a></code> <code><a href="#document">Document</a></code> to another, with
- <a href="#replacement-enabled">replacement enabled</a>.<p class="note">A <code><a href="#document">Document</a></code> does not necessarily have a
+ <a href="#replacement-enabled">replacement enabled</a>. Second, a <code><a href="#document">Document</a></code>
+ can end up being reused for several <code><a href="#window">Window</a></code> objects when
+ the <code title="dom-document-open"><a href="#dom-document-open">document.open()</a></code> method is
+ used, such that the mapping is then 1-to-many.<p class="note">A <code><a href="#document">Document</a></code> does not necessarily have a
<a href="#browsing-context">browsing context</a> associated with it. In particular,
data mining tools are likely to never instantiate browsing
contexts.<hr><p>A <a href="#browsing-context">browsing context</a> can have a <dfn id="creator-browsing-context">creator browsing
@@ -46449,15 +46417,33 @@
</ol><p>This specification defines the following <dfn id="unloading-document-cleanup-steps">unloading document
cleanup steps</dfn>. Other specifications can define more.</p>
- <ol><li><p><span>Close the WebSocket connection</span> of any
- <code>WebSocket</code> objects that were created by the <code title="dom-WebSocket">WebSocket()</code> constructor visible on the
- <code><a href="#document">Document</a></code>'s <code><a href="#window">Window</a></code> object. If this
- affected any <code>WebSocket</code> objects, the set
- <code><a href="#document">Document</a></code>'s <var title="concept-document-salvageable">salvageable</var> state to
- false.
-
- <a href="#refsWEBSOCKET">[WEBSOCKET]</a>
-
+ <ol><li>
+
+ <p><span>Make disappear</span> any <code>WebSocket</code> objects
+ that were created by the <code title="dom-WebSocket">WebSocket()</code> constructor whose global
+ object is the <code><a href="#document">Document</a></code>'s <code><a href="#window">Window</a></code> object.
+
+
+ <a href="#refsWEBSOCKET">[WEBSOCKET]</a>
+
+
+ </p>
+
+ <p>If this affected any <code>WebSocket</code> objects, the set
+ <code><a href="#document">Document</a></code>'s <var title="concept-document-salvageable">salvageable</var> state to
+ false.</p>
+
+ </li>
+
+ <li>
+
+ <p>If the <code><a href="#document">Document</a></code>'s <code><a href="#window">Window</a></code> object <span title="concept-PeerConnection-owner">owns</span> any
+ <code>PeerConnection</code> objects whose
+ <span><code>PeerConnection</code> readiness state</span> is not
+ <code title="dom-PeerConnection-CLOSED">CLOSED</code>, then set
+ <code><a href="#document">Document</a></code>'s <var title="concept-document-salvageable">salvageable</var> state to
+ false.</p>
+
</li>
<li><p>If the <code><a href="#document">Document</a></code>'s <var title="concept-document-salvageable">salvageable</var> state is
@@ -50534,8 +50520,6 @@
interface.</p>
-
-
</div><h5 id="client-identification"><span class="secno">6.5.1.1 </span>Client identification</h5><pre class="idl">[Supplemental, NoInterfaceObject]
interface <dfn id="navigatorid">NavigatorID</dfn> { readonly attribute DOMString <a href="#dom-navigator-appname" title="dom-navigator-appName">appName</a>;
readonly attribute DOMString <a href="#dom-navigator-appversion" title="dom-navigator-appVersion">appVersion</a>;
@@ -51006,17 +50990,13 @@
arbitrarily ignore invocations with particular arguments for
security, privacy, or usability reasons.</li>
- <li><p><a href="#resolve-a-url" title="resolve a url">Resolve</a> the <var title="">scriptURL</var> argument relative to the <a href="#entry-script">entry
+ <li><p><a href="#resolve-a-url" title="resolve a url">Resolve</a> the value of the
+ method's first argument relative to the <a href="#entry-script">entry
script</a>'s <a href="#script-s-base-url" title="script's base URL">base
URL</a>.</li>
<li><p>If this fails, abort these steps.</li>
- <li><p>If the <a href="#origin">origin</a> of the resulting <a href="#absolute-url">absolute
- URL</a> is not the <a href="#same-origin" title="same origin">same</a> as the
- origin of the <a href="#entry-script">entry script</a>, then abort these
- steps.</li>
-
<li><p>Process the resulting <a href="#absolute-url">absolute URL</a> as the
<a href="#url">URL</a> to an OpenSearch description document. <a href="#refsOPENSEARCH">[OPENSEARCH]</a></li>
@@ -64835,10 +64815,15 @@
section. (That section uses some of the variables whose values
were calculated earlier in this algorithm.)</li>
- <li>Text runs must be wrapped at the edge of their containing
- blocks, regardless of the value of the 'white-space' property,
- even if doing so requires splitting a word where there is no
- line breaking opportunity.</li>
+ <li>Text runs must be wrapped according to the CSS
+ line-wrapping rules, except that additionally, regardless of
+ the value of the 'white-space' property, lines must be wrapped
+ at the edge of their containing blocks, even if doing so
+ requires splitting a word where there is no line breaking
+ opportunity. (Thus, normally text wraps as needed, but if there
+ is a particularly long word, it does not overflow as it
+ normally would in CSS, it is instead forcibly wrapped at the
+ box's edge.)</li>
<li>The viewport (and initial containing block) is
<var title="">video</var>'s rendering area.</li>
@@ -65073,7 +65058,13 @@
<li><p>Return <var title="">output</var>.</li>
- </ol><h5 id="applying-css-properties-to-webvtt-node-objects"><span class="secno">10.3.2.2 </span>Applying CSS properties to <span title="WebVTT Node Object">WebVTT Node Objects</span></h5>
+ </ol><p>User agents may allow the user to override the above algorithm's
+ positioning of cues, e.g. by dragging them to another location on
+ the <code><a href="#the-video-element">video</a></code>, or even off the <code><a href="#the-video-element">video</a></code>
+ entirely.</p>
+
+
+ <h5 id="applying-css-properties-to-webvtt-node-objects"><span class="secno">10.3.2.2 </span>Applying CSS properties to <span title="WebVTT Node Object">WebVTT Node Objects</span></h5>
<p>When following the <a href="#rules-for-updating-the-display-of-webvtt-text-tracks">rules for updating the display of WebVTT
text tracks</a>, user agents must set properties of <span title="WebVTT Node Object">WebVTT Node Objects</span> as defined in
@@ -65180,8 +65171,9 @@
ignored:</p>
<ul class="brief"><li>'color'</li>
- <li>'text-shadow'</li>
+ <li>'text-decoration'</li>
<li>'text-outline'</li>
+ <li>'text-shadow'</li>
<li>the properties corresponding to the 'background' shorthand</li>
<li>the properties corresponding to the 'outline' shorthand</li>
<li>the properties corresponding to the 'font' shorthand, including 'line-height'</li>
@@ -65253,20 +65245,26 @@
<li><p>For the purposes of class selector matching, <span title="WebVTT Internal Node Object">WebVTT Internal Node
Objects</span> have the classes described as the <span>WebVTT
Node Object's applicable classes</span>.</li>
+ <li><p>For the purposes of ID selector matching, <span title="List
+ of WebVTT Node Objects">Lists of WebVTT Node Objects</span> have
+ the ID given by the cue's <a href="#text-track-cue-identifier">text track cue identifier</a>,
+ if any.</li>
+
</ul><p>The following properties apply to the '::cue()' pseudo-element
with an argument:</p>
<ul class="brief"><li>'color'</li>
- <li>'text-shadow'</li>
+ <li>'text-decoration'</li>
<li>'text-outline'</li>
+ <li>'text-shadow'</li>
<li>the properties corresponding to the 'background' shorthand</li>
<li>the properties corresponding to the 'outline' shorthand</li>
<li>properties relating to the transition and animation features</li>
- </ul><p>The following properties apply to the '::cue()' pseudo-element
- with an argument when the selector does not contain the ':past' and
- ':future' pseudo-classes:</p>
+ </ul><p>In addition, the following properties apply to the '::cue()'
+ pseudo-element with an argument when the selector does not contain
+ the ':past' and ':future' pseudo-classes:</p>
<ul class="brief"><li>the properties corresponding to the 'font' shorthand, including 'line-height'</li>
Received on Friday, 17 June 2011 09:55:21 UTC