- From: Sam Ruby via cvs-syncmail <cvsmail@w3.org>
- Date: Thu, 11 Oct 2012 00:13:11 +0000
- To: public-html-commits@w3.org
Update of /sources/public/html5/srcset
In directory hutz:/tmp/cvs-serv10388
Modified Files:
Overview.html
Log Message:
commit 221161bd6ef401129fda5da6d23cc61d33404cc3
Author: Edward O'Connor <hober0@gmail.com>
Date: Wed Oct 10 16:57:36 2012 -0700
[meta] Fix up publication tool markers.
Index: Overview.html
===================================================================
RCS file: /sources/public/html5/srcset/Overview.html,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -d -r1.2 -r1.3
--- Overview.html 2 Oct 2012 20:43:32 -0000 1.2
+++ Overview.html 11 Oct 2012 00:13:09 -0000 1.3
@@ -324,7 +324,7 @@
<h1>The srcset attribute</h1>
<h2 class="no-num no-toc" id=an-html-extension-for-adaptive-images>An HTML extension for adaptive images</h2>
- <h2 class="no-num no-toc" id="editor's-draft-date-1-january-1970">Editor's Draft 2 October 2012</h2>
+ <h2 class="no-num no-toc" id="editor's-draft-date-1-january-1970">Editor's Draft 11 October 2012</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>
@@ -415,7 +415,7 @@
Group</a> is the W3C working group responsible for this
specification's progress along the W3C Recommendation
track.
- This specification is the 2 October 2012 Editor's Draft.
+ This specification is the 11 October 2012 Editor's Draft.
</p>
@@ -756,8 +756,8 @@
<li>
- <p>Do a <span>potentially CORS-enabled fetch</span> of the
- <span>absolute URL</span> that resulted from the earlier step,
+ <p>Do a <span>potentially CORS-enabled fetch</span><!--FETCH--> of
+ the <span>absolute URL</span> that resulted from the earlier step,
with the <i>mode</i> being the state of the element's <code title=attr-img-crossorigin>crossorigin</code> content attribute,
the <i title="">origin</i> being the <span>origin</span> of the
<code>img</code> element's <code>Document</code>, and the
@@ -797,7 +797,7 @@
source</span> once the resource has been <span title=fetch>fetched</span> must act as appropriate given the
following alternatives:</p>
- <dl class=switch><dt>If the download was successful</dt>
+ <dl class=switch><dt>If the download was successful and the user agent was able to determine the image's width and height</dt>
<dd>Set the <code>img</code> element to the <span title=img-all>completely available</span> state, update the
presentation of the image appropriately, add the image to the
@@ -825,15 +825,14 @@
a simple event</span> named <code title=event-load>load</code>
at the <code>img</code> element.</p>
- <p>If at any point the user agent discovers that the image data is
- corrupted in some fatal way, or that the image data is not in a
- supported file format, then the user agent must set the
- <code>img</code> element to the <span title=img-error>broken</span> state. If the <span title=fetch>fetching</span> algorithm is still running for this
- element, then the user agent must also abort that algorithm,
- discarding any pending <span title=concept-task>tasks</span>
- generated by that algorithm, and then <span>queue a task</span> to
- <span>fire a simple event</span> named <code title=event-error>error</code> at the <code>img</code>
- element.</p>
+ <p>Otherwise, either the image data is corrupted in some fatal way
+ such that the image dimensions cannot be obtained, or the image
+ data is not in a supported file format; the user agent must set
+ the <code>img</code> element to the <span title=img-error>broken</span> state, abort the <span title=fetch>fetching</span> algorithm, discarding any pending
+ <span title=concept-task>tasks</span> generated by that
+ algorithm, and then <span>queue a task</span> to <span>fire a
+ simple event</span> named <code title=event-error>error</code>
+ at the <code>img</code> element.</p>
</li>
@@ -1105,10 +1104,10 @@
<li>
- <p>Do a <span>potentially CORS-enabled fetch</span> of the
- resulting <span>absolute URL</span>, with the <i>mode</i> being
- <var title="">CORS mode</var>, the <i title="">origin</i> being
- the <span>origin</span> of the <code>img</code> element's
+ <p>Do a <span>potentially CORS-enabled fetch</span><!--FETCH--> of
+ the resulting <span>absolute URL</span>, with the <i>mode</i>
+ being <var title="">CORS mode</var>, the <i title="">origin</i>
+ being the <span>origin</span> of the <code>img</code> element's
<code>Document</code>, and the <i>default origin behaviour</i> set
to <i>taint</i>.</p>
@@ -1298,154 +1297,4 @@
<p>Thanks to Ian Hickson, who specified the <code>srcset</code>
attribute in the WHATWG HTML Living Standard. See that document for
- other relevant acknowledgements. <a href=#refsHTML>[HTML]</a></p>
-
-<!--
- v2 * library of resources:
- var library = new ZipFile("data.zip");
- library.onload = function() {
- var sound1 = library.getAudio("sound1.wav"); // returns an Audio object
- var image1 = library.getImage("image1.png"); // returns an HTMLImageElement
- var doc1 = library.getXMLDocument("doc1.xml"); // returns a Document (XML Document mode)
- var doc2 = library.getHTMLDocument("doc1.html"); // returns a Document (HTML Document mode)
- }
- or:
- var library = new ResourceLoader("data.zip");
- library.add("moredata.zip");
- library.onload = function() { ... }
- library.onloading = function() {
- reportLoadProgress(library.progress); // 0.0 .. 1.0
- }
- or:
- var library = new AudioZip("sounds.zip");
- library.onload = function() {
- var sound1 = library["sound1.wav"];
- sound.play();
- }
- v2 * a fairly common situation for web authors is to have two lists, where
- the contents of the second depends on the value of the first. Is there
- any way we could extend the current model to include this functionality?
- (e.g. bugzilla product/component ui)
- v2 * quick-searchable select
- v2 * include/exclude selectors (two multi-select columns with arrows to
- move selected items) and that sort of thing.
- http://slashdot.org/comments.pl?sid=110240&cid=9357022
- v2 * Oh, and forms need a standardized Help widget/icon. I know I can
- turn my cursor into a question mark, but I'm looking for something
- simple and pervasive. Maybe you can wrap fields in a help tag, just
- as you do for fieldsets. And in that help tag, attributes are
- available that allow for a nice, formatted, clean, full help text
- popup/area/thing.
- http://slashdot.org/comments.pl?sid=110240&cid=9359006
- v2 * Validating only part of a form. - Anja Lehmann
- v2 * Reminder to add a way to expose access keys in buttons, i.e.
- Sub&mit where & signifies the m is the access key to use. Possibly
- automatic? <input accesskey="m" value="Submit"> browser would be
- smart enough to underline the first instance of the access key if
- it exists (case insensitive)? - kerz
- [or deprecate the lot (->web apps)]
- v2 * need an attribute that says "the children of this element are in
- their own tabbing universe, tabindex should be relative to each
- other, not to the document"
- -> web apps?
- v2 * make select widgets have multiple columns
- or ->web apps with list view
- v2 * required as a group (one of the following must be available):
- + i propose something like the following:
- <input type="text" group="contact" name="voicephone"> Voice phone
- <input type="text" group="contact" name="fax"> Fax
- <input type="text" group="contact" name="mobile"> Mobile phone
- <input type="text" group="contact" name="email"> E-mail
- if the user fills out none of the form fields in the "contact"
- group, an error message is shown and the form is not submitted.
- - Peter-Paul Koch
- v2 * formatting of number fields, text fields, etc, so that when the
- field is not focused, the value is displayed differently. Seems
- like this would also be useful e.g. for <output> or something so
- you can display localised dates, etc.
- v2 * being able to select date range (from day x to day y)
- v2 * ways of visualizing a linefeed in a <textarea> so it looks different
- from wrapping text
- v2 * all login systems have
- 1. enter username and password
- 2. create new account
- 3. lost password
- some way of integrating this into one system, since it's so common
- v2 * way of identifying different sorts of mailadresses
- a) mailing-list
- b) person
- c) department in a company ("support", "marketing" and such)
- d) general mail (like "info", "mail", "contact" and such)
- e) other sorts of groupings
- (or ->web apps; this is talking about in mailto: links, I think)
- v2 * hotswapping login identities like in windows xp
- you are logged in on operamail.com, and you want to check the mail
- of another user. somehow, combined with the wand or whatever,
- the browser will remember the login page, and it can re-submit it
- without having to load the initial page (saving time)
- v2 * provide different measuring systems, like having the html indicate
- fluid in both fluid ounces and liters, and the browser can display
- one or the other based on regional settings in the browser or ui,
- display conversions in a tooltip, or let the user decide which
- format to display.
- v2 * indicate "x days ago" or "y days into the future" rather than date
- v2 * input control for anniversaries
- v2 * only submit fields that have changed, or a way to include in the
- submission a list of which form controls were changed from their
- default value
- v2 * type="time" value="now"
- v2 * add something to type="number" to support basic currency and unit
- formatting of input
- v2 * <fieldset enabled-if-checked="myCheckboxOrRadioButton">
- ...to allow sections to only be enabled if a radio button makes it
- relevant, for instance.
- v2 * Yan Morin proposed a multi-column dropdown <select> or <datalist>:
- _________________
- |_New_York______|V|_________________ <- input with a table link and a down arrow
- |_City__________|_State_|_Country_|_| <- header of the table
- | Montreal | QC | Canada |A| <- top arrow of the scroll
- |>New York <| NY | US | | <- selected row
- | Washington | DC | US |X| <- cursor scroll
- | San Francisco | CA | US | |
- |_Toronto_______|__ON___|_Canada__|V| <- bottom arrow of the scroll
-
- v2 * add for="" attribute to <input type="password"> so that you can
- link usernames and passwords. (Jonas Sicking)
- v2 * value for unchecked checkbox?
- v2 * A way to specify the default button - Michael Gratton
- v2 * <fieldset readonly>?
- v2 * dolphinling suggests having a way to mark certain parts of a
- form as being dependent on another (mutually exclusive parts of
- a form)
- v2 * expose the form data set, either as an object (on which one can
- invoke the JSON serialiser), or in the form of a method on
- HTMLFormElement that returns the form data set serialised
- according to a particular encoding (defaulting to the form's
- enctype="" one, probably). This would allow forms to be used
- with XHR-like systems without having to manually construct the
- form data set the way that is done today.
- v2 * expose the file upload progress when uploading files in a form
- (ideally using the same mechanism as XHR2?); ack Rob Evans
-
-Consistency in editorial style:
- v2 * need to become consistent about whether or not to quote keyword
- ("<code title="">foo</code>" vs <code>foo</code>)
- v2 * make the spec consistent about whether the word "algorithm" is part of
- an algorithm's name or not ("</dfn> algorithm", "</span> algorithm")
- v2 * make the spec more consistent about its use of "hexadecimal"
- and "base-sixteen", the order that 0-9 A-Z a-z is mentioned,
- and the detail to which the spec explains how to interpret a
- string as a hexadecimal number.
- v2 * become more consistent about what markup we use to mark up
- productions (nothing? <i>? <code>?)
- v2 * use <code>Document</code> consistently instead of 'document'.
- v2 * be clearer about arrays/lists/collections being zero-based
- despite using the term "/index/th".
- v2 * use the sample widgets:
- <li><img alt="A text field with editable sections for each
- value, with a button to pop up a dialog showing a calendar or
- clock." src="sample-datetime-ui-2"></li>
- <li><img alt="A calendar grid with a clock in the upper right
- hand corner." src="sample-datetime-ui-3"></li>
--->
- </body></html>
\ No newline at end of file
+ other relevant acknowledgements. <a href=#refsHTML>[HTML]</a></p></body></html>
\ No newline at end of file
Received on Thursday, 11 October 2012 00:13:13 UTC