Skip to content

Commit

Permalink
[e] (0) Some rejiggering of the acks section.
Browse files Browse the repository at this point in the history 
Affected topics: HTML

git-svn-id: http://svn.whatwg.org/webapps@8614 340c8d12-0b0e-0410-8428-c7bf67bfef74
  • Loading branch information
@Hixie
Hixie committed May 7, 2014
1 parent bb115c4 commit 0ff129d
Show file tree
Hide file tree
Showing 3 changed files with 54 additions and 354 deletions.
182 changes: 15 additions & 167 deletions complete.html
View file
Expand Up @@ -318,13 +318,6 @@ <h2 class="no-num no-toc">Living Standard &mdash; Last Updated 7 May 2014</h2>
<a href=http://ian.hixie.ch/+ class=feedback><span><strong>E-mail the Editor</strong> <code>ian@hixie.ch</code></span></a>
</div>
</div>
<p class=copyright>
<span>Written by Ian Hickson (Google, ian@hixie.ch)</span>
&middot;
<span>Parts &copy; Copyright 2004-2014 Apple Inc., Mozilla Foundation, and Opera Software ASA</span>
&middot;
<span>You are granted a license to use, reproduce and create derivative works of this document</span>
</p>
</header><hr><div id=configUI></div>

<h2 class="no-num no-toc" id=contents>Table of contents</h2>
Expand Down Expand Up @@ -104634,8 +104627,7 @@ <h2 class=no-num id=references>References</h2><!--REFS-->

</dl><h2 class=no-num id=acknowledgments>Acknowledgments</h2> <!-- ACKS -->

<p>Thanks to Tim Berners-Lee for inventing HTML, without which none
of this would exist.</p>
<p>Thanks to Tim Berners-Lee for inventing HTML, without which none of this would exist.</p>

<p>Thanks to

Expand Down Expand Up @@ -105349,20 +105341,24 @@ <h2 class=no-num id=references>References</h2><!--REFS-->
drag-and-drop mechanism, <code title=attr-contenteditable><a href=#attr-contenteditable>contenteditable</a></code>, and other
features first widely deployed by the Windows Internet Explorer browser.</p>

<p class=impl>Special thanks and $10,000 to David Hyatt who came up with a broken implementation
of the <a href=#adoptionAgency>adoption agency algorithm</a> that the editor had to reverse
engineer and fix before using it in the parsing section.</p>

<p>Thanks to the participants of the microdata usability study for allowing us to use their
mistakes as a guide for designing the microdata feature.</p>

<div class=impl>

<p>Special thanks and $10,000 to David Hyatt who came up with a broken implementation of the <a href=#adoptionAgency>adoption agency algorithm</a> that the editor had to reverse engineer and
fix before using it in the parsing section.</p>
<p>Thanks to the many sources that provided inspiration for the examples used in the
specification.</p>

</div>
<p>Thanks also to the Microsoft blogging community for some ideas, to the attendees of the W3C
Workshop on Web Applications and Compound Documents for inspiration, to the #mrt crew, the #mrt.no
crew, and the #whatwg crew, and to Pillar and Hedral for their ideas and support.</p>

<p>Thanks to Igor Zhbanov for generating PDF versions of the specification.</p>

<p>Thanks to the many sources that provided inspiration for the examples used in the
specification.</p>
<p>This specification is written by Ian Hickson (Google, ian@hixie.ch), with contributions from
Simon Pieters (Opera, simonp@opera.com) in the <code><a href=#the-img-element>img</a></code> section.</p>



Expand Down Expand Up @@ -105395,158 +105391,10 @@ <h2 class=no-num id=references>References</h2><!--REFS-->
(<a itemprop=license href=http://creativecommons.org/licenses/by/2.0/>CC BY 2.0</a>)</p>
</div>

<p>Thanks also to the Microsoft blogging community for some ideas, to the attendees of the W3C
Workshop on Web Applications and Compound Documents for inspiration, to the #mrt crew, the #mrt.no
crew, and the #whatwg crew, and to Pillar and Hedral for their ideas and support.</p>
<p>Parts of this specification are &copy; Copyright 2004-2014 Apple Inc., Mozilla Foundation, and
Opera Software ASA. You are granted a license to use, reproduce and create derivative works of
this document.</p>

<!-- Hopefully Kam won't notice he's covered by these acknowledgements three times! -->

<!--
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>
-->

0 comments on commit 0ff129d

Please sign in to comment.