[Bug 7539] Since @summary is an official part of the table element, it is no longer obsolete. Suffienct warning language exists in it's definition that this entry should be removed
[Bug 8095] link's "type" attribute could be used to advertise available representations if it were linked to the Accept: header per Mike Kelly's thread(s)
[Bug 8096] <link>'s "type" attribute should be allowed to appear multiple times and/or should allow for a space separated list of advertised types, such that clients can request them via the Accept: header.
[Bug 8145] New: Unclear: "Certain algorithms in this specification spoon-feed the parser characters one *string* at a time." Better: "one character at a time"?
[Bug 8145] Unclear: "Certain algorithms in this specification spoon-feed the parser characters one *string* at a time." Better: "one character at a time"?
[Bug 8147] New: The suggested size limit is absurd considering the multi-GB space available on even the cheapest netbooks these days. We need a clear "I want this much, how much did the user and his agent allow me to have?" API. Otherwise, online media apps like photo al
[Bug 8147] The suggested size limit is absurd considering the multi-GB space available on even the cheapest netbooks these days. We need a clear "I want this much, how much did the user and his agent allow me to have?" API. Otherwise, online media apps like photo al
[Bug 8150] New: In the description for article, you talk about "Web log posts" but in the example, you use the much more common and understood "blog post". I think the latter should be used throughout. (I would even go so far as to suggest that "Web log" has lost meaning
[Bug 8151] New: "If the resulting value is not a recognized language code, then it must be treated as an unknown language (as if the value was the empty string)." -- consider how this interacts with CSS :lang(), with passthrough/roundtripping, screen readers that recogni
[Bug 8153] New: "The default is start. Other values are ignored." (et passim) would read better if the sentences are reversed ("possible values are [...]. Other values are ignored. The default is [...].")
[Bug 8173] New: Last paragraph, first (only) sentence; add the "to" in brackets ([]) as follows: "are expected to distribute the remainder first [to] the last entry whose unit is relative"
[Bug 8188] Has any thought been put into changing "Fetching an external script must delay the load event..." for async scripts? It seems reasonable to at least provide a way for scripts to not block window.onload.
[Bug 8188] New: Has any thought been put into changing "Fetching an external script must delay the load event..." for async scripts? It seems reasonable to at least provide a way for scripts to not block window.onload.
[Bug 8189] [WA] "reset the connection" should probably be rephrased to "reestablish the connection" to be less confusing ("does it mean reset the TCP connection?")
[Bug 8189] New: "reset the connection" should probably be rephrased to "reestablish the connection" to be less confusing ("does it mean reset the TCP connection?")
[Bug 8190] [WA] event source: "completes loading" should probably be defined in terms of the last task from the networking task source's "fetch" algorithm
[Bug 8190] New: event source: "completes loading" should probably be defined in terms of the last task from the networking task source's "fetch" algorithm
[Bug 8197] New: This design might work for JavaScript, but it won't work well in static-typed languages like Java or C#. Instead of overridding "namedItem", a better design would be to add a new method called "allNamedItems" which always returns an HTMLCollection. "nam
[Bug 8208] New: The data-* attributes need to be clearer about their applicability to JS libraries, and in particular should have some suggestions about using unambiguous attribute names like data-dojo-range or data-jq-selector or whatever.
[Bug 8211] HTML 4 defined these as entities &name; where the ";" wasn't part of the entity name, and there wasn't a variation that some names don't have ";". If this is an example of error recovery, valid HTML should require the ;.
[Bug 8211] New: HTML 4 defined these as entities &name; where the ";" wasn't part of the entity name, and there wasn't a variation that some names don't have ";". If this is an example of error recovery, valid HTML should require the ;.
[Bug 8216] New: editorial: Hide "The name must be one that is terminated by a U+003B SEMICOLON character (;)." and relevant rows in the entity table from the author view. [sp]
[Bug 8230] New: It might be good with a comment in script's Content attributes section mentioning onload/onerror being defined in Global attributes (I've had the question come up several times about script.onload missing from html5).
[Bug 8232] New: [gs] End tag "body" ignore case isn't noted as fragment case, but end tag "html" has a note saying that it can only be ignored in the fragment case. Either that note is wrong or end tag body should say it is fragment case.
[Bug 8235] Given that Gecko and Webkit don't support them in XML, I think that named properties in HTMLDocument objects should be restricted to HTML documents, given that this feature is only included for backward compatibility and is horribly designed.
[Bug 8235] New: Given that Gecko and Webkit don't support them in XML, I think that named properties in HTMLDocument objects should be restricted to HTML documents, given that this feature is only included for backward compatibility and is horribly designed.
[Bug 8236] 1) why a query is stored in the `search' attribute and a URL fragment is stored in the `fragment' attribute? The naming is a bit confusing. 2) Why the is no restrictions for the `port' attribute: an integer in a range [0-65535]; 3) The getter condition fo
[Bug 8236] New: 1) why a query is stored in the `search' attribute and a URL fragment is stored in the `fragment' attribute? The naming is a bit confusing. 2) Why the is no restrictions for the `port' attribute: an integer in a range [0-65535]; 3) The getter condition fo
[Bug 8239] New: [gs] "insert a character" is impossible with e.g., ElementTree, as it has no concept of adjacent text nodes. Need to clarify whether that is ever conforming or not.
[Bug 8240] New: Quote: "The value attribute must not be present unless the form attribute is present." This doesn't make sense, since the button can also belong to a form by being put between the form element tags. It should read: "The value attribute must not be prese
[Bug 8244] New: can you make RDF statements where the subject is another resource here? Metadata has previously been normally where subject is the current resource (or object with rev) but general RDF does not constrain this.
[Bug 8252] HTTP caching rules are _ignored_? What the hell? What's wrong with extending Cache-Control to support user-agent caching instead of coming up with an entirely new mechanism?
[Bug 8252] New: HTTP caching rules are _ignored_? What the hell? What's wrong with extending Cache-Control to support user-agent caching instead of coming up with an entirely new mechanism?
[Bug 8256] [gs] Is form.submit() async or sync? I don't see where this is defined. From my reading it should be sync, as it should just run the steps to completion.
[Bug 8256] New: [gs] Is form.submit() async or sync? I don't see where this is defined. From my reading it should be sync, as it should just run the steps to completion.
[Bug 8259] New: There is one case of "The public identifier is set to" in amongst all the "The public identifier starts with". This seems like something that could easily lead to bugs. Please reorder the list to group together by the condition.
[Bug 8259] There is one case of "The public identifier is set to" in amongst all the "The public identifier starts with". This seems like something that could easily lead to bugs. Please reorder the list to group together by the condition.
[Bug 8260] New: The name apparently must be compared in an ASCII case-insensitive manner, even though it is guaranteed to already be all ASCII lowercase from the tokenizer. It would make more sense to compare it case-sensitively (like it is earlier in the "initial" mode)
[Bug 8272] New: why not make the heading information compulsory for the Section element ?? In a loose implementation like the current one, the Section element is acting just like a Div element but which lacks backward compatibility.
[Bug 8278] New: why can't the frame number be requested? It's video, position is expressed in frames, not in seconds. a frames per second value could easily convert this to seconds
[Bug 8307] New: It would be nice if there were a way to draw an image with a color key. The only other way I can think of doing this is by a for loop and pixel by pixel copying... which probably isn't fast
[Bug 8325] New: Please remove requirements that errors "must be reported to the user" and "should be reported to the user" throughout; "may be reported to the user" is appropriate. [sp]
[Bug 8333] New: In the example: I do not understand why the URL that the user is accessing starts with upper case characters. If the point is, that this part is case insensitive, it should be spelled out instead of this example.
[Bug 8334] New: the stadandard shall explicity cite an example of a url based on RTSP to promote this standard. Today LIVE sreaming is too often achieved with improper "tricks" like HTTP streaming...
[Bug 8334] the stadandard shall explicity cite an example of a url based on RTSP to promote this standard. Today LIVE sreaming is too often achieved with improper "tricks" like HTTP streaming...
[Bug 8335] New: the stadandard shall explicity cite an example of a url based on RTSP to promote this standard. Today LIVE sreaming is too often achieved with improper "tricks" like HTTP streaming...
[Bug 8335] the stadandard shall explicity cite an example of a url based on RTSP to promote this standard. Today LIVE sreaming is too often achieved with improper "tricks" like HTTP streaming...
[Bug 8337] New: This implies that the dragleave event is only fired in the case of an unsuccessful drag, but it's very useful to bubble a dragleave event regardless of success or failure of the drag.
[Bug 8344] New: Please give the detailed information and the pupose why we are using . with out that no one can understand sorry if any thing wrong with me
[Bug 8345] New: The keygen element ought to be extended to support elliptic curve keys. This is especially important in light of NIST guidelines (see pg 63, 66 in http://csrc.nist.gov/groups/ST/toolkit/documents/SP800-57Part1_3-8-07.pdf (pg 63, pg 66) in http://csrc.nist
[Bug 8352] New: the example links should include a type="" attribute to allow automatic selection of the resource to retreive without having to query each of their type to see which one is supported by the browser (this cannot be safely deduced from the "extension" in UR
[Bug 8353] New: How could a browser or even a careful reader know that the licence would applies to the photo only, and not just to the paragraph bewlo the figure? The license link should apply to all the content of its container, here the "body element", so it should be
[Bug 8361] New: Dropping the noscript element from XHTML is problematic. E.g., in the provided example, the calculate button cannot be removed before it the browser displays it, causing a graphical glitch, whitch can be quite large depending on the size of the alterative
[Bug 8363] New: HTML 4 says <br> should behave like U+2028 with respect to bidi. CSS 2 refers to HTML4 for HTML elements. Only WebKit does this. Please say explicitly whether <br> should act as a "forced line break" for the purposes of bidi. [sp]
[Bug 8381] New: I greatly appreciate the addition of custom attribute values, but I take strong exception to the particular notation. In reality, HTML 5 is providing just one attribute named "data," which is quite acceptale because attribute values may be structured. W
[Bug 8386] For some time functions, it is needed to define a time slice like 22:30-24:00, which allows to calculate time differences; this is not possible with 22:30-0:00. Thus I recommend to extend to 0 <= hour <= 24.
[Bug 8386] New: For some time functions, it is needed to define a time slice like 22:30-24:00, which allows to calculate time differences; this is not possible with 22:30-0:00. Thus I recommend to extend to 0 <= hour <= 24.
[Bug 8391] New: What is the meaning of having multiple <source> elements? Presumably a sequence in the case of audio and video... where do I find that info. Thx
[Bug 8393] I believe this should allow for lower case letters too... right now a tag can start with upper/lower but only have upper after the first character. Add lower to this state to fix.
[Bug 8393] New: I believe this should allow for lower case letters too... right now a tag can start with upper/lower but only have upper after the first character. Add lower to this state to fix.
[Bug 8395] <ruby> OJ <rp>(<rt>Orange Juice<rp>)</ruby> is a wrong example compared to the prior part of the document and not legal html5 it should be <ruby> OJ <rp>(</rp><rt>Orange Juice</rt><rp>)</rp></ruby>
[Bug 8395] New: <ruby> OJ <rp>(<rt>Orange Juice<rp>)</ruby> is a wrong example compared to the prior part of the document and not legal html5 it should be <ruby> OJ <rp>(</rp><rt>Orange Juice</rt><rp>)</rp></ruby>
[Bug 8396] New: clip() is fine, but why isn't there something like a stencil buffer? It's similar to clip except you turn on the stencil then render an image and only where you rendered the image are pixels rendered to the canvas.
[Bug 8397] New: The normative text "...so that user agents can offer to add them to the user's calendar" should be moved to the next sentence which begins "For example". Adding events to a calendar is an *example* usage of the time element, not its raison d'etre.
[Bug 8397] The normative text "...so that user agents can offer to add them to the user's calendar" should be moved to the next sentence which begins "For example". Adding events to a calendar is an *example* usage of the time element, not its raison d'etre.
[Bug 8405] New: The setter method is defined with an octet argument, so type conversions will happen as defined by WebIDL before the setter implementation gets to see it, and so the setter will only see valid values (integers 0..255) and shouldn't define any rounding or