[Bug 10365] popstate event fires after onload (first page visit) -- intended behavior? would be annoying if there was a script that ajax loaded a page at onpopstate, and hand typing in a url, the page is returned by the server, and then onpopstate fires after onload,

[Bug 11140] Subject: Physical Keys and Gestures for "accesskey" attribute The use of ASCII/Unicode code points for key binding has numerous well-known drawbacks. There are vital physical keyboard keys with no Unicode representation. Even for the main alphabet keys sp

[Bug 11201] Hi there, Reading through the HTML5 Offline spec at http://dev.w3.org/html5/spec/offline.html , the spec is not clear on what should happen if the manifest attribute of the html tag is modified during/after the document has loaded. eg, if Javascript is u

[Bug 11201] New: Hi there, Reading through the HTML5 Offline spec at http://dev.w3.org/html5/spec/offline.html , the spec is not clear on what should happen if the manifest attribute of the html tag is modified during/after the document has loaded. eg, if Javascript is u

[Bug 11217] Footnotes I find it hard to believe, that even today, HTML does not include a specific element for including notes within the text. Notes are necessary for the full argumentation in the text without still belonging to the main text itself, and they includ

[Bug 11217] New: Footnotes I find it hard to believe, that even today, HTML does not include a specific element for including notes within the text. Notes are necessary for the full argumentation in the text without still belonging to the main text itself, and they includ

[Bug 11225] New: You should allow the part after the at sign to be ldh-str 0*( "." ldh-str ), or whatever the proper syntax is, to allow "username@localhost". This might actually be useful for testing web apps, and it doesn't seem like it would cause any extra harm. Plu

[Bug 11229] New: Try making an author-specific edition that has one page per section, a tree on the side, and ben's styles, as per http://www.reddit.com/r/programming/comments/dzww6/who_edits_the_w3c_specs_they_look_like_a_ransom/c14ilc2

[Bug 11237] If there's an itemtype="", then the itemprop="" names can be anything listed in the specification that defines the given itemtype="". I should probably clarify that such a specification should only use colons and dots in keywords that are absolute URLs, t

[Bug 11237] New: If there's an itemtype="", then the itemprop="" names can be anything listed in the specification that defines the given itemtype="". I should probably clarify that such a specification should only use colons and dots in keywords that are absolute URLs, t

[Bug 11245] I cannot find an explicit statement about XML compatibility of empty attributes. In former XHTML standards, the syntax used to be <input checked="checked".../> Now with the implied value "" of empty attributes, the syntax is <input checked=""/> as I under

[Bug 11245] New: I cannot find an explicit statement about XML compatibility of empty attributes. In former XHTML standards, the syntax used to be <input checked="checked".../> Now with the implied value "" of empty attributes, the syntax is <input checked=""/> as I under

[Bug 11247] New: 7.1.3.4: I think it would be a good practice to throw a QUOTA_EXCEEDED_EXCEPTION just some seconds (i.e. 5s) BEFORE the QUOTA_EXCEEDED_ERR is thrown. This would give us a way to convict the script/data in a clean state with(out) or at least less corrupted

[Bug 11253] "User agents may wait for a suitable break in the user's interaction before queuing the task; for example, a user agent could wait for the user to have not hit a key for 100ms, so as to only fire the event when the user pauses, instead of continuously for

[Bug 11253] New: "User agents may wait for a suitable break in the user's interaction before queuing the task; for example, a user agent could wait for the user to have not hit a key for 100ms, so as to only fire the event when the user pauses, instead of continuously for

[Bug 11254] New: Could you just say outright that <b>, <i>, <s>, <sup>, <sub>, <br>, and maybe others are typographical and not semantic? They're in HTML because Unicode doesn't cover them and CSS can't, because you need to mark up inline where they go. They're no more

[Bug 11285] New: You're missing an "and" or something here, it's not clear when the last clause is applicable: if the algorithm was invoked in the attribute mode, any occurrences of the """ character by the string "&quot;", or if it was not, any occurrences of the "<" cha

[Bug 11285] You're missing an "and" or something here, it's not clear when the last clause is applicable: if the algorithm was invoked in the attribute mode, any occurrences of the """ character by the string "&quot;", or if it was not, any occurrences of the "<" cha

[Bug 11302] New: In 'A start tag whose tag name is "select"' perhaps the first step needs to be somethiing like: "If the current node is an option element then act as if an end tag with the tag name "option"had been seen." Similar statements in the same section for the op

[Bug 11319] I would think the pattern attribute ought to allow patterns to specify ignoring case. We have a system in place where users can enter product codes in (they match a pattern), but also would like to match certain specific strings (e.g. "freight") and want

[Bug 11319] New: I would think the pattern attribute ought to allow patterns to specify ignoring case. We have a system in place where users can enter product codes in (they match a pattern), but also would like to match certain specific strings (e.g. "freight") and want

[Bug 11338] Elliott Sprehn suggests a note here saying something like "In the HTML serialization, namespace prefixes and namespace declarations are non-conforming and are do not have the same effect as in XML. In particular, the colon has no special meaning in HTML

[Bug 11338] New: Zeros says we should add a note here saying something like "In the HTML serialization, namespace prefixes and namespace declarations are non-conforming and are do not have the same effect as in XML. In particular, the colon has no special meaning in HTML

[Bug 11345] New: "Errors that result in disproportionally poor performance" has a bad example. It doesn't result in disproportionally poor performance (the conforming alternative also has to examine all open elements, one at a time for each close tag). A better example is

[Bug 11353] Instead of "If rowspan is zero, then let cell grows downward be true, and set rowspan to 1," it should read, If rowspan is zero, then set rowspan to 1. If rowspan is greater than 1, then let cell grows downward be true.

[Bug 11353] New: Instead of "If rowspan is zero, then let cell grows downward be true, and set rowspan to 1," it should read, If rowspan is zero, then set rowspan to 1. If rowspan is greater than 1, then let cell grows downward be true.

[Bug 11359] New: When I compare the processing of attribute value in single/double quoted state it's different to unqoted. <a href=' and <a href=" forces to ignore markup until EOF or next quote what is really not good.

[Bug 11359] When I compare the processing of attribute value in single/double quoted state it's different to unqoted. <a href=' and <a href=" forces to ignore markup until EOF or next quote what is really not good.

[Bug 11399] New: The ability to lock individual channels (i.e. prevent them from being updated by drawing functions) would allow for some interesting composition tricks, such as drawing directly to the alpha channel.

[Bug 11402] New: One problem of todays JavaScript libraries is, that the client has to download the same library over and over again, while visiting multiple sites. One could use services like Google Libraries API for a central location, but that introduces new points of

[Bug 11402] One problem of todays JavaScript libraries is, that the client has to download the same library over and over again, while visiting multiple sites. One could use services like Google Libraries API for a central location, but that introduces new points of

[Bug 9774] "consecutive lines displayed below each other" - since subtitles tend to be rendered at the bottom, it's actually better for new subtitles to be rendered higher up. Of course, the individual lines of each subtitle still extend downwards, but it's still po

[Bug 9775] "positioned to a multiple of the line dimensions of the first line of the cue" - enforcing the same line height for every line ihurts text rendering appearance for no apparent reason. This is especially true if text styling is supported (bold text is larg