W3C home > Mailing lists > Public > public-html-diffs@w3.org > February 2009

spec/Overview.html 1.2035 2864 Remove some notes that were intended for

From: poot <cvsmail@w3.org>
Date: Tue, 24 Feb 2009 11:30:16 +0900 (JST)
To: public-html-diffs@w3.org
Message-Id: <20090224023016.5ED332BBFE@toro.w3.mag.keio.ac.jp>
Remove some notes that were intended for the rendering section but which
are now addressed; address others. (whatwg r2864)

Index
http://people.w3.org/mike/diffs/html5/spec/Overview.1.2035.html#index
videoHeight
http://people.w3.org/mike/diffs/html5/spec/Overview.1.2035.html#dom-video-videoheight
4.10.4.2.4 The size attribute
http://people.w3.org/mike/diffs/html5/spec/Overview.1.2035.html#the-size-attribute
size
http://people.w3.org/mike/diffs/html5/spec/Overview.1.2035.html#attr-select-size
4.8.7.1 Video and audio codecs for video elements
http://people.w3.org/mike/diffs/html5/spec/Overview.1.2035.html#video-and-audio-codecs-for-video-elements
required
http://people.w3.org/mike/diffs/html5/spec/Overview.1.2035.html#concept-input-required
4.10.4.2.5 The required attribute
http://people.w3.org/mike/diffs/html5/spec/Overview.1.2035.html#the-required-attribute
10.3.2 Images
http://people.w3.org/mike/diffs/html5/spec/Overview.1.2035.html#images-0
10.3 Replaced elements
http://people.w3.org/mike/diffs/html5/spec/Overview.1.2035.html#replaced-elements

http://people.w3.org/mike/diffs/html5/spec/Overview.diff.html
http://dev.w3.org/cvsweb/html5/spec/Overview.html?r1=1.2034&r2=1.2035&f=h
http://html5.org/tools/web-apps-tracker?from=2863&to=2864

===================================================================
RCS file: /sources/public/html5/spec/Overview.html,v
retrieving revision 1.2034
retrieving revision 1.2035
diff -u -d -r1.2034 -r1.2035
--- Overview.html	24 Feb 2009 02:19:41 -0000	1.2034
+++ Overview.html	24 Feb 2009 02:27:03 -0000	1.2035
@@ -14626,8 +14626,7 @@
   controls, even if the <code title=attr-media-controls><a href=#attr-media-controls>controls</a></code> attribute is absent.<p>User agents may allow video playback to affect system features
   that could interfere with the user's experience; for example, user
   agents could disable screensavers while video playback is in
-  progress.</p><!-- XXX rendering section should mention that resizing a video
-  should in no way interrupt playback --><p class=warning>User agents should not provide a public API to
+  progress.<p class=warning>User agents should not provide a public API to
   cause videos to be shown full-screen. A script, combined with a
   carefully crafted video file, could trick the user into thinking a
   system-modal dialog had been shown, and prompt the user for a
@@ -14635,12 +14634,7 @@
   launching full-screen videos when links are clicked or pages
   navigated. Instead, user-agent specific interface features may be
   provided to easily allow the user to obtain a full-screen playback
-  mode.<p class=XXX>The spec does not currently define the
-  interaction of the "controls" attribute with the "height" and
-  "width" attributes. This will likely be defined in the rendering
-  section based on implementation experience. So far, browsers seem to
-  be making the controls overlay-only, thus somewhat sidestepping the
-  issue.<h5 id=video-and-audio-codecs-for-video-elements><span class=secno>4.8.7.1 </span>Video and audio codecs for <code><a href=#video>video</a></code> elements</h5><p>User agents may support any video and audio codecs and container
+  mode.<h5 id=video-and-audio-codecs-for-video-elements><span class=secno>4.8.7.1 </span>Video and audio codecs for <code><a href=#video>video</a></code> elements</h5><p>User agents may support any video and audio codecs and container
   formats.<p class=XXX>It would be helpful for interoperability if all
   browsers could support the same codecs. However, there are no known
   codecs that satisfy all the current players: we need a codec that is
@@ -23466,8 +23460,7 @@
   integer</a> greater than zero.<p>If the attribute is present, then its value must be parsed using
   the <a href=#rules-for-parsing-non-negative-integers>rules for parsing non-negative integers</a>, and if the
   result is a number greater than zero, then the user agent should
