[Bug 12213] New: What!? Is this a joke, if I get the value of an input element in 'filename' mode, I get the filename with an extra string prepended to it, so that to use the filename I will always have to strip the first 12 characters? That is really messed up.
[Bug 12222] New: Drop rel=external. It doesn't do anything anywhere. Pages that use it mostly use it as a scripting hook to inject target=_blank to get around validation.
[Bug 12223] New: Drop rel=help. It's for showing a button in the browser's UI which no browser shows by default. It doesn't seem to be helpful for users, so just wastes authors' time.
[Bug 12230] New: From this algorithm it does not seem to follow that dispatching a synthetic non-canceled submit event at a form causes it to be submitted. Yet that is what browsers implement. So that forms have a default handler for submit events should probably be split
[Bug 12237] New: The MIME type for multipart/form-data needs "boundary=" inserted as well. Please do not make it part of the boundary string by the way.
[Bug 12240] New: "The values 'true' and 'false' are not allowed on boolean attributes." - this also implies that "false" is not a valid attribute name, since ... false="false" ... (meaning the "false" property is 'true') would not be permitted in XML serialization
[Bug 12251] New: The idea of limited-scope style elements is useful, but it causes compability issues. Current browsers ignore the scope attribute and apply the style to the entire document. It is probably better (safe) to ignore a style sheet that is meant to be scoped t
[Bug 12252] New: #appcache Tests: 0 Demos: 0 Latest Internet Explorer beta: no support whatsoever Latest Firefox trunk nightly build: no support whatsoever Latest WebKit or Chromium trunk build: no support whatsoever Latest Opera beta or preview build: no support wh
[Bug 12258] New: The example under "It could equally well be written as follows:" is incorrect and is missing images/sound-icon.png and images/background.png from the above example
[Bug 12264] New: Point 3. ("Otherwise, split the underlying string on spaces to get the list of tokens in the object's underlying string.") is not needed, because after point 2. there are no space characters left.
[Bug 12269] New: If step is the required increase or decrease of the value, is there any way to declare the value used by stepUp() and stepDown()? I had been using step as the number to increase/decrease the value when the up/down arrows were clicked in Chrome, but new bu
[Bug 12276] New: In the HTTP spec, the and that's what's related to http-equiv, it's Content-Type, not content-type etc.. I think the current definition of http-equiv needs to be revised.
[Bug 12277] New: Need to check whether browsers follow this (or are willing to), and if so, spec it: http://hacks.mozilla.org/2011/03/history-api-changes-in-firefox-4/
[Bug 12282] New: If the given browsing context name is _parent, then the chosen browsing context must be the parent browsing context of the current one, unless there isn't one, in which case the chosen browsing context must be the current browsing context.
[Bug 12284] New: How about call the new standard "HML". Then my "C" program won't have to check for a '4 or 3' character word. we will already know the word is 3 characters.
[Bug 12286] New: PropertyValueArray shouldn't use sequence<...>, see http://lists.w3.org/Archives/Public/public-webapps/2011JanMar/0938.html â it should be a method, for one.
[Bug 12290] New: The user agent must allow the element to be focused, should allow the element to be reached using sequential focus navigation, and should place the element in the sequential focus navigation order so that it is:
[Bug 12296] New: Whitespace handling here doesn't match ES, or Gecko, or Opera. Is there some reason to not just say it works the same as parseInt? Test case alerts 2 in Firefox and Opera (like parseInt()), 0 in Chrome: data:text/html,<!doctype html><input tabindex="&nb
[Bug 12299] New: The (normative and non-normative) assertion that tokenlist.item(index) / tokenlist[index] returns null for index>=length appears to be in conflict with WebIDL, at least for the index property case; afaict WebIDL requires that index property getters throw
[Bug 12306] New: "When authors use the canvas element, they must also provide content that, when presented to the user, conveys essentially the same function or purpose as the bitmap canvas." While everyone can probably agree that alternative content is a good idea when f
[Bug 12312] New: This says "The codecs parameter, which certain MIME types define, might be necessary to specify exactly how the resource is encoded." Is this completely up to the browser to decide? Are there any instructions for browsers on how to respond if the codecs a
[Bug 12326] New: The wrap attribute lacks the value "off", which is consistently supported by major browsers and corresponds to the old default behavior, which is still reflected in the HTML 4.01 Recommendation. Please add it and modify the definition of "soft" according
[Bug 12337] New: "are to be" and "are not to be" should be "should be" and "should not be" respectively, for consistency with the following paragraphs.
[Bug 12339] New: We should mention that UAs may use a different clock than the wall clock for defining the rate of time in the media timeline, specifically so that they are allowed to use the soundcard clock to ensure reliable audio playback.
[Bug 12342] New: no need to repeat content of examples; each example should have only new content (currently yellow); that will make document smaller for printing and more readable
[Bug 12344] New: in 3.2.2, in this sentence:'he nodes representing HTML elements in the DOM implement,', the word 'must' does not appear. The sentence should be 'he nodes representing HTML elements in the DOM must implement,'
[Bug 12350] New: Should mention that in the "parents" column, categories refer to elements that _expect_ that category, not elements of those categories...
[Bug 12351] New: Consider changing 'the same object' to 'the same such object' when talking about live objects in various places in the spec, for pedantism...
[Bug 12352] New: Is a list of name/value pairs a valid table, even though it is technically only a one-dimensional associative array, since it requires two columns?
[Bug 12353] New: Is a list of name/value pairs a valid table, even though it is technically only a one-dimensional associative array, since it requires two columns?
[Bug 12354] New: "If the poster attribute's value is the empty string" should also say "or if it is absent", since the algorithm is invoked when the attribute is removed too.
[Bug 12355] New: It would be great to be eable to "scope" some styles but with a CSS file, not into the HTML code itself. What about a src attribute on style, a scoped attribute on link tag, or some specific syntax into the CSS file ?
[Bug 12359] New: If the content model says it can only contain dt and dd elements then why does it say further down "if a dl contains [...] elements other than dt and dd [...]?
[Bug 12360] New: It seems more accurate to say that the media element "is not currently playing" instead of saying "is paused or not". The phrase "is paused" seems to imply that it's been manually paused by the user, but this would not apply when a page is first viewed an
[Bug 12361] New: The "implementation status" for the events doesn't seem to be up to date. For example the canplaythrough event seems to work in Chrome, even though the status says it's not supported by any browser.
[Bug 12373] New: If I understand this correctly, there is no need for h2-h6. Just h1 is enough? I think it should be made more clear how heading ranks work, both implicitly and explicitly.
[Bug 12374] New: "stylistically offset" means that this element has no semantic value whatsoever? It is jsut for style purpose? Then why not use a span? It seems strange to me that there is no specific element to mark up people. Even though there is a load of microdata av
[Bug 12401] New: "The noscript element must not be used in XML documents." "[...] it has no effect in the XHTML syntax." Why is this? Is this to intentionally confuse or restrict web developers into using a particular habit? There is no fathomable functionally practical r
[Bug 12405] New: There's a problem with overlaying a sign-language video and using native controls, because the overlaid video overlaps the native controls
Fwd: Last Call: <draft-ietf-httpbis-content-disp-06.txt> (Use of the Content-Disposition Header Field in the Hypertext Transfer Protocol (HTTP)) to Proposed Standard