|
|
|
|
|
acknowledgements three times! --> |
|
|
|
|
|
<!-- |
|
|
v2 ideas: |
|
|
* library of resources: |
|
|
v2 * library of resources: |
|
|
var library = new ZipFile("data.zip"); |
|
|
library.onload = function() { |
|
|
var sound1 = library.getAudio("sound1.wav"); // returns an Audio object |
|
|
|
|
var sound1 = library["sound1.wav"]; |
|
|
sound.play(); |
|
|
} |
|
|
--> |
|
|
<!-- |
|
|
TODO: |
|
|
XXX * ability for a web app to save a file to the local disk: |
|
|
var file = window.openFile(); // throws up UI |
|
|
file.read(); |
|
|
var file = window.saveAsFile(); // throws up UI |
|
|
file.write(); |
|
|
...or something? (<input type=file>?) |
|
|
XXX * http://lxr.mozilla.org/mozilla/source/dom/public/idl/html/nsIDOMNSHTMLDocument.idl |
|
|
XXX * define how to handle APNGs that have out-of-order aDATs and other |
|
|
errors in image formats, since pav and vlad refuse to define it for APNG: |
|
|
<Hixie> vlad: you should define what the UA should do with out-of-order aDATs |
|
|
<pav> its an error |
|
|
<pav> pretty sure we say that somewhere |
|
|
<Hixie> yes i know it's an error |
|
|
<Hixie> but that doesn't say what the UA should do |
|
|
<pav> error == image is invalid |
|
|
<vlad> yep |
|
|
<vlad> either broken image icon |
|
|
<vlad> or display first frame (fall back to normal PNG) |
|
|
<vlad> up to the UA |
|
|
<Hixie> right |
|
|
<Hixie> you should say which one |
|
|
<pav> its up to the UA |
|
|
<Hixie> why? |
|
|
<vlad> "SHOULD display the first frame, but MAY display broken image icon if that's not convenient", in rfc parlance |
|
|
<vlad> because it's not useful to specify that, IMO |
|
|
<Hixie> up to the UA means one UA will implement something, it'll become a popular UA, then all the others will have to copy it. |
|
|
<vlad> how a UA wants to handle image errors is up to the UA |
|
|
<pav> we're designing an image format, not the html image tag |
|
|
<pav> the html spec should say what to do with it |
|
|
XXX * <title site="" publisher="" author="">Page Title</title> ? |
|
|
XXX * [onclick] should make element focusable; enter should send onclick ? |
|
|
XXX * should have some text talking about the fact that it's ok if your |
|
|
page passes through a period of non-conformance while script is |
|
|
running, but that in between scripts it should be compliant. |
|
|
XXX * mousedown's default action is focus, so canceling mousedown stops |
|
|
focus transference. http://www.mozilla.org/editor/midasdemo/ |
|
|
XXX * <select><option><hr> support? |
|
|
XXX * need explanation of when to use undo/redo, and when to use |
|
|
back/forward |
|
|
XXX * need to become consistent about whether or not to quote keyword |
|
|
("<code title="">foo</code>" vs <code>foo</code>) |
|
|
XXX * need to properly xref events throughout |
|
|
XXX * onclick="" only fires if it is a MouseEvent ? |
|
|
XXX * hsivonen makes the following suggestions: |
|
|
> To make document conformance a more useful concept for the purpose of catching |
|
|
> author errors, I suggest that the following attributes be made required: |
|
|
> href and rel on link |
|
|
> href on base |
|
|
> name and content on meta (other than the encoding decl) |
|
|
> src on img |
|
|
> code, height and width on applet |
|
|
> name and value on param |
|
|
XXX * DOM0 quirks that Mozilla knows about: |
|
|
http://lxr.mozilla.org/seamonkey/source/dom/src/base/nsDOMClassInfo.cpp |
|
|
XXX * make the spec consistent about whether the word "algorithm" is part of |
|
|
an algorithm's name or not ("</dfn> algorithm", "</span> algorithm") |
|
|
XXX * make a consistent decision of which of the following formats to use: |
|
|
U+1234 FOO BAR character ("foo") |
|
|
U+1234 FOO BAR character ('foo') |
|
|
U+1234 FOO BAR character (foo) |
|
|
U+1234 FOO BAR ("foo") character |
|
|
U+1234 FOO BAR ('foo') character |
|
|
U+1234 FOO BAR (foo) character |
|
|
U+1234 FOO BAR character ("<code title="">foo</code>") |
|
|
U+1234 FOO BAR character ('<code title="">foo</code>') |
|
|
U+1234 FOO BAR character (<code title="">foo</code>) |
|
|
U+1234 FOO BAR ("<code title="">foo</code>") character |
|
|
U+1234 FOO BAR ('<code title="">foo</code>') character |
|
|
U+1234 FOO BAR (<code title="">foo</code>) character |
|
|
...and make these match: |
|
|
0x12 (ASCII FOO) |
|
|
0x12 (ASCII "foo") |
|
|
0x12 (ASCII 'foo') |
|
|
0x12 ("foo") |
|
|
0x12 ('foo') |
|
|
0x12 (ASCII "<code title="">foo</code>") |
|
|
0x12 (ASCII '<code title="">foo</code>') |
|
|
0x12 ("<code title="">foo</code>") |
|
|
0x12 ('<code title="">foo</code>') |
|
|
XXX * check case of hex characters in the ASCII cases. |
|
|
XXX * trim function in JS for strings to remove spaces |
|
|
XXX * date checking functions in JS (.isValidDate?) |
|
|
XXX * a fairly common situation for web authors is to have two lists, where |
|
|
v2 * [onclick] should make element focusable; enter should send onclick ? |
|
|
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) |
|
|
XXX * quick-searchable select |
|
|
XXX * fallback that will only appear in non-webforms clients (e.g. for |
|
|
formats for date fields) |
|
|
XXX * include/exclude selectors (two multi-select columns with arrows to |
|
|
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 |
|
|
XXX * Oh, and forms need a standardized Help widget/icon. I know I can |
|
|
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 |
|
|
XXX * Validating only part of a form. - Anja Lehmann |
|
|
XXX * Reminder to add a way to expose access keys in buttons, i.e. |
|
|
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)] |
|
|
XXX * option.text should do the same as option.textContent |
|
|
XXX * need an attribute that says "the children of this element are in |
|
|
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? |
|
|
XXX * make select widgets have multiple columns |
|
|
v2 * make select widgets have multiple columns |
|
|
or ->web apps with list view |
|
|
XXX * required as a group (one of the following must be available): |
|
|
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 |
|
|
|
|
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 |
|
|
XXX * 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> |
|
|
XXX * formatting of number fields, text fields, etc, so that when the |
|
|
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. |
|
|
XXX * password and confirm password: can we have a way to do client-side |
|
|
validation of this? |
|
|
XXX * <input type="search"> |
|
|
http://weblogs.mozillazine.org/hyatt/archives/2004_07.html#005890 |
|
|
XXX * would be nice to say how to handle duplicate IDs once and for all |
|
|
instead of spreading it all over the spec. |
|
|
XXX * being able to select date range (from day x to day y) |
|
|
XXX * ways of visualizing a linefeed in a <textarea> so it looks different |
|
|
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 |
|
|
XXX * all login systems have |
|
|
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 |
|
|
XXX * way of identifying different sorts of mailadresses |
|
|
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) |
|
|
XXX * hotswapping login identities like in windows xp |
|
|
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) |
|
|
XXX * provide different measuring systems, like having the html indicate |
|
|
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. |
|
|
XXX * indicate "x days ago" or "y days into the future" rather than date |
|
|
XXX * input control for anniversaries |
|
|
XXX * only submit fields that have changed, or a way to include in the |
|
|
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 |
|
|
XXX * have a way of marking the first option of a <select> as the default |
|
|
v2 * have a way of marking the first option of a <select> as the default |
|
|
but have it not satisfy a new required="" attribute on <select> so |
|
|
that you can have selects that require a valid value. |
|
|
XXX * Dave Raggett inadvertently suggested there should be a way to submit |
|
|
canvas elements. |
|
|
XXX * type="time" value="now" |
|
|
XXX * should "mixed fractional number" be used instead of "fractional"? |
|
|
XXX * terse BNF to define the allowed values of the various attributes |
|
|
instead of, or in addition to, the prose. [or not, it wouldn't be terse] |
|
|
XXX * add something to type="number" to support basic currency and unit |
|
|
v2 * type="time" value="now" |
|
|
v2 * add something to type="number" to support basic currency and unit |
|
|
formatting of input |
|
|
XXX * <fieldset enabled-if-checked="myCheckboxOrRadioButton"> |
|
|
v2 * <fieldset enabled-if-checked="myCheckboxOrRadioButton"> |
|
|
...to allow sections to only be enabled if a radio button makes it |
|
|
relevant, for instance. |
|
|
XXX * Yan Morin proposed a multi-column dropdown <select> or <datalist>: |
|
|
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 |
|
|
|
|
| San Francisco | CA | US | | |
|
|
|_Toronto_______|__ON___|_Canada__|V| <- bottom arrow of the scroll |
|
|
|
|
|
XXX * add for="" attribute to <input type="password"> so that you can |
|
|
v2 * add for="" attribute to <input type="password"> so that you can |
|
|
link usernames and passwords. (Jonas Sicking) |
|
|
XXX * value for unchecked checkbox? |
|
|
XXX * A way to specify the default button - Michael Gratton |
|
|
XXX * <fieldset readonly>? |
|
|
XXX * action="" should be defined as not being relative to base URI |
|
|
see https://bugzilla.mozilla.org/show_bug.cgi?id=297761 |
|
|
XXX * rephrase things so that an enumerated attribute puts the _element_ into |
|
|
various states, instead of the attribute |
|
|
XXX * dolphinling suggests having a way to mark certain parts of a |
|
|
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) |
|
|
XXX * 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. |
|
|
XXX * expose the form data set, either as an object (on which one can |
|
|
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. |
|
|
--> |
|
|
<!-- |
|
|
TODO: |
|
|
XXX * should have some text talking about the fact that it's ok if your |
|
|
page passes through a period of non-conformance while script is |
|
|
running, but that in between scripts it should be compliant. |
|
|
XXX * mousedown's default action is focus, so canceling mousedown stops |
|
|
focus transference. http://www.mozilla.org/editor/midasdemo/ |
|
|
XXX * need explanation of when to use undo/redo, and when to use |
|
|
back/forward |
|
|
XXX * need to become consistent about whether or not to quote keyword |
|
|
("<code title="">foo</code>" vs <code>foo</code>) |
|
|
XXX * onclick="" only fires if it is a MouseEvent ? |
|
|
XXX * hsivonen makes the following suggestions: |
|
|
> To make document conformance a more useful concept for the purpose of catching |
|
|
> author errors, I suggest that the following attributes be made required: |
|
|
> href and rel on link |
|
|
> href on base |
|
|
> name and content on meta (other than the encoding decl) |
|
|
> src on img |
|
|
> code, height and width on applet |
|
|
> name and value on param |
|
|
XXX * make the spec consistent about whether the word "algorithm" is part of |
|
|
an algorithm's name or not ("</dfn> algorithm", "</span> algorithm") |
|
|
XXX * make a consistent decision of which of the following formats to use: |
|
|
U+1234 FOO BAR character ("foo") |
|
|
U+1234 FOO BAR character ('foo') |
|
|
U+1234 FOO BAR character (foo) |
|
|
U+1234 FOO BAR ("foo") character |
|
|
U+1234 FOO BAR ('foo') character |
|
|
U+1234 FOO BAR (foo) character |
|
|
U+1234 FOO BAR character ("<code title="">foo</code>") |
|
|
U+1234 FOO BAR character ('<code title="">foo</code>') |
|
|
U+1234 FOO BAR character (<code title="">foo</code>) |
|
|
U+1234 FOO BAR ("<code title="">foo</code>") character |
|
|
U+1234 FOO BAR ('<code title="">foo</code>') character |
|
|
U+1234 FOO BAR (<code title="">foo</code>) character |
|
|
...and make these match: |
|
|
0x12 (ASCII FOO) |
|
|
0x12 (ASCII "foo") |
|
|
0x12 (ASCII 'foo') |
|
|
0x12 ("foo") |
|
|
0x12 ('foo') |
|
|
0x12 (ASCII "<code title="">foo</code>") |
|
|
0x12 (ASCII '<code title="">foo</code>') |
|
|
0x12 ("<code title="">foo</code>") |
|
|
0x12 ('<code title="">foo</code>') |
|
|
XXX * check case of hex characters in the ASCII cases. |
|
|
XXX * option.text should do the same as option.textContent |
|
|
XXX * 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> |
|
|
XXX * should "mixed fractional number" be used instead of "fractional"? |
|
|
XXX * 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. |
|
|
XXX * become more consistent about what markup we use to mark up |
|
|
productions (nothing? <i>? <code>?) |
|
|
XXX * should check all cases of 'active document' and change the |