-  ensure that at least that many characters are visible.<p class=XXX>The rendering section will define this in more
-  detail.<p>The <code title=dom-input-size><a href=#dom-input-size>size</a></code> DOM attribute
+  ensure that at least that many characters are visible.<p>The <code title=dom-input-size><a href=#dom-input-size>size</a></code> DOM attribute
   <a href=#limited-to-only-positive-non-zero-numbers>limited to only positive non-zero numbers</a>.<h6 id=the-required-attribute><span class=secno>4.10.4.2.5 </span>The <code title=attr-input-required><a href=#attr-input-required>required</a></code> attribute</h6><p>The <dfn id=attr-input-required title=attr-input-required><code>required</code></dfn>
   attribute is a <a href=#boolean-attribute>boolean attribute</a>. When specified, the
   element is <dfn id=concept-input-required title=concept-input-required><i>required</i></dfn>.<p><strong>Constraint validation:</strong> If the element is <i title=concept-input-required><a href=#concept-input-required>required</a></i>, and its <code title=dom-input-value><a href=#dom-input-value>value</a></code> DOM attribute applies and is in
@@ -23993,15 +23986,7 @@
   then the <code title=attr-input-size><a href=#attr-input-size>size</a></code> attribute's
   default value is 4. If the <code title=attr-select-multiple><a href=#attr-select-multiple>multiple</a></code> attribute is absent,
   then the <code title=attr-input-size><a href=#attr-input-size>size</a></code> attribute's
-  default value is 1.</p><!-- XXX for the rendering section
-  <p>If the <code title="attr-select-multiple">multiple</code>
-  attribute is absent, and either the <code
-  title="attr-input-size">size</code> attribute is also absent or
-  parsing its value using the <span>rules for parsing non-negative
-  integers</span> returns 1, 0, or an error, then the control should
-  be rendered as a drop-down select box. Otherwise, it should be
-  rendered as a list select box.</p>
-  --><p>If the <code title=attr-select-multiple><a href=#attr-select-multiple>multiple</a></code>
+  default value is 1.<p>If the <code title=attr-select-multiple><a href=#attr-select-multiple>multiple</a></code>
   attribute is absent, and the element is not <a href=#concept-fe-disabled title=concept-fe-disabled>disabled</a>, then the user agent
   should allow the user to pick an <code><a href=#the-option-element>option</a></code> element in its
   <a href=#concept-select-option-list title=concept-select-option-list>list of options</a> that
@@ -48134,7 +48119,12 @@
   elements are expected to be treated as ordinary elements in the
   rendering model.<p>The <code><a href=#audio>audio</a></code> element, when it has a <code title=attr-media-controls><a href=#attr-media-controls>controls</a></code> attribute, is expected
   to be treated as a replaced element about one line high, as wide as
-  is necessary to expose the user agent's user interface features.</p><hr><p>The following CSS rules are expected to apply:<pre class=css>@namespace url(http://www.w3.org/1999/xhtml);
+  is necessary to expose the user agent's user interface features.<p>The <code><a href=#video>video</a></code> element's <code title=attr-media-controls><a href=#attr-media-controls>controls</a></code> attribute is not
+  expected to affect the size of the rendering; controls are expected
+  to be overlaid with the page content without causing any layout
+  changes, and are expected to disappear when the user does not need
+  them.<p class=note>Resizing <code><a href=#video>video</a></code> and <code><a href=#the-canvas-element>canvas</a></code>
+  elements does not interrupt video playback or clear the canvas.</p><hr><p>The following CSS rules are expected to apply:<pre class=css>@namespace url(http://www.w3.org/1999/xhtml);
 
 iframe { border: 2px inset; }</pre><h4 id=images-0><span class=secno>10.3.2 </span>Images</h4><p>When an <code><a href=#the-img-element>img</a></code> element or an <code><a href=#the-input-element>input</a></code> element
   when its <code title=attr-input-type><a href=#attr-input-type>type</a></code> attribute is in
@@ -49441,4 +49431,6 @@
         - or on the radio button itself
         - or both, so it works even when the form controls have names
           that vary more than HTMLFormControlCollection allows?
+ XXX * should check all cases of 'active document' and change the
+       relevant ones to 'fully active document'.
 -->
Received on Tuesday, 24 February 2009 02:30:52 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Saturday, 18 December 2010 06:13:58 GMT