[Bug 6057] in the audio portion of the spec, at the end of 4.7.8.0 it mentions "If the src argument is present..." but the example given calls it the argument 'url'
[Bug 7143] "attributes marked with an asterisk cannot be specified on body elements" is confusing, since <body onload=""> is pretty common. Of course that's the attribute specified on a tag, but still, I'm just a simple author reading the spec for the first time :)
[Bug 7144] I am not sure if we are ditching ALT in favour of legend. You don't make this clear here. Some of your alt examples here resemble longdesc, which I am in favour of ditching completely. I'd be interested to see your answer on whatwg list about this
[Bug 7152] "When the user agent has completely fetched of the entire media resource, [â¦]" No 'of' and only one of 'completely' or 'entire' should remain in the text. Mentioned one week ago on the list. Taking the opportunity to try this inline review box.
[Bug 7154] icon attribute: We can't apply so-called "CSS Sprite" technique for command icons. We need another attribute to specify clip position and size.
[Bug 7190] Since all "specially focusable" elements have an activation behaviour, the Action of accesskey-laden commands is to _not_ focus them if they are focusable. Instead, such elements should probably always be focused if focusable, then be activated.
[Bug 7241] Need to explain exactly what happens if wrap=hard is specified *without* cols being specified. Should it act like wrap=soft, or like cols=20?
[Bug 7253] Media elements should provide a "next" property to gaplessly play back another media object after it has finished. This woud allow proper playback of gapless albums and an in-browser implementation of HTTP Adaptive Bitrate Streaming.
[Bug 7254] If <audio> was able to play back multiple source urls without gaps, JavaScript could decode or generate continuous audio to data: urls on the fly.
[Bug 7258] Should state that a new Date object is returned each time the date/time/timezone attributes are accessed if the intention is for them not to be reflecting datetime="" or the element content.
[Bug 7263] this thing really heavy, tried solution: switch to user mode css, after all rendered, return to author mode, scrolling is heavy though,,, try open panel & add info, heavy too..
[Bug 7269] user agent requirements: for value=8 max="", step 4 and 11 will cause current value and maximum value to be set to 1, which is destructive (if script wanted to obtain the original value). suggest step 4 change to set maximum to value
[Bug 7273] The word "left" should not be part of the link when saying that attributes can be left unquoted. It sounds too much like "left outer join" or such, and might imply that it was legal to unquote only one side, or some such oddness. JimJJewett@gmail
[Bug 7274] The word "left" should not be part of the link when saying that attributes can be left unquoted. It sounds too much like "left outer join" or such, and might imply that it was legal to unquote only one side, or some such oddness. JimJJewett@gmail
[Bug 7275] "The markup snippet at the top of this section" should be a link to that snippet; the section is long enough that the snippet will already have scrolled off-screen for some people. (In my case, it had also escaped my short-term memory.) JimJJewett@gmail
[Bug 7277] """(This is only a "SHOULD" and not a "MUST" requirement because it has been proven to be impossible.""" There has to be better wording than 'should do the impossible'. Should attempt to verify? Impossible in some cases? JimJJewett@gmail
[Bug 7278] numbers seem ignorant of i18n - is <meter>10,3</meter> taken as 10? requirements for number may expand to include, i.e.: U+002C COMMA for European â
[Bug 7351] The note ("The point of hgroup is to mask an h2 element (that acts as a secondary title) from the outline algorithm.") should be explicitly associated with the example below it that it applies to. (in general, a hgroup could mask an h3, h4, h5, etc.).
[Bug 7357] That ApplicationCache implements EventTarget should be a line in the IDL, not in prose: "ApplicationCache implements EventTarget;". This might apply to other sections too.
[Bug 7364] The contents attribute is declared as read/write, however the following description only gives information about getting the value of the attribute. Should the contents attribute be marked as readonly?
[Bug 7368] The suggested UI for the mark element does not match the description and the examples. E.g. code highlighting is not something you want to see marked in the scrollbar. Personally I think code highlighting should just be done with strong.
[Bug 7369] if context font is set to '' or null, the font from the css should be used. In this case, you have no idea what font is being use, so measureText should return a height of the font, as well as the width so that proper displaying can be done.
[Bug 7403] What should happen when audio does not have controls but author specifies display:inline? Show fallback? Show blank box with the same size as if it had controls? Force display:none?
[Bug 7407] "The examples in the previous section show how information could be marked up on a page that doesn't expect its microdata to be re-used." is not true anymore
[Bug 7415] "The rules for parsing simple color values are as given in the following algorithm." --> "The rules for parsing simple color values are given in the following algorithm."
[Bug 7418] See if we can make popstate more synchronous so that when it fires, the doc is in the expected state, rather than three back-button-steps later. But consider nested calls to history.back().
[Bug 7419] Add replaceState() â e.g. consider panning on a maps application, not all the steps should be new states for back/forward, but we do want to update the url for persistence.
[Bug 7427] When the maxlength attribute is omitted it should return -1 like Opera and Firefox and not 0. (Alternatively it could return the maximum value like Chrome and presumably Safari do, but that seems less nice.
[Bug 7428] Safari 4 preloads media and FF 3.5 doesn't in <audio> tag; perhaps HTML5 sections 4.8.10.5 4.8.10.8 are unclear or need a 'preloading' attribute added.
[Bug 7431] "willful double violation of RFC 2046": The word "double" is splitting the defined term "willful violation". This sounds like a new defined term and interferes with document searching. Instead use "willful violation of two aspects of RFC 2046"
[Bug 7432] 'have been noted as "willful violations"': Other places use the signular, "willful violation". For consistency, non-native english readers and easy text search, use the singular when defining the term. E.g. 'have each been noted as a "willful violation".
[Bug 7434] Everything with role=heading should also have an associated aria-level that indicates the level of the heading. The level of the heading should probably be based on the outline algorithm.
[Bug 7441] The specification only ever uses the prefix:localName convention for some attributes in the XML namespace and whenever it does it is pretty explicit about it. xml:id is never mentioned outside this section and the prefixes svg and html are never used.
[Bug 7445] editorial: This section becomes a subsection of "the xhtml syntax" in the author edition. Maybe either move this section somewhere else or keep the "Rendering" and "Interaction with CSS" headings outside class=impl
[Bug 7447] "Use the data and type attributes to invoke plugins." should also mention that <param> can be used to pass parameters with these names to the plugin
[Bug 7453] "preferred name" should be "preferred MIME name" but it should also state that if there is no preferred MIME name for the encoding the name of the encoding should be used.
[Bug 7456] Ogg vorbis realy should be standard since it is open and everything can then support it without patent costs. This is REALLY important. Most other standards need patent money. Apple's H.264 is CERTAINly bad here.
[Bug 7457] Ogg theora needs to be used here as an open standard. Having different standards in different browsers will confuse the matter and it is the only standard to my knowledge that is not patent encumbered. This is seriously important to reinstate.
[Bug 7466] This section forbids exposing rel=feed but not exposing e.g. rel=copyright. I think that is wrong. The specification should not dictate UI for this.
[Bug 7470] JimJJewett gmail: The implications of these tables should also appear at element level -- e.g, td model or dom should mention aria- -- unless it is explicitly not exposed, for some reason.
[Bug 7473] JimJJewett gmail: Mention explicitly that the mapping for foreign content -- including adopted MathML or SVG -- is left to those working groups. (Otherwise, I would have expected some strong native semantics for math to math)
[Bug 7477] "It is an element with an ID key" makes it sound like "ID" is an adjetive for "key". Consider a phrasing like the previous bullet. Namely, "It is an element with an ID equal to key."
[Bug 7481] The Form submission algorithm section states "If the submitter is anything but a form element...", yet this section states "validate the constraints of form element form".
[Bug 7482] The maxLength attribute for input elements can be -1, indicating no maxlength attribute present, per DOM Level 2 HTML. HTML 5 has changed that to be "unsigned long", which -1 cannot be.
[Bug 7487] An internal general parsed entity is not XML namespace-well-formed in the general case, since a fragment can have text and multiple elements at the top level
[Bug 7489] I wanted to know what a fallback entry is so I clicked on the "fallback entries" link. This took me to a section that describes fallback entries as "Resources that were listed in the cache's manifest as fallback entries". But that's a recursive definition
[Bug 7494] It puts together on src etc. of the audio tag and the img tag, and it wants a united method of knowing meta information on src. It is a name of a song, and a name of the singer in case of the song. If it is a photograph, it is GPS informational etc.
[Bug 7501] Change "The value must be a short free-form string THAT giving the name of the Web application that the page represents." It should read- "The value must be a short free-form string giving the name of the Web application that the page represents."
[Bug 7502] The clarification that the footer can be used as a site-wide footer or a section footer is not inherently clear via the spec. I suggest specifically stating just that: use for a section or an entire site.
[Bug 7503] there is no specification for detection of this feature. how do i know whether to use draggable="true" or revert to a drag simulation library like scriptaculous? - jkwon.work@gmail.com
[Bug 7506] Clarify that the warning about "The presence of an obsolete permitted DOCTYPE" only applies to HTML, not XHTML which has no restriction on what DOCTYPEs may be used
[Bug 7511] The implicit mechanism doesn't fire onsubmit or validate as written today. The exception for when the submitter is the form should be changed to just be a flag for .submit() specifically.
[Bug 7519] Should rephrase "All the elements in this specification have a defined content model, which describes what nodes are allowed inside the elements, and thus what the structure of an HTML document or fragment must look like." to more explicitly say that HTML
[Bug 7521] This table is confusing because it mixes content, IDL attributes, methods, and events. Maybe the various concepts can be grouped and get an appropriate row-group header so it is more clear. The introduction for the table doesn't mention the events and doe
[Bug 7524] The list of forbidden Unicode characters in the authoring requirements does not match the list that generates parse errors in #tokenizing-character-references
[Bug 7526] spelling: Before this task is run, *sa* part of the event loop mechanism, the rendering will have been updated to resize the video element if appropriate.
[Bug 7543] Consensus on ietf-http-wg was that repetition of relations is meaningless and we should rather use numbering (e.g. "up2"), names (e.g. "great-grandparent") or an attribute (e.g. level="3").
[Bug 7544] Atom (RFC 4287) further specifies that "The image SHOULD have an aspect ratio of one (horizontal) to one (vertical) and SHOULD be suitable for presentation at a small size". Consider doing the same here.
[Bug 7545] Atom (RFC 4287) defines a "logo" in addition to the "icon": "The image SHOULD have an aspect ratio of 2 (horizontal) to 1 (vertical)". Consider doing the same here.
[Bug 7550] The invalid event does have a default action. Namely to display UI. However, UAs should probably not be forbidden to show that a field is invalid before submitting, but how can page author suppress the UI for that?
[Bug 7560] The following sentence could be made more clear, or given an example to indicate what is meant: "The otherwise optional U+000A LINE FEED (LF) character must be included if the element's contents start with that character"
[Bug 7574] The annotation here has 20 tests, but the box for viewing them is bigger than the browser window, hiding the close button. Set a max height and overflow:auto on the popup box.
[Bug 7583] IE8 won't run click events on a label's associated input if the input is hidden via CSS with "display:none" or "visibility:hidden". Other browsers will. There doesn't seem to be an appropriate platform behavior to emulate here, so the exact behavior sho
[Bug 7590] The sentence about HTMLUnknownElement should s/this specification/this specification (or other appliciable specifications)/ to allow delta specs to define HTML elements
[Bug 7599] Either drop the two places that set the "Origin" HTTP header, or update HTML5 to match the Sec-From/Origin I-D (if the latter is stable enough yet).
[Bug 7606] the current behaviour in firefox on a disable input type='submit' is not to show the tooltip, in IE it will appear and then disappear but only when hovering over the text. Should the behaviour of the tooltip be more specifically defined when the element
[Bug 7618] "Whether a document is an HTML document or an XML document affects the behavior of certain APIs, as well as a few CSS rendering rules." - actually, i think it doesn't affect CSS rendering anymore, just selector matching
[Bug 7619] "Document objects also implement the document-level interface of any other namespaces found in the document that the UA supports." - drop "found in the document" since it doesn't make sense to implement another interface on-the-fly when finding another na
[Bug 7620] I think Opera has some security checks for location, added because of some Flash vulnerability. If other browsers have similar checks, would be good to specify
[Bug 7622] "There has got to be a better way of doing this, surely." - is there an intent to rewrite this before last call? is there implementor interest? is it considered for removal?
[Bug 7625] Since "event handler attributes" is an abstract concept it might be better to just call it "event handlers" so attributes is not confused with either IDL or content attributes here.
[Bug 7628] The later 'block' box container should simply map to the first/last dd element. This makes UA implementations easier and script emulation of the feature in contemporary UAs as well. Both can simply toggle the display property between block and none.
[Bug 7635] Include an example with the table rearranged so that it doesn't need a description, and advice that doing so might be more useful than writing a description
[Bug 7640] The definition of the "isindex" element here makes such elements' main interface be HTMLElement rather than HTMLUnknownElement. I suppose that's not intended
[Bug 7641] The rendering of <details> says everything but the first dt will be hidden, but the element definition says the first dd represents the details. Also, having overflow:hidden when the details are open probably has unintended side-effects like clipping cont
[Bug 7643] Why not use display:none instead of overflow:hidden; height:0? display:none seems to have the desired behavior in terms of exposure to AT and keyboard navigation in browsers.
[Bug 7649] It would be useful to see an example of how section works when it's not in the context of an article, in the example text (chapters, tabs, etc) all of those would sit inside a wrapping article element.
[Bug 7664] The in-memory representation is known as "DOM HTML", or "the DOM" for short. This specification defines version 5 of DOM HTML, known as "DOM5 HTML".
[Bug 7674] are the chunks for inputs having the content-type header for each chunk specified appropriately? e.g. file inputs should set the header according to the file selected by the user
[Bug 7677] Is there any behavior defined for setting the src property. For example, is the expectation that object should (A) load the src if autobuffer is true (B) stop playing if currently playing (C) something else (D) nothing at all?
[Bug 7697] The type attribute should ammend the Accept header accordingly. HTTP spec is in accordance with the rules here, in terms of the Accept header being non-authorative. script and style elements already ammend accept header (in firefox) but not for other link
[Bug 7701] Step 6.2 tells you to remove node from the stack of open elements and then go to step 6.1. 6.1 requires that you set node to be the node above node in the stack of open elements. However node is no longer in the stack of open elements
[Bug 7717] If the user does not give permission it is not stated explicitly what will happen. It would be nice if the specification did state that the algorithm will be terminated at that point. (Should an event be dispatched?)
[Bug 7718] "If a Document or image was generated from a data: URL that was returned as the location of an HTTP redirect" ... "If a Document or image was obtained in some other manner (e.g. ... a data: URL returned as the location of an HTTP redirect ...)" - the last
[Bug 7724] I would like to know: what is to become of the A elementâs NAME attribute? I validated a HTML5 website that I am working this Wednesday (2009-09-23) which contained an A element with a NAME attribute: the W3C Markup Validator did not mind one bit. Howe
[Bug 7725] It should be made more clear that only the "disk representation" is changed, not the "memory representation". I.e. images are not suddenly reloaded etc.
[Bug 7732] Server crawls (also on Safari), then page's loading slow and in parts, get a bizzare feeling, it's no longer a web page but an app I'am loading, don't like that, resizing causes page blanks of seconds length
[Bug 7734] open being an attribute of the section rather than the content area means you can never use this to mark up content which has multiple control/detail areas which are opened or closed independently like tabs or accordion
[Bug 7746] <link rel=search> should be used instead of <input type=search> for backwards-compatibility and beacuse the search input type poses no additional input restrictions.