public-html-bugzilla@w3.org from March 2010: by date

Wednesday, 31 March 2010
- [Bug 9122] Obsolete but Conforming bugzilla@wiggum.w3.org
- [Bug 9061] allow image maps on the canvas element. bugzilla@wiggum.w3.org
- [Bug 9061] allow image maps on the canvas element. bugzilla@wiggum.w3.org
- [Bug 9380] New: If contenteditable is true, this *should* mean that the *content* of the element is editable, not the element itself. For example, if the user selects "mytext" in <div contenteditable=true>mytext</div>, and then invokes execCommand('bold'), this should wr bugzilla@wiggum.w3.org
- [Bug 9379] New: If contenteditable is true, this *should* mean that the *content* of the element is editable, not the element itself. For example, if the user selects "mytext" in <div contenteditable=true>mytext</div>, and then invokes execCommand('bold'), this should wr bugzilla@wiggum.w3.org
- [Bug 9061] allow image maps on the canvas element. bugzilla@wiggum.w3.org
- [Bug 9378] New: It is confusing that rank is defined in terms of h1-h6 elements and then later the behaviour for hgroup is tacked on. It would be clearer to define rank further down for everything all at once bugzilla@wiggum.w3.org
- [Bug 9051] feed autodiscovery for main feed on posts bugzilla@wiggum.w3.org
- [Bug 9135] provide an inline link in the canvas section to the 2d context spec bugzilla@wiggum.w3.org
- [Bug 9135] provide an inline link in the canvas section to the 2d context spec bugzilla@wiggum.w3.org
- [Bug 9057] status section, ref to "HTML specifications" bugzilla@wiggum.w3.org
- [Bug 9061] allow image maps on the canvas element. bugzilla@wiggum.w3.org
- [Bug 9051] feed autodiscovery for main feed on posts bugzilla@wiggum.w3.org
- [Bug 9051] feed autodiscovery for main feed on posts bugzilla@wiggum.w3.org
- [Bug 9122] Obsolete but Conforming bugzilla@wiggum.w3.org
- [Bug 9354] Leading/trailing whitespace in attributes that take a URL should be conforming bugzilla@wiggum.w3.org
- [Bug 9099] suggestion; use list for <br> non-conforming example form alternative bugzilla@wiggum.w3.org
- [Bug 9289] What about polyglot documents which are *both* HTML5 and XHTML5 ? I think it would make a lot of sense to spend a few words on that because virtually nobody will use XHMTL5 with the correct MIME-type because of the legacy browsers. bugzilla@wiggum.w3.org
- [Bug 7158] this is a discribing comment bugzilla@wiggum.w3.org
- [Bug 9281] The sentence "When used to include data blocks..." would benefit from clarification: "When used to include non-JavaScript data blocks..." bugzilla@wiggum.w3.org
- [Bug 9281] The sentence "When used to include data blocks..." would benefit from clarification: "When used to include non-JavaScript data blocks..." bugzilla@wiggum.w3.org
- [Bug 9278] "...with the same argument, the user agent **may** return the same object as the object returned by the earlier call.": Make this a must. To quote hsivonen, "The Web leaves no edge case unexercised." bugzilla@wiggum.w3.org
- [Bug 9270] Add <dialog> back bugzilla@wiggum.w3.org
- [Bug 9354] Leading/trailing whitespace in attributes that take a URL should be conforming bugzilla@wiggum.w3.org
- [Bug 8116] URNs are URIs but not URLs bugzilla@wiggum.w3.org
- [Bug 7721] Drag and Drop is not keyboard accessible bugzilla@wiggum.w3.org
- [Bug 9272] This admonition should probably be marked as “Important” rather than “Note”, because of the consequences confusing the definitions of whitespace could have. bugzilla@wiggum.w3.org
- [Bug 9260] On one extreme, we have parentheses. On the other extreme, we have sidebars. But in the middle ground, we have footnotes. How should footnotes be handled if <aside> is not the right way to do it? bugzilla@wiggum.w3.org
- [Bug 9267] Allow alternative of simple <h> element that uses ancestors to determine hierarchy. (Or take a lesson from DocBook and reuse the <title> element, allowing its semantic meaning to change depending on the context.) bugzilla@wiggum.w3.org
- [Bug 7444] EUC-JP and ISO-2022-JP also need replacement encodings: CP51932 (or eucJP-ms) and CP50221. bugzilla@wiggum.w3.org
- [Bug 9265] Although I’m loving the spec in general, what about a generic <h>header</h> element that can be nested? After all, we are not writing <section1>, <section2>, <section3>, and so on … bugzilla@wiggum.w3.org
- [Bug 9233] Incorporate a Link to UAAG with appropriate wording into browser sections bugzilla@wiggum.w3.org
- [Bug 9326] HTML elements mapping to ARIA and A11y APIs bugzilla@wiggum.w3.org
- [Bug 9259] clarification needed: "one big page with a scrollbar would be equivalent" Many readers might think as I did, "equivalent to what?" On reflection, I understand -- to the tabbed interface -- but the language could be clearer. bugzilla@wiggum.w3.org
- [Bug 9259] clarification needed: "one big page with a scrollbar would be equivalent" Many readers might think as I did, "equivalent to what?" On reflection, I understand -- to the tabbed interface -- but the language could be clearer. bugzilla@wiggum.w3.org
- [Bug 9151] The first item in the list seems truncated or not in item list form. It ends "and," bugzilla@wiggum.w3.org
- [Bug 9151] The first item in the list seems truncated or not in item list form. It ends "and," bugzilla@wiggum.w3.org
- [Bug 9153] The element list isn't in alphabetical order (unlike the same element list further down). bugzilla@wiggum.w3.org
- [Bug 9354] Leading/trailing whitespace in attributes that take a URL should be conforming bugzilla@wiggum.w3.org
- [Bug 9153] The element list isn't in alphabetical order (unlike the same element list further down). bugzilla@wiggum.w3.org
- [Bug 9249] Step 9.4 s/is are/are/ bugzilla@wiggum.w3.org
- [Bug 9249] Step 9.4 s/is are/are/ bugzilla@wiggum.w3.org
- [Bug 9152] The list of elements doesn't include elements like input, select (and probably others) that are includes in MSIE. bugzilla@wiggum.w3.org
- [Bug 9179] <body><section> results in <section> being associated with the <body> element's section. I'd expect <section> to be associated with its own section. bugzilla@wiggum.w3.org
- [Bug 9177] Can the script element please allow the scope attribute in the same semantic way as the style element? The dom would be limited to only elements under that node. bugzilla@wiggum.w3.org
- [Bug 9180] "The event thus is not to be fired faster than about 66Hz or slower than 4Hz." - unless the event handler is still running, in which case it could be slower bugzilla@wiggum.w3.org
- [Bug 9180] "The event thus is not to be fired faster than about 66Hz or slower than 4Hz." - unless the event handler is still running, in which case it could be slower bugzilla@wiggum.w3.org
- [Bug 9188] Fix the references in the txt version to have URLs. bugzilla@wiggum.w3.org
- [Bug 9251] "When content fails to load (e.g. due to a network error), then the user agent must queue a task to fire a simple event named error at the element instead." is pretty vague (e.g. do bad URLs fire onerror? cross-domain failures?) Same applies to <frame>. bugzilla@wiggum.w3.org
- [Bug 9251] "When content fails to load (e.g. due to a network error), then the user agent must queue a task to fire a simple event named error at the element instead." is pretty vague (e.g. do bad URLs fire onerror? cross-domain failures?) Same applies to <frame>. bugzilla@wiggum.w3.org
- [Bug 7670] Use of prefixes is too complicated for a Web technology bugzilla@wiggum.w3.org
- [Bug 7670] Use of prefixes is too complicated for a Web technology bugzilla@wiggum.w3.org
- [Bug 7670] Use of prefixes is too complicated for a Web technology bugzilla@wiggum.w3.org
- [Bug 9375] New: progress uses ProgressEvent bugzilla@wiggum.w3.org
- [Bug 9365] Attribute selectors for HTML5 audio and video should be listed as case insensitive bugzilla@wiggum.w3.org
- [Bug 9372] html 5 bugzilla@wiggum.w3.org
- [Bug 7670] Use of prefixes is too complicated for a Web technology bugzilla@wiggum.w3.org
- [Bug 7471] JimJJewett gmail: Make explicit reasons for *not* exposing aspect ratio/clipping. (Security vs simplification). Deals with http://www.w3.org/AudioVideo/2007/12/SMIL-AudioVideoControlConcepts.html#L2398 note1 bugzilla@wiggum.w3.org
- [Bug 9374] New: implementation of dash-styles for lines as seen in the pdf-specification would be nice (would require two additional parameters, "dashStyle" and "dashLength", for example) bugzilla@wiggum.w3.org
- [Bug 9242] It is not clear whether "shortcut icon" is a valid keyword; it is widely used and seems to validate in the experimental HTML5 validator. bugzilla@wiggum.w3.org
- [Bug 9247] last note states small does not de-emphasize. This naturally leads to the question what does. Answer that question bugzilla@wiggum.w3.org
- [Bug 9247] last note states small does not de-emphasize. This naturally leads to the question what does. Answer that question bugzilla@wiggum.w3.org
- [Bug 7471] JimJJewett gmail: Make explicit reasons for *not* exposing aspect ratio/clipping. (Security vs simplification). Deals with http://www.w3.org/AudioVideo/2007/12/SMIL-AudioVideoControlConcepts.html#L2398 note1 bugzilla@wiggum.w3.org
- [Bug 6763] Inconsistent use of American and British English bugzilla@wiggum.w3.org
- [Bug 6763] Inconsistent use of American and British English bugzilla@wiggum.w3.org
- [Bug 9245] Poster should somehow also be able to define a frame (or timeline position) to be used as the frame. bugzilla@wiggum.w3.org
- [Bug 9242] It is not clear whether "shortcut icon" is a valid keyword; it is widely used and seems to validate in the experimental HTML5 validator. bugzilla@wiggum.w3.org
- [Bug 9244] "if the values used are not allowed according to the definitions in this specification, then the element does not define a link": What should happen if one value is valid and one isn't? bugzilla@wiggum.w3.org
- [Bug 9244] "if the values used are not allowed according to the definitions in this specification, then the element does not define a link": What should happen if one value is valid and one isn't? bugzilla@wiggum.w3.org
- [Bug 8321] change controller for HTML media type bugzilla@wiggum.w3.org
- [Bug 9202] This comment overlays found text in my Firefox 3.0.18, which is bad. bugzilla@wiggum.w3.org
- [Bug 9372] New: html 5 bugzilla@wiggum.w3.org
- [Bug 9253] Calling putImageData() should force browsers to render the canvas to screen, otherwise animations won't work. bugzilla@wiggum.w3.org
- [Bug 9243] This section should print the character in addition to its unicode number. bugzilla@wiggum.w3.org
- [Bug 9243] This section should print the character in addition to its unicode number. bugzilla@wiggum.w3.org
- [Bug 9371] New: I misinterpreted "represents a paragraph-level thematic break" to mean "should occur between paragraphs". Might be nice to add "can be used anywhere the p element is used", or to mention "for rendering or analysis purposes" or "most flow elements are para bugzilla@wiggum.w3.org
- [Bug 8321] change controller for HTML media type bugzilla@wiggum.w3.org
Tuesday, 30 March 2010
- [Bug 9240] rules for td[align=center] are missing bugzilla@wiggum.w3.org
- [Bug 9240] rules for td[align=center] are missing bugzilla@wiggum.w3.org
- [Bug 9236] Add Path objects and intersects() function bugzilla@wiggum.w3.org
- [Bug 9232] name=size should also be highlighted bugzilla@wiggum.w3.org
- [Bug 9226] The subcategories of form-associated elements should have consistent naming. Probably all of them should end in "elements". bugzilla@wiggum.w3.org
- [Bug 9226] The subcategories of form-associated elements should have consistent naming. Probably all of them should end in "elements". bugzilla@wiggum.w3.org
- [Bug 9224] It should be mentioned that setting playbackRate can be ignored. I.e. if playing backwards is not supported by the codec, if hardware acceleration does not support it, etc. bugzilla@wiggum.w3.org
- [Bug 9223] It is unlikely this will work on mobile as you cannot make tcp connections into a mobile phone. They will be blocked by the operator's firewall and this is very unlikely to change. Of course, this isn't a reason not to specify this, but it's good to be aw bugzilla@wiggum.w3.org
- [Bug 9220] xref doesn't work for "bgcolor" in "When a body, table, thead, tbody, tfoot, tr, td, or th element has a bgcolor attribute set" bugzilla@wiggum.w3.org
- [Bug 9211] slotIndices (new IDL attribute): collection of all col-row intersections (slots) the cell spans bugzilla@wiggum.w3.org
- [Bug 9210] colSpan: there is no default value (rowSpan has one) bugzilla@wiggum.w3.org
- [Bug 9209] sectionRowIndex: check text in parentheses, seems redundant bugzilla@wiggum.w3.org
- [Bug 9209] sectionRowIndex: check text in parentheses, seems redundant bugzilla@wiggum.w3.org
- [Bug 9208] “isn't” – either “s not” or “isn’t” bugzilla@wiggum.w3.org
- [Bug 9030] Add more dfns (more helpful list coming) bugzilla@wiggum.w3.org
- [Bug 9202] This comment overlays found text in my Firefox 3.0.18, which is bad. bugzilla@wiggum.w3.org
- [Bug 9206] "datetime content attribute" xref is dead bugzilla@wiggum.w3.org
- [Bug 9206] "datetime content attribute" xref is dead bugzilla@wiggum.w3.org
- [Bug 9205] I'm missing a specification on the relation between onreadystatechange and onload. Will they be used interchangeably? When will they fire? Will onreadystatechange fire multiple times during downloading an external resource (readystate="loading")? bugzilla@wiggum.w3.org
- [Bug 9205] I'm missing a specification on the relation between onreadystatechange and onload. Will they be used interchangeably? When will they fire? Will onreadystatechange fire multiple times during downloading an external resource (readystate="loading")? bugzilla@wiggum.w3.org
- [Bug 9204] The onload event is missing a description on when it fires. Particularly on elements downloading auxiliary documents (img, script, link) it is important to specify when exactly that event is fired. Same for onerror and onabort events (and similar). bugzilla@wiggum.w3.org
- [Bug 9202] This comment overlays found text in my Firefox 3.0.18, which is bad. bugzilla@wiggum.w3.org
- [Bug 9201] xref getElementById() bugzilla@wiggum.w3.org
- [Bug 9200] xref document.getElementById(), and clarify on which document it should be called. bugzilla@wiggum.w3.org
- [Bug 9200] xref document.getElementById(), and clarify on which document it should be called. bugzilla@wiggum.w3.org
- [Bug 9200] xref document.getElementById(), and clarify on which document it should be called. bugzilla@wiggum.w3.org
- [Bug 9199] [a-urn] xref "href" bugzilla@wiggum.w3.org
- [Bug 9198] <embed hspace> and <embed vspace> should not be allowed bugzilla@wiggum.w3.org
- [Bug 9199] [a-urn] xref "href" bugzilla@wiggum.w3.org
- [Bug 9198] <embed hspace> and <embed vspace> should not be allowed bugzilla@wiggum.w3.org
- [Bug 9145] steps 1 to 3 could be merged into "A string that is an ASCII case-insensitive match for the string "<!DOCTYPE"" bugzilla@wiggum.w3.org
- [Bug 9195] the icns format does not support such ridiculously huge icon sizes! Where can I get an 8k x 8k screen please? printing would use the SVG anyway. bugzilla@wiggum.w3.org
- [Bug 9145] steps 1 to 3 could be merged into "A string that is an ASCII case-insensitive match for the string "<!DOCTYPE"" bugzilla@wiggum.w3.org
- [Bug 9193] "If hash changed is true, then, if the new URL has a fragment identifier, scroll to the fragment identifier." is wrong. It should scroll if it's a new entry that hasn't been traversed to before, even if it's the same fragid as before; and it should _not_ bugzilla@wiggum.w3.org
- [Bug 9193] "If hash changed is true, then, if the new URL has a fragment identifier, scroll to the fragment identifier." is wrong. It should scroll if it's a new entry that hasn't been traversed to before, even if it's the same fragid as before; and it should _not_ bugzilla@wiggum.w3.org
- [Bug 7034] authoring conformance requirements in the spec should either be removed or replaced bugzilla@wiggum.w3.org
- [Bug 8321] change controller for HTML media type bugzilla@wiggum.w3.org
- [Bug 8321] change controller for HTML media type bugzilla@wiggum.w3.org
- [Bug 8321] change controller for HTML media type bugzilla@wiggum.w3.org
- [Bug 9366] Add |addClass|, |removeClass|, and shorten |getElementsByClassName| to |getElementsByClass| for |HTMLElement|. bugzilla@wiggum.w3.org
- [Bug 7468] make <table border="1" cellpadding="10" cellspacing="0"> conforming bugzilla@wiggum.w3.org
- [Bug 9369] New: Propose Changing Content model to phrasing content model bugzilla@wiggum.w3.org
- [Bug 8784] politics in <param> example bugzilla@wiggum.w3.org
- [Bug 8793] registration procedure for@rel values bugzilla@wiggum.w3.org
- [Bug 8321] change controller for HTML media type bugzilla@wiggum.w3.org
- [Bug 8252] HTTP caching rules are _ignored_? What's wrong with extending Cache-Control to support user-agent caching instead of coming up with an entirely new mechanism? bugzilla@wiggum.w3.org
- [Bug 9367] New: fixe broken links in IDLs by changing id references of hyperlinks in IDLs to point to content in domintro boxes instead of UA implementation details bugzilla@wiggum.w3.org
- [Bug 9080] Confusing alt text in the second The Lady of Shalott example bugzilla@wiggum.w3.org
- [Bug 9366] New: Add |addClass|, |removeClass|, and shorten |getElementsByClassName| to |getElementsByClass| for |HTMLElement|. bugzilla@wiggum.w3.org
- [Bug 8207] Change definition of URL to normative reference to IRIBIS bugzilla@wiggum.w3.org
- [Bug 8207] Change definition of URL to normative reference to IRIBIS bugzilla@wiggum.w3.org
- [Bug 7391] Reference to WEBADDRESS should be replaced with reference to IRIbis bugzilla@wiggum.w3.org
- [Bug 7657] Redefining dt and dd bugzilla@wiggum.w3.org
- [Bug 8246] what about IE parsing problems? http://html5doctor.com/dd-details-wrong-again/ bugzilla@wiggum.w3.org
- [Bug 6853] restore meta keywords, search engines use them bugzilla@wiggum.w3.org
- [Bug 8784] politics in <param> example bugzilla@wiggum.w3.org
- [Bug 8793] registration procedure for@rel values bugzilla@wiggum.w3.org
- [Bug 9081] Confusing alt text in the fourth The Lady of Shalott example bugzilla@wiggum.w3.org
- [Bug 9160] input['type=checkbox'].checkValidity ought to work like the radio type, testing the whole checkbox group, not each checkbox individually bugzilla@wiggum.w3.org
- [Bug 8321] change controller for HTML media type bugzilla@wiggum.w3.org
- [Bug 9160] input['type=checkbox'].checkValidity ought to work like the radio type, testing the whole checkbox group, not each checkbox individually bugzilla@wiggum.w3.org
- [Bug 8252] HTTP caching rules are _ignored_? What's wrong with extending Cache-Control to support user-agent caching instead of coming up with an entirely new mechanism? bugzilla@wiggum.w3.org
- [Bug 9160] input['type=checkbox'].checkValidity ought to work like the radio type, testing the whole checkbox group, not each checkbox individually bugzilla@wiggum.w3.org
- [Bug 9160] input['type=checkbox'].checkValidity ought to work like the radio type, testing the whole checkbox group, not each checkbox individually bugzilla@wiggum.w3.org
- [Bug 9191] Is there a way to get the text back out? e.g., context.getTexts returning an array of the character strings ever added with fillText and strokeText? -jJ bugzilla@wiggum.w3.org
- [Bug 9190] What effects do fillText and strokeText have on the accessibility fallback (ADOM?)? Should they take a default to also adding it, as by canvas.appendChild(document.createTextNode(s))? (Then maybe add a 5th parameter to allow turning it off) -jJ bugzilla@wiggum.w3.org
- [Bug 9186] @abbr (td/th): may authors use @title instead? bugzilla@wiggum.w3.org
- [Bug 9155] "The attribute must be ignored if the autoplay attribute is present." - seems wrong when the user has set a pref to make autoplay="" not autoplay bugzilla@wiggum.w3.org
- [Bug 9160] input['type=checkbox'].checkValidity ought to work like the radio type, testing the whole checkbox group, not each checkbox individually bugzilla@wiggum.w3.org
- [Bug 9182] Can I nest <ruby> elements? I think that you should add content model of the <ruby> element, "but there must be no ruby element descendants.". bugzilla@wiggum.w3.org
- [Bug 9181] Find the effectAllowed line bugzilla@wiggum.w3.org
- [Bug 9155] "The attribute must be ignored if the autoplay attribute is present." - seems wrong when the user has set a pref to make autoplay="" not autoplay bugzilla@wiggum.w3.org
- [Bug 9176] typo in 4th |th|: ‘per _c_ent’ (or rather ‘percent’) and please be metric, not inchic bugzilla@wiggum.w3.org
- [Bug 9175] should clearly say that cellIndex is not necessarily the same as slot_x (and there should be easy access to slot_x and slot_y) bugzilla@wiggum.w3.org
- [Bug 9175] should clearly say that cellIndex is not necessarily the same as slot_x (and there should be easy access to slot_x and slot_y) bugzilla@wiggum.w3.org
- [Bug 9173] This section should have a stable id so that http://dev.w3.org/html5/tests/submission/Microsoft/windowobject/security_location_0.htm can link to it bugzilla@wiggum.w3.org
- [Bug 9173] This section should have a stable id so that http://dev.w3.org/html5/tests/submission/Microsoft/windowobject/security_location_0.htm can link to it bugzilla@wiggum.w3.org
- [Bug 9168] iframeborder -> frameborder bugzilla@wiggum.w3.org
- [Bug 9168] iframeborder -> frameborder bugzilla@wiggum.w3.org
- [Bug 9164] If maxWidth = 0, repeatedly choosing smaller font sizes will never result in a zero-width piece of text, so steps 3-4 loop infinitely; there should be some way to e.g. abort and draw nothing if maxWidth is too small. [pt] bugzilla@wiggum.w3.org
- [Bug 9163] The domintro box only has document.dir, and ought to have element.dir too. [pt] bugzilla@wiggum.w3.org
- [Bug 9162] please define authors' requirements and non-normative introduction for authors to HTML's fragment identifiers bugzilla@wiggum.w3.org
- [Bug 9161] it should explicitly say alt="" MUST NOT be blank unless it MAY be left blank bugzilla@wiggum.w3.org
- [Bug 9161] it should explicitly say alt="" MUST NOT be blank unless it MAY be left blank bugzilla@wiggum.w3.org
- [Bug 9160] input['type=checkbox'].checkValidity ought to work like the radio type, testing the whole checkbox group, not each checkbox individually bugzilla@wiggum.w3.org
- [Bug 9365] New: Attribute selectors for HTML5 audio and video should be listed as case insensitive bugzilla@wiggum.w3.org
Monday, 29 March 2010
- [Bug 9159] metadata keyword description - "Hints to the user agent that the author either does not expect the user to need the media resource...". The word "either" seems to be unnecessary. bugzilla@wiggum.w3.org
- [Bug 9143] The b element lacks encouragement to use classes (cf i element) bugzilla@wiggum.w3.org
- [Bug 9143] The b element lacks encouragement to use classes (cf i element) bugzilla@wiggum.w3.org
- [Bug 9080] Confusing alt text in the second The Lady of Shalott example bugzilla@wiggum.w3.org
- [Bug 9364] New: s/dom-MessagpePort-postMessage/dom-MessagePort-postMessage/ bugzilla@wiggum.w3.org
- [Bug 7681] link tag: rel: associate pages about the same person across many sites bugzilla@wiggum.w3.org
- [Bug 9081] Confusing alt text in the fourth The Lady of Shalott example bugzilla@wiggum.w3.org
- [Bug 9081] Confusing alt text in the fourth The Lady of Shalott example bugzilla@wiggum.w3.org
- [Bug 9081] Confusing alt text in the fourth The Lady of Shalott example bugzilla@wiggum.w3.org
- [Bug 9077] Lady of Shalott example doesn't really "enhance the themes or subject matter of the page content" bugzilla@wiggum.w3.org
- [Bug 9077] Lady of Shalott example doesn't really "enhance the themes or subject matter of the page content" bugzilla@wiggum.w3.org
- [Bug 9077] Lady of Shalott example doesn't really "enhance the themes or subject matter of the page content" bugzilla@wiggum.w3.org
- [Bug 9081] Confusing alt text in the fourth The Lady of Shalott example bugzilla@wiggum.w3.org
- [Bug 9081] Confusing alt text in the fourth The Lady of Shalott example bugzilla@wiggum.w3.org
- [Bug 9077] Lady of Shalott example doesn't really "enhance the themes or subject matter of the page content" bugzilla@wiggum.w3.org
- [Bug 9080] Confusing alt text in the second The Lady of Shalott example bugzilla@wiggum.w3.org
- [Bug 9079] Mis-use of <h2> in The Lady of Shalott examples bugzilla@wiggum.w3.org
- [Bug 9131] please elaborate on "If there is no relevant pointing device" - how can you get the mouse position on the drag or dragend events? bugzilla@wiggum.w3.org
- [Bug 9207] Anything else: This part of the spec is problematic, for example, a query string variable &lang_id=1 in as part of an attribute of say an img tag, will get converted into an character token when it shouldn't be. Why is the set of characters a-z, A-Z, 0- bugzilla@wiggum.w3.org
- [Bug 9207] Anything else: This part of the spec is problematic, for example, a query string variable &lang_id=1 in as part of an attribute of say an img tag, will get converted into an character token when it shouldn't be. Why is the set of characters a-z, A-Z, 0- bugzilla@wiggum.w3.org
- [Bug 9351] Do not interpret & followed by an entity name followed by = as an entity reference in attribute values (maybe in text content too) bugzilla@wiggum.w3.org
- [Bug 9351] Do not interpret & followed by an entity name followed by = as an entity reference (possibly just in attribute values) bugzilla@wiggum.w3.org
- [Bug 9351] Do not interpret & followed by an entity name followed by = as an entity reference (possibly just in attribute values) bugzilla@wiggum.w3.org
- [Bug 9351] Do not interpret & followed by an entity name followed by = as an entity reference in attribute values bugzilla@wiggum.w3.org
- [Bug 9154] the message in dom-intro boxes look like "issue" boxes. could you make them look less like issue boxes? e.g. be styled the same way as other "this section is non-normative" paragraphs; possibly have .impl style (so they get highlighted in highlight UA tex bugzilla@wiggum.w3.org
- [Bug 9154] the message in dom-intro boxes look like "issue" boxes. could you make them look less like issue boxes? e.g. be styled the same way as other "this section is non-normative" paragraphs; possibly have .impl style (so they get highlighted in highlight UA tex bugzilla@wiggum.w3.org
- [Bug 9149] Don't require set-cookie2; see <https://bugzilla.mozilla.org/show_bug.cgi?id=472529#c129> bugzilla@wiggum.w3.org
- [Bug 9149] Don't require set-cookie2; see <https://bugzilla.mozilla.org/show_bug.cgi?id=472529#c129> bugzilla@wiggum.w3.org
- [Bug 9148] "either does not expect the user to need the media resource, but that" -- "either ... but" is wrong, this needs to be reworded. bugzilla@wiggum.w3.org
- [Bug 9148] "either does not expect the user to need the media resource, but that" -- "either ... but" is wrong, this needs to be reworded. bugzilla@wiggum.w3.org
- [Bug 9141] 10.2.2.2: overriding explicitly declared encodings is a bad idea maybe make this only for when both HTTP and HTML didn't specify the encoding bugzilla@wiggum.w3.org
- [Bug 9137] i'd like to encode a geographical position in the format like <span itemprop=geo itemvalue="lat;lon">HUMAN-FRIENDLY- and LOCALIZED-LAT, LON</span>, but current microdata syntax does not allow it. <meta itemprop=geo content=...> could be used, but contain bugzilla@wiggum.w3.org
- [Bug 9133] "if it is a number between 0.0 and 1.0" - does 'between' mean inclusive or exclusive? bugzilla@wiggum.w3.org
- [Bug 9133] "if it is a number between 0.0 and 1.0" - does 'between' mean inclusive or exclusive? bugzilla@wiggum.w3.org
- [Bug 9132] "if it is a number between 0.0 and 1.0" - what is a number? Is it something that WebIDL converts to an IDL double value in its 'any' conversion? Or does toDataURL("image/jpeg", "0.5") count as a number too? bugzilla@wiggum.w3.org
- [Bug 9132] "if it is a number between 0.0 and 1.0" - what is a number? Is it something that WebIDL converts to an IDL double value in its 'any' conversion? Or does toDataURL("image/jpeg", "0.5") count as a number too? bugzilla@wiggum.w3.org
- [Bug 9129] The terms used from the DOM specification need some <code> love. bugzilla@wiggum.w3.org
- [Bug 9131] please elaborate on "If there is no relevant pointing device" - how can you get the mouse position on the drag or dragend events? bugzilla@wiggum.w3.org
- [Bug 9129] The terms used from the DOM specification need some <code> love. bugzilla@wiggum.w3.org
- [Bug 9124] missing formatBlock candidates bugzilla@wiggum.w3.org
- [Bug 9124] missing formatBlock candidates bugzilla@wiggum.w3.org
- [Bug 9362] <embed> should fire 'load' event so that it's more useful for e.g. SVG bugzilla@wiggum.w3.org
- [Bug 9121] "Returns the one-dimensional array containing the data." - should say "in RGBA order, as integers in the range 0 .. 255", so that it's giving the information authors need to know. [pt] bugzilla@wiggum.w3.org
- [Bug 9120] "The allowed values for repeat are repeat" - should be "allowed values for <var>repetition</var>" [pt] bugzilla@wiggum.w3.org
- [Bug 9121] "Returns the one-dimensional array containing the data." - should say "in RGBA order, as integers in the range 0 .. 255", so that it's giving the information authors need to know. [pt] bugzilla@wiggum.w3.org
- [Bug 9120] "The allowed values for repeat are repeat" - should be "allowed values for <var>repetition</var>" [pt] bugzilla@wiggum.w3.org
- [Bug 9119] "Gradients must be painted only where ..." - this sentence applies to all gradients (not just radial), so it should be placed after the following sentence ("The points in the radial gradient ..."), so that all the radial-specific sentences are kept togthe bugzilla@wiggum.w3.org
- [Bug 9118] "If either of the radii are negative throws an INDEX_SIZE_ERR exception." - s/throws/, throws/ [pt] bugzilla@wiggum.w3.org
- [Bug 9117] "Throws an INDEX_SIZE_ERR exception if the offset it out of range" - s/it/is/ [pt] bugzilla@wiggum.w3.org
- [Bug 9118] "If either of the radii are negative throws an INDEX_SIZE_ERR exception." - s/throws/, throws/ [pt] bugzilla@wiggum.w3.org
- [Bug 9117] "Throws an INDEX_SIZE_ERR exception if the offset it out of range" - s/it/is/ [pt] bugzilla@wiggum.w3.org
- [Bug 9113] re: "axis on td and th elements" text could say "Use the scope attribute on the relevant th" bugzilla@wiggum.w3.org
- [Bug 9116] Will we be to manipulate the address via JavaScript without the # to get true deeplinking? bugzilla@wiggum.w3.org
- [Bug 9113] re: "axis on td and th elements" text could say "Use the scope attribute on the relevant th" bugzilla@wiggum.w3.org
- [Bug 9114] "If the second argument isn't one of the allowed values, throws a SYNTAX_ERR exception." - incorrect copy-and-paste from the createPattern text bugzilla@wiggum.w3.org
- [Bug 9114] "If the second argument isn't one of the allowed values, throws a SYNTAX_ERR exception." - incorrect copy-and-paste from the createPattern text bugzilla@wiggum.w3.org
- [Bug 9106] Description of the commandType attribute talks about a value of "checked". Should be "checkbox". bugzilla@wiggum.w3.org
- [Bug 9106] Description of the commandType attribute talks about a value of "checked". Should be "checkbox". bugzilla@wiggum.w3.org
- [Bug 9101] How noHref "reflect"s nohref is not well defined; nohref is not explicitly mentioned as a "boolean attribute" bugzilla@wiggum.w3.org
- [Bug 9101] How noHref "reflect"s nohref is not well defined; nohref is not explicitly mentioned as a "boolean attribute" bugzilla@wiggum.w3.org
- [Bug 9104] there were <link urn=""> and <link methods="">, too. [RFC1866] bugzilla@wiggum.w3.org
- [Bug 9104] there were <link urn=""> and <link methods="">, too. [RFC1866] bugzilla@wiggum.w3.org
- [Bug 9102] this CSS style sheet does not work because "type" attribute values are compared case-insensitively according to the "Matching HTML elements using selectors" section bugzilla@wiggum.w3.org
- [Bug 9102] this CSS style sheet does not work because "type" attribute values are compared case-insensitively according to the "Matching HTML elements using selectors" section bugzilla@wiggum.w3.org
- [Bug 9350] Make <wbr> element conforming bugzilla@wiggum.w3.org
- [Bug 9103] 'padding-left' here should be marked as LTR-specific bugzilla@wiggum.w3.org
- [Bug 9103] 'padding-left' here should be marked as LTR-specific bugzilla@wiggum.w3.org
- [Bug 9000] datasrc, <script event>, <script for> and so on are missing bugzilla@wiggum.w3.org
- [Bug 9350] Make <wbr> element conforming bugzilla@wiggum.w3.org
- [Bug 9000] datasrc, <script event>, <script for> and so on are missing bugzilla@wiggum.w3.org
- [Bug 9350] Make <wbr> element conforming bugzilla@wiggum.w3.org
- [Bug 9000] datasrc, <script event>, <script for> and so on are missing bugzilla@wiggum.w3.org
- [Bug 9215] Provide a Webcam example that is in accord with WCAG 2 or Defer to "HTML5: Techniques for providing useful text alternatives" bugzilla@wiggum.w3.org
- [Bug 9215] Provide a Webcam example that is in accord with WCAG 2 or Defer to "HTML5: Techniques for providing useful text alternatives" bugzilla@wiggum.w3.org
Sunday, 28 March 2010
- [Bug 9362] New: <embed> should fire 'load' event so that it's more useful for e.g. SVG bugzilla@wiggum.w3.org
- [Bug 7468] make <table border="1" cellpadding="10" cellspacing="0"> conforming bugzilla@wiggum.w3.org
- [Bug 9079] Mis-use of <h2> in The Lady of Shalott examples bugzilla@wiggum.w3.org
- [Bug 9081] Confusing alt text in the fourth The Lady of Shalott example bugzilla@wiggum.w3.org
- [Bug 9080] Confusing alt text in the second The Lady of Shalott example bugzilla@wiggum.w3.org
- [Bug 9077] Lady of Shalott example doesn't really "enhance the themes or subject matter of the page content" bugzilla@wiggum.w3.org
- [Bug 7468] make <table border="1" cellpadding="10" cellspacing="0"> conforming bugzilla@wiggum.w3.org
- [Bug 9215] Provide a Webcam example that is in accord with WCAG 2 or Defer to "HTML5: Techniques for providing useful text alternatives" bugzilla@wiggum.w3.org
- [Bug 6610] add a preventable forced-fragment method bugzilla@wiggum.w3.org
- [Bug 7681] link tag: rel: associate pages about the same person across many sites bugzilla@wiggum.w3.org
- [Bug 7682] link tag: rel: associate pages about the same organization across many sites bugzilla@wiggum.w3.org
- [Bug 6853] restore meta keywords, search engines use them bugzilla@wiggum.w3.org
- [Bug 7525] meta/@name=keywords should be specified (and made conforming) bugzilla@wiggum.w3.org
- [Bug 6853] restore meta keywords, search engines use them bugzilla@wiggum.w3.org
- [Bug 6609] negative keywords-not meta tags bugzilla@wiggum.w3.org
- [Bug 9361] script element should be allowed essentially anywhere bugzilla@wiggum.w3.org
- [Bug 6609] negative keywords-not meta tags bugzilla@wiggum.w3.org
- [Bug 9361] New: script element should be allowed essentially anywhere bugzilla@wiggum.w3.org
- [Bug 9360] New: <iframe allowTransparency> should be mentioned in the obsolete section bugzilla@wiggum.w3.org
- [Bug 9359] New: hspace and vspace attributes should be listed in obsolete section bugzilla@wiggum.w3.org
- [Bug 9358] New: Explanation of content model requirements could be improved bugzilla@wiggum.w3.org
- [Bug 7682] link tag: rel: associate pages about the same organization across many sites bugzilla@wiggum.w3.org
- [Bug 7681] link tag: rel: associate pages about the same person across many sites bugzilla@wiggum.w3.org
- [Bug 7681] link tag: rel: associate pages about the same person across many sites bugzilla@wiggum.w3.org
- [Bug 6853] restore meta keywords, search engines use them bugzilla@wiggum.w3.org
- [Bug 6610] add a preventable forced-fragment method bugzilla@wiggum.w3.org
- [Bug 6609] negative keywords-not meta tags bugzilla@wiggum.w3.org
- [Bug 6610] add a preventable forced-fragment method bugzilla@wiggum.w3.org
- [Bug 6609] negative keywords-not meta tags bugzilla@wiggum.w3.org
- [Bug 7601] refer to pronunciations for TTS PLS with link rel value "pronunciation" bugzilla@wiggum.w3.org
- [Bug 7645] associate printable pages and less-convenient-to-print pages with link rel value "print" bugzilla@wiggum.w3.org
- [Bug 6606] generic 3rd-party <mark>, Smart Tags, and Accelerators prevention bugzilla@wiggum.w3.org
- [Bug 6774] <mark> element: restrict insertion by other servers bugzilla@wiggum.w3.org
- [Bug 9357] New: input element color state should be able to suffer from a type mismatch bugzilla@wiggum.w3.org
- [Bug 9355] Obsolete presentational markup should be conforming bugzilla@wiggum.w3.org
- [Bug 9356] New: Presumably "Errors that encourage a correct understanding of the spec" should read "an incorrect" instead of "a correct". bugzilla@wiggum.w3.org
- [Bug 9355] Many, most, or all obsolete features should be conforming bugzilla@wiggum.w3.org
- [Bug 9355] New: Many, most, or all obsolete features should be conforming bugzilla@wiggum.w3.org
- [Bug 7468] make <table border="1" cellpadding="10" cellspacing="0"> conforming bugzilla@wiggum.w3.org
- [Bug 9349] Make <nobr> element conforming bugzilla@wiggum.w3.org
Saturday, 27 March 2010
- [Bug 9354] New: Leading/trailing whitespace in attributes that take a URL should be conforming bugzilla@wiggum.w3.org
- [Bug 9353] New: autocomplete=off should be allowed and should work on non-<input> form controls bugzilla@wiggum.w3.org
- [Bug 9352] Make unescaped & conforming in attribute values in some cases bugzilla@wiggum.w3.org
- [Bug 9352] New: Make unescaped & conforming in attribute values in some cases bugzilla@wiggum.w3.org
- [Bug 9351] New: Do not interpret & followed by an entity name followed by = as an entity reference in attribute values bugzilla@wiggum.w3.org
- [Bug 9350] New: Make <wbr> element conforming bugzilla@wiggum.w3.org
- [Bug 9349] New: Make <nobr> element conforming bugzilla@wiggum.w3.org
- [Bug 9348] New: s/<span title="event-click">/<code title="event-click">/ bugzilla@wiggum.w3.org
- [Bug 9347] New: s/title="attr-href"/title="attr-a-href"/ bugzilla@wiggum.w3.org
- [Bug 9346] New: define attr-option-name bugzilla@wiggum.w3.org
- [Bug 9084] Opera's implementation of this treats the comma as a delimiter (i.e. if you select Abyssinian from the drop-down and type a ',' after that, it gives you the drop-down again to select another item). I like this feature but want to make sure it is interopab bugzilla@wiggum.w3.org
- [Bug 9345] New: "what matters for implementations it the presence of the attribute" - s/it/is/ [pt] bugzilla@wiggum.w3.org
- [Bug 9344] New: "constrolled" [pt] bugzilla@wiggum.w3.org
- [Bug 8967] Why is the optional argument in the middle? Isn't it more convenient when copy/pasting code to make optional modifications at either end without having to precisely place the cursor somewhere in the middle? Particularly for piecing together arguments, too bugzilla@wiggum.w3.org
- [Bug 9215] Provide a Webcam example that is in accord with WCAG 2 or Defer to "HTML5: Techniques for providing useful text alternatives" bugzilla@wiggum.w3.org
- [Bug 9343] New: s/inlien/inline/, s/this specifications makes it/this specification makes it/ bugzilla@wiggum.w3.org
- [Bug 7034] authoring conformance requirements in the spec should either be removed or replaced bugzilla@wiggum.w3.org
- [Bug 7034] authoring conformance requirements in the spec should either be removed or replaced bugzilla@wiggum.w3.org
Friday, 26 March 2010
- [Bug 9337] Frameset/Frame Specification Amendment bugzilla@wiggum.w3.org
- [Bug 9337] Frameset/Frame Specification Amendment bugzilla@wiggum.w3.org
- [Bug 9340] New: "RCDATAs element" should be "RCDATA elements" (or rephrase to refer to a single element) bugzilla@wiggum.w3.org
- [Bug 9339] New: " Until the manifest is changed, those pages will not be fetched from the server again." WHAAAA? In order to get the benefits of app cached images and scripts and css, I have to have HTML pages that are never updated with fresh info, except when I change bugzilla@wiggum.w3.org
- [Bug 9338] New: Why can't I have the resource files (CSS file, images, JavaScript files) be cached without caching the whole page? I hacn't have a different HTML tag for just the sign-on page, and the other pages need to not be cached due to private, frequently changing bugzilla@wiggum.w3.org
- [Bug 9330] very gud bugzilla@wiggum.w3.org
- [Bug 9337] Frameset/Frame Specification Amendment bugzilla@wiggum.w3.org
- [Bug 9335] values need to be case-insensitive in xhtml too for the ua style sheet to work (e.g. <input type="HIDDEN"/>) bugzilla@wiggum.w3.org
- [Bug 9337] Frameset/Frame Specification Amendment bugzilla@wiggum.w3.org
- [Bug 9337] New: Frameset/Frame Specification Amendment bugzilla@wiggum.w3.org
- [Bug 9336] New: Remove concept of views as per discussion at least TPAC in the WebApps WG. At some point DOM Level 2 Views will be updated to recommend that implementors not implement the concept. bugzilla@wiggum.w3.org
- [Bug 9335] New: values need to be case-insensitive in xhtml too for the ua style sheet to work (e.g. <input type="HIDDEN"/>) bugzilla@wiggum.w3.org
- [Bug 9334] New: Markup error in decision-policy-v2.html bugzilla@wiggum.w3.org
- [Bug 9333] New: [ms] "The image argument is an instance of either HTMLImageElement, HTMLCanvasElement, or HTMLVideoElement. If the image is of the wrong type or null" WebIDL already ensures that it isn't of the wrong type, just check for null. bugzilla@wiggum.w3.org
- [Bug 9332] New: It's not clear that the (implied) HTML 4.01 use of tfoot is prohibited (which seems to demand content identical to thead). Or should duplicate thead content be allowed in tfoot? Section should also have a tfoot example with meaningful content (a failing o bugzilla@wiggum.w3.org
- [Bug 9331] New: "Columns can correspond to col elements, but in the absence of col elements are implied." appears to be missing a comma after "... but in the absence of col...". bugzilla@wiggum.w3.org
- [Bug 9330] New: very gud bugzilla@wiggum.w3.org
- [Bug 9329] New: drawImage filtering when dx and dy aren't integers needs defined bugzilla@wiggum.w3.org
Thursday, 25 March 2010
- [Bug 9326] New: HTML elements mapping to ARIA and A11y APIs bugzilla@wiggum.w3.org
- [Bug 7468] make <table border="1" cellpadding="10" cellspacing="0"> conforming bugzilla@wiggum.w3.org
- [Bug 7468] make <table border="1" cellpadding="10" cellspacing="0"> conforming bugzilla@wiggum.w3.org
- [Bug 9314] Include issue markers in drafts for issues that have been closed without prejudice bugzilla@wiggum.w3.org
- [Bug 9314] Include issue markers in drafts for issues that have been closed without prejudice bugzilla@wiggum.w3.org
- [Bug 9322] dsdfs fe efefaafd asd bugzilla@wiggum.w3.org
- [Bug 9322] New: dsdfs fe efefaafd asd bugzilla@wiggum.w3.org
- [Bug 9207] Anything else: This part of the spec is problematic, for example, a query string variable &lang_id=1 in as part of an attribute of say an img tag, will get converted into an character token when it shouldn't be. Why is the set of characters a-z, A-Z, 0- bugzilla@wiggum.w3.org
- [Bug 9316] Make rejected bugs more visible bugzilla@wiggum.w3.org
- [Bug 8896] Clarify that anyone who is dissatisfied with a bug resolution may reopen or escalate bugzilla@wiggum.w3.org
- [Bug 8893] Clarify how Change Proposals get reviewed and what happens to Change Proposals that do not meet requirements bugzilla@wiggum.w3.org
- [Bug 9318] The state for bugs with no reply should be CLOSED NoReply instead of VERIFIED NoReply bugzilla@wiggum.w3.org
- [Bug 9318] The state for bugs with no reply should be CLOSED NoReply instead of VERIFIED NoReply bugzilla@wiggum.w3.org
- [Bug 9318] New: The state for bugs with no reply should be CLOSED NoReply instead of VERIFIED NoReply bugzilla@wiggum.w3.org
- [Bug 9317] bug states should distinguish the true state of the bug bugzilla@wiggum.w3.org
- [Bug 9313] Use some state other than CLOSED for issues that are closed without prejudice, for lack of action by a deadline bugzilla@wiggum.w3.org
- [Bug 9313] Use some state other than CLOSED for issues that are closed without prejudice, for lack of action by a deadline bugzilla@wiggum.w3.org
- [Bug 9187] Need transparency in issue and bug status in databases & document. bugzilla@wiggum.w3.org
- [Bug 9317] New: bug states should distinguish the true state of the bug bugzilla@wiggum.w3.org
- [Bug 9316] New: Make rejected bugs more visible bugzilla@wiggum.w3.org
- [Bug 9315] New: Retain issue markers for issues that have timed out even during Last Call bugzilla@wiggum.w3.org
- [Bug 9314] New: Include issue markers in drafts for issues that have been closed without prejudice bugzilla@wiggum.w3.org
- [Bug 9313] Use some state other than CLOSED for issues that are closed without prejudice, for lack of action by a deadline bugzilla@wiggum.w3.org
- [Bug 9313] New: Use some state other than CLOSED for issues that are closed without prejudice, for lack of action by a deadline bugzilla@wiggum.w3.org
- [Bug 9187] Need transparency in issue and bug status in databases & document. bugzilla@wiggum.w3.org
- [Bug 9007] Clarify that bugs should not be reopened when escalating to the tracker bugzilla@wiggum.w3.org
- [Bug 9217] Remove the Paragraph-Section-Heading loophole for not providing a text alternative. bugzilla@wiggum.w3.org
- [Bug 9283] NEEDSINFO is a more appropriate resolution for bugs that are missing info than INVALID bugzilla@wiggum.w3.org
Wednesday, 24 March 2010
- [Bug 9311] New: Two instances of "(unless this has been overrriden as described above)" where: s/overrriden/overriden bugzilla@wiggum.w3.org
- [Bug 9307] I think the darker composite operation should be reintroduced. http://ajaxian.com/archives/harmony-canvas-drawing-tool for example. bugzilla@wiggum.w3.org
- [Bug 9308] I think the darker composite operation should be reintroduced. http://ajaxian.com/archives/harmony-canvas-drawing-tool for example. bugzilla@wiggum.w3.org
- [Bug 8896] Clarify that anyone who is dissatisfied with a bug resolution may reopen or escalate bugzilla@wiggum.w3.org
- [Bug 9309] New: "For the purposes of the CSS ruby model, runs of descendants of ruby elements ..." - s/descendants/children/ ? bugzilla@wiggum.w3.org
- [Bug 9308] New: I think the darker composite operation should be reintroduced. http://ajaxian.com/archives/harmony-canvas-drawing-tool for example. bugzilla@wiggum.w3.org
- [Bug 9307] New: I think the darker composite operation should be reintroduced. http://ajaxian.com/archives/harmony-canvas-drawing-tool for example. bugzilla@wiggum.w3.org
- [Bug 7670] Use of prefixes is too complicated for a Web technology bugzilla@wiggum.w3.org
- [Bug 9214] Allow role="presentation" on img bugzilla@wiggum.w3.org
- [Bug 9215] Provide a Webcam example that is in accord with WCAG 2 or Defer to "HTML5: Techniques for providing useful text alternatives" bugzilla@wiggum.w3.org
- [Bug 9215] Provide a Webcam example that is in accord with WCAG 2 or Defer to "HTML5: Techniques for providing useful text alternatives" bugzilla@wiggum.w3.org
- [Bug 9214] Allow role="presentation" on img bugzilla@wiggum.w3.org
- [Bug 7670] Use of prefixes is too complicated for a Web technology bugzilla@wiggum.w3.org
- [Bug 7670] Use of prefixes is too complicated for a Web technology bugzilla@wiggum.w3.org
- [Bug 7670] Use of prefixes is too complicated for a Web technology bugzilla@wiggum.w3.org
- [Bug 9214] Allow role="presentation" on img bugzilla@wiggum.w3.org
- [Bug 7525] meta/@name=keywords should be specified (and made conforming) bugzilla@wiggum.w3.org
- [Bug 9214] Allow role="presentation" on img bugzilla@wiggum.w3.org
- [Bug 9214] Allow role="presentation" on img bugzilla@wiggum.w3.org
- [Bug 9012] There is concern that continued development of HTML+RDFa belongs in a different working group. bugzilla@wiggum.w3.org
- [Bug 9011] There are discussions of alternate extensibility mechanisms, covered in [issue-41], which might allow other ways of integrating RDFa. bugzilla@wiggum.w3.org
- [Bug 7670] Use of prefixes is too complicated for a Web technology bugzilla@wiggum.w3.org
- [Bug 8976] Modifying the Input Document section is labeled as informative but include normative requirements bugzilla@wiggum.w3.org
- [Bug 8976] Modifying the Input Document section is labeled as informative but include normative requirements bugzilla@wiggum.w3.org
- [Bug 7670] Use of prefixes is too complicated for a Web technology bugzilla@wiggum.w3.org
- [Bug 9214] Allow role="presentation" on img bugzilla@wiggum.w3.org
- [Bug 9214] Allow role="presentation" on img bugzilla@wiggum.w3.org
- [Bug 9214] Allow role="presentation" on img bugzilla@wiggum.w3.org
- [Bug 9214] Allow role="presentation" on img bugzilla@wiggum.w3.org
- [Bug 9214] Allow role="presentation" on img bugzilla@wiggum.w3.org
- [Bug 9215] Provide a Webcam example that is in accord with WCAG 2 or Defer to "HTML5: Techniques for providing useful text alternatives" bugzilla@wiggum.w3.org
- [Bug 9214] Allow role="presentation" on img bugzilla@wiggum.w3.org
Tuesday, 23 March 2010
- [Bug 9215] Provide a Webcam example that is in accord with WCAG 2 or Defer to "HTML5: Techniques for providing useful text alternatives" bugzilla@wiggum.w3.org
- [Bug 9215] Provide a Webcam example that is in accord with WCAG 2 or Defer to "HTML5: Techniques for providing useful text alternatives" bugzilla@wiggum.w3.org
- [Bug 9215] Provide a Webcam example that is in accord with WCAG 2 or Defer to "HTML5: Techniques for providing useful text alternatives" bugzilla@wiggum.w3.org
- [Bug 9214] Allow role="presentation" on img bugzilla@wiggum.w3.org
- [Bug 9215] Provide a Webcam example that is in accord with WCAG 2 or Defer to "HTML5: Techniques for providing useful text alternatives" bugzilla@wiggum.w3.org
- [Bug 9214] Allow role="presentation" on img bugzilla@wiggum.w3.org
- [Bug 9215] Provide a Webcam example that is in accord with WCAG 2 or Defer to "HTML5: Techniques for providing useful text alternatives" bugzilla@wiggum.w3.org
- [Bug 9214] Allow role="presentation" on img bugzilla@wiggum.w3.org
- [Bug 9235] An additional useful transformation would be Perspective. bugzilla@wiggum.w3.org
- [Bug 8716] Replace img Guidance for Conformance Checkers with Suggested Text for Short Text Alternatives bugzilla@wiggum.w3.org
- [Bug 9218] Enable Automatic Validators to Programmatically Determine the Presence or Absence of a Set of Text Alternatives bugzilla@wiggum.w3.org
- [Bug 8872] split out and modify parts of Section 4.8.2.1 the img element bugzilla@wiggum.w3.org
- [Bug 8171] Implement the text alternatives proposal from WAI bugzilla@wiggum.w3.org
- [Bug 9218] Enable Automatic Validators to Programmatically Determine the Presence or Absence of a Set of Text Alternatives bugzilla@wiggum.w3.org
- [Bug 9217] Remove the Paragraph-Section-Heading loophole for not providing a text alternative. bugzilla@wiggum.w3.org
- [Bug 9217] Remove the Paragraph-Section-Heading loophole for not providing a text alternative. bugzilla@wiggum.w3.org
- [Bug 9218] Enable Automatic Validators to Programmatically Determine the Presence or Absence of a Set of Text Alternatives bugzilla@wiggum.w3.org
- [Bug 9217] Remove the Paragraph-Section-Heading loophole for not providing a text alternative. bugzilla@wiggum.w3.org
- [Bug 9217] Remove the Paragraph-Section-Heading loophole for not providing a text alternative. bugzilla@wiggum.w3.org
- [Bug 9217] Remove the Paragraph-Section-Heading loophole for not providing a text alternative. bugzilla@wiggum.w3.org
- [Bug 9216] Provide a CAPTCHA example that is in accord with WCAG 2 or Defer to "HTML5: Techniques for providing useful text alternatives" bugzilla@wiggum.w3.org
- [Bug 9212] Change the Generator Mechanism for img from Document Level to Element Level bugzilla@wiggum.w3.org
- [Bug 9215] Provide a Webcam example that is in accord with WCAG 2 or Defer to "HTML5: Techniques for providing useful text alternatives" bugzilla@wiggum.w3.org
- [Bug 7525] meta/@name=keywords should be specified (and made conforming) bugzilla@wiggum.w3.org
- [Bug 7525] meta/@name=keywords should be specified (and made conforming) bugzilla@wiggum.w3.org
- [Bug 9301] New: Don't support style like "Solid" "ShortDash" "ShortDot"? bugzilla@wiggum.w3.org
- [Bug 7525] meta/@name=keywords should be specified (and made conforming) bugzilla@wiggum.w3.org
- [Bug 9218] Enable Automatic Validators to Programmatically Determine the Presence or Absence of a Set of Text Alternatives bugzilla@wiggum.w3.org
- [Bug 9217] Remove the Paragraph-Section-Heading loophole for not providing a text alternative. bugzilla@wiggum.w3.org
- [Bug 9216] Provide a CAPTCHA example that is in accord with WCAG 2 or Defer to "HTML5: Techniques for providing useful text alternatives" bugzilla@wiggum.w3.org
- [Bug 9212] Change the Generator Mechanism for img from Document Level to Element Level bugzilla@wiggum.w3.org
- [Bug 9215] Provide a Webcam example that is in accord with WCAG 2 or Defer to "HTML5: Techniques for providing useful text alternatives" bugzilla@wiggum.w3.org
- [Bug 9214] Allow role="presentation" on img bugzilla@wiggum.w3.org
- [Bug 9213] HTML5 Lacks a Way to Programmatically-Determine Missing Text Alternatives bugzilla@wiggum.w3.org
- [Bug 7525] meta/@name=keywords should be specified (and made conforming) bugzilla@wiggum.w3.org
- [Bug 9126] Please make the bug filing dialog ignoreable (e.g. make it a single-line box above or instead of the comment box). Consider moving focus so that pressing enter in an attempt to close the dialog doesn't file a dup bug. bugzilla@wiggum.w3.org
Monday, 22 March 2010
- [Bug 9300] Remove the requirement to close NCR and entities with a semicolon bugzilla@wiggum.w3.org
- [Bug 9300] Remove the requirement to close NCR and entities with a semicolon bugzilla@wiggum.w3.org
- [Bug 9300] Remove the requirement to close NCR and entities with a semicolon bugzilla@wiggum.w3.org
- [Bug 7011] [in off-bug discussion] canvas accessible fallback provision is under specified bugzilla@wiggum.w3.org
- [Bug 9300] Remove the requirement to close NCR and entities with a semicolon bugzilla@wiggum.w3.org
- [Bug 9300] Remove the requirement to close NCR and entities with a semicolon bugzilla@wiggum.w3.org
- [Bug 9300] Remove the requirement to close NCR and entities with a semicolon bugzilla@wiggum.w3.org
- [Bug 9300] New: Remove the requirement to close NCR and entities with a colon bugzilla@wiggum.w3.org
- [Bug 7034] authoring conformance requirements in the spec should either be removed or replaced bugzilla@wiggum.w3.org
- [Bug 7034] authoring conformance requirements in the spec should either be removed or replaced bugzilla@wiggum.w3.org
- [Bug 7362] inclusion of the title as a case where the alt may be omitted is problematic bugzilla@wiggum.w3.org
- [Bug 7633] The use of @summary should be encouraged when circumstances warrant bugzilla@wiggum.w3.org
- [Bug 5758] <audio> and <video> do not have sufficient support for synchronized accessibility content bugzilla@wiggum.w3.org
- [Bug 7011] [in off-bug discussion] canvas accessible fallback provision is under specified bugzilla@wiggum.w3.org
- [Bug 9289] New: What about polyglot documents which are *both* HTML5 and XHTML5 ? I think it would make a lot of sense to spend a few words on that because virtually nobody will use XHMTL5 with the correct MIME-type because of the legacy browsers. bugzilla@wiggum.w3.org
- [Bug 9235] An additional useful transformation would be Perspective. bugzilla@wiggum.w3.org
- [Bug 9287] DOCTYPE "mostly useless" bugzilla@wiggum.w3.org
Sunday, 21 March 2010
- [Bug 9287] DOCTYPE "mostly useless" bugzilla@wiggum.w3.org
- [Bug 7670] Use of prefixes is too complicated for a Web technology bugzilla@wiggum.w3.org
- [Bug 9287] New: DOCTYPE "mostly useless" bugzilla@wiggum.w3.org
- [Bug 7034] authoring conformance requirements in the spec should either be removed or replaced bugzilla@wiggum.w3.org
- [Bug 9235] An additional useful transformation would be Perspective. bugzilla@wiggum.w3.org
Saturday, 20 March 2010
- [Bug 9235] An additional useful transformation would be Perspective. bugzilla@wiggum.w3.org
- [Bug 7034] authoring conformance requirements in the spec should either be removed or replaced bugzilla@wiggum.w3.org
- [Bug 7034] authoring conformance requirements in the spec should either be removed or replaced bugzilla@wiggum.w3.org
- [Bug 9286] New: marginheight and topmargin are missing from the list of obsolete elements bugzilla@wiggum.w3.org
Friday, 19 March 2010
- [Bug 7158] this is a discribing comment bugzilla@wiggum.w3.org
- [Bug 9284] New: Consider giving guidelines for use of different bug resolutions bugzilla@wiggum.w3.org
- [Bug 9283] New: NEEDSINFO is a more appropriate resolution for bugs that are missing info than INVALID bugzilla@wiggum.w3.org
- [Bug 6033] Forms section bugzilla@wiggum.w3.org
- [Bug 6033] Forms section bugzilla@wiggum.w3.org
- [Bug 7034] authoring conformance requirements in the spec should either be removed or replaced bugzilla@wiggum.w3.org
- [Bug 9281] The sentence "When used to include data blocks..." would benefit from clarification: "When used to include non-JavaScript data blocks..." bugzilla@wiggum.w3.org
- [Bug 9281] The sentence "When used to include data blocks..." would benefit from clarification: "When used to include non-JavaScript data blocks..." bugzilla@wiggum.w3.org
- [Bug 9282] The sentence "When used to include data blocks..." would benefit from clarification: "When used to include non-JavaScript data blocks..." bugzilla@wiggum.w3.org
- [Bug 9282] New: The sentence "When used to include data blocks..." would benefit from clarification: "When used to include non-JavaScript data blocks..." bugzilla@wiggum.w3.org
- [Bug 9281] New: The sentence "When used to include data blocks..." would benefit from clarification: "When used to include non-JavaScript data blocks..." bugzilla@wiggum.w3.org
- [Bug 7034] authoring conformance requirements in the spec should either be removed or replaced bugzilla@wiggum.w3.org
- [Bug 9280] Add default button option/attribute for forms bugzilla@wiggum.w3.org
- [Bug 9280] New: Add default button option/attribute for forms bugzilla@wiggum.w3.org
- [Bug 9279] New: Align the English isindex prompt with Firefox and Chrome bugzilla@wiggum.w3.org
- [Bug 7851] Some (perhaps all) scripts with a for="" attribute should be ignored bugzilla@wiggum.w3.org
- [Bug 7851] Some (perhaps all) scripts with a for="" attribute should be ignored bugzilla@wiggum.w3.org
Thursday, 18 March 2010
- [Bug 9264] Provide a way to prevent Content-Language from acting as language fallback bugzilla@wiggum.w3.org
- [Bug 9264] Provide a way to prevent Content-Language from acting as language fallback bugzilla@wiggum.w3.org
- [Bug 9278] New: "...with the same argument, the user agent **may** return the same object as the object returned by the earlier call.": Make this a must. To quote hsivonen, "The Web leaves no edge case unexercised." bugzilla@wiggum.w3.org
- [Bug 9264] Provide a way to prevent Content-Language from acting as language fallback bugzilla@wiggum.w3.org
- [Bug 9268] Why can’t we just reuse the <caption> element and describe its meaning according to context? (i.e., spec gives directions for “caption in table” and “caption in figure” contexts.) Semantically, both fulfill the same purpose. And even if there bugzilla@wiggum.w3.org
- [Bug 7392] Please use some term other than "URL" for Web Addresses bugzilla@wiggum.w3.org
- [Bug 8116] URNs are URIs but not URLs bugzilla@wiggum.w3.org
- [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 bugzilla@wiggum.w3.org
- [Bug 7633] The use of @summary should be encouraged when circumstances warrant bugzilla@wiggum.w3.org
- [Bug 7633] The use of @summary should be encouraged when circumstances warrant bugzilla@wiggum.w3.org
- [Bug 7362] inclusion of the title as a case where the alt may be omitted is problematic bugzilla@wiggum.w3.org
- [Bug 7011] [in off-bug discussion] canvas accessible fallback provision is under specified bugzilla@wiggum.w3.org
- [Bug 5758] <audio> and <video> do not have sufficient support for synchronized accessibility content bugzilla@wiggum.w3.org
- [Bug 5758] <audio> and <video> do not have sufficient support for synchronized accessibility content bugzilla@wiggum.w3.org
- [Bug 7721] Drag and Drop is not keyboard accessible bugzilla@wiggum.w3.org
- [Bug 7633] The use of @summary should be encouraged when circumstances warrant bugzilla@wiggum.w3.org
- [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 bugzilla@wiggum.w3.org
- [Bug 7362] inclusion of the title as a case where the alt may be omitted is problematic bugzilla@wiggum.w3.org
- [Bug 7011] [in off-bug discussion] canvas accessible fallback provision is under specified bugzilla@wiggum.w3.org
- [Bug 5758] <audio> and <video> do not have sufficient support for synchronized accessibility content bugzilla@wiggum.w3.org
- [Bug 7721] Drag and Drop is not keyboard accessible bugzilla@wiggum.w3.org
- [Bug 9272] New: This admonition should probably be marked as “Important” rather than “Note”, because of the consequences confusing the definitions of whitespace could have. bugzilla@wiggum.w3.org
- [Bug 9260] On one extreme, we have parentheses. On the other extreme, we have sidebars. But in the middle ground, we have footnotes. How should footnotes be handled if <aside> is not the right way to do it? bugzilla@wiggum.w3.org
- [Bug 9270] New: I think this specification is a big step backwards. I don't know if it technically qualifies as “tag soup”, but it sure feels like it. Semantically, a <dl> makes more sense, and moreover I think the <dialog> element (removed during current ongoing bugzilla@wiggum.w3.org
- [Bug 9268] New: Why can’t we just reuse the <caption> element and describe its meaning according to context? (i.e., spec gives directions for “caption in table” and “caption in figure” contexts.) Semantically, both fulfill the same purpose. And even if there bugzilla@wiggum.w3.org
- [Bug 9267] New: Allow alternative of simple <h> element that uses ancestors to determine hierarchy. (Or take a lesson from DocBook and reuse the <title> element, allowing its semantic meaning to change depending on the context.) bugzilla@wiggum.w3.org
- [Bug 7444] EUC-JP and ISO-2022-JP also need replacement encodings: CP51932 (or eucJP-ms) and CP50221. bugzilla@wiggum.w3.org
- [Bug 7444] EUC-JP and ISO-2022-JP also need replacement encodings: CP51932 (or eucJP-ms) and CP50221. bugzilla@wiggum.w3.org
- [Bug 7444] EUC-JP and ISO-2022-JP also need replacement encodings: CP51932 (or eucJP-ms) and CP50221. bugzilla@wiggum.w3.org
- [Bug 7444] EUC-JP and ISO-2022-JP also need replacement encodings: CP51932 (or eucJP-ms) and CP50221. bugzilla@wiggum.w3.org
- [Bug 7444] EUC-JP and ISO-2022-JP also need replacement encodings: CP51932 (or eucJP-ms) and CP50221. bugzilla@wiggum.w3.org
- [Bug 7444] EUC-JP and ISO-2022-JP also need replacement encodings: CP51932 (or eucJP-ms) and CP50221. bugzilla@wiggum.w3.org
- [Bug 9264] Provide a way to prevent Content-Language from acting as language fallback bugzilla@wiggum.w3.org
- [Bug 9263] Incorrect language determination algorithm bugzilla@wiggum.w3.org
- [Bug 9264] Provide a way to prevent Content-Language from acting as language fallback bugzilla@wiggum.w3.org
- [Bug 9265] New: Although I’m loving the spec in general, what about a generic <h>header</h> element that can be nested? After all, we are not writing <section1>, <section2>, <section3>, and so on … bugzilla@wiggum.w3.org
- [Bug 9264] New: Provide a way to prevent Content-Language from acting as language fallback bugzilla@wiggum.w3.org
- [Bug 9263] New: Incorrect language determination algorithm bugzilla@wiggum.w3.org
Wednesday, 17 March 2010
- [Bug 9255] why the hell is it uppercase in the longer exemple? bugzilla@wiggum.w3.org
- [Bug 9261] Copying all the attributes would include the "id" attribute. Doesn't this allow multiple duplicate ID attributes? This is what current browsers do, so I guess which element gets selected in this situation by CSS or getElementById should be specified in th bugzilla@wiggum.w3.org
- [Bug 9261] New: Copying all the attributes would include the "id" attribute. Doesn't this allow multiple duplicate ID attributes? This is what current browsers do, so I guess which element gets selected in this situation by CSS or getElementById should be specified in th bugzilla@wiggum.w3.org
- [Bug 9260] New: On one extreme, we have parentheses. On the other extreme, we have sidebars. But in the middle ground, we have footnotes. How should footnotes be handled if <aside> is not the right way to do it? bugzilla@wiggum.w3.org
- [Bug 9259] New: clarification needed: "one big page with a scrollbar would be equivalent" Many readers might think as I did, "equivalent to what?" On reflection, I understand -- to the tabbed interface -- but the language could be clearer. bugzilla@wiggum.w3.org
Tuesday, 16 March 2010
- [Bug 8891] No change or so-called zero edit proposals bugzilla@wiggum.w3.org
- [Bug 8891] No change or so-called zero edit proposals bugzilla@wiggum.w3.org
- [Bug 9255] New: why the hell is it uppercase in the longer exemple? bugzilla@wiggum.w3.org
- [Bug 9151] The first item in the list seems truncated or not in item list form. It ends "and," bugzilla@wiggum.w3.org
- [Bug 6496] Allow <img aria-labelledby> to act as a text alternative bugzilla@wiggum.w3.org
- [Bug 8716] Replace img Guidance for Conformance Checkers with Suggested Text for Short Text Alternatives bugzilla@wiggum.w3.org
- [Bug 9098] Correct the img element definition. Replace with suggested text. bugzilla@wiggum.w3.org
- [Bug 9215] Provide a Webcam example that is in accord with WCAG 2 or Defer to "HTML5: Techniques for providing useful text alternatives" bugzilla@wiggum.w3.org
- [Bug 7851] Some (perhaps all) scripts with a for="" attribute should be ignored bugzilla@wiggum.w3.org
- [Bug 9153] The element list isn't in alphabetical order (unlike the same element list further down). bugzilla@wiggum.w3.org
- [Bug 8646] Private communication exception bugzilla@wiggum.w3.org
- [Bug 9216] Provide a CAPTCHA example that is in accord with WCAG 2 or Defer to "HTML5: Techniques for providing useful text alternatives" bugzilla@wiggum.w3.org
- [Bug 9241] Explicitly state, "For guidance on accessibility requirements for text alternatives authors should consult WCAG 2.0" and link to WCAG 2.0 bugzilla@wiggum.w3.org
- [Bug 9225] lax interpretation of legacy encoding decl allows attackers to change encoding of a page bugzilla@wiggum.w3.org
- [Bug 9213] HTML5 Lacks a Way to Programmatically-Determine Missing Text Alternatives bugzilla@wiggum.w3.org
- [Bug 9249] Step 9.4 s/is are/are/ bugzilla@wiggum.w3.org
- [Bug 9152] The list of elements doesn't include elements like input, select (and probably others) that are includes in MSIE. bugzilla@wiggum.w3.org
- [Bug 9179] <body><section> results in <section> being associated with the <body> element's section. I'd expect <section> to be associated with its own section. bugzilla@wiggum.w3.org
- [Bug 9217] Remove the Paragraph-Section-Heading loophole for not providing a text alternative. bugzilla@wiggum.w3.org
- [Bug 9071] Handling of "[" in between-doctype-public-and-system-identifiers-state may not be ideal bugzilla@wiggum.w3.org
- [Bug 9214] Allow role="presentation" on img bugzilla@wiggum.w3.org
- [Bug 9218] Enable Automatic Validators to Programmatically Determine the Presence or Absence of a Set of Text Alternatives bugzilla@wiggum.w3.org
- [Bug 9212] Change the Generator Mechanism for img from Document Level to Element Level bugzilla@wiggum.w3.org
- [Bug 9177] Can the script element please allow the scope attribute in the same semantic way as the style element? The dom would be limited to only elements under that node. bugzilla@wiggum.w3.org
- [Bug 9180] "The event thus is not to be fired faster than about 66Hz or slower than 4Hz." - unless the event handler is still running, in which case it could be slower bugzilla@wiggum.w3.org
- [Bug 9207] Anything else: This part of the spec is problematic, for example, a query string variable &lang_id=1 in as part of an attribute of say an img tag, will get converted into an character token when it shouldn't be. Why is the set of characters a-z, A-Z, 0- bugzilla@wiggum.w3.org
- [Bug 9233] Incorporate a Link to UAAG with appropriate wording into browser sections bugzilla@wiggum.w3.org
- [Bug 9188] Fix the references in the txt version to have URLs. bugzilla@wiggum.w3.org
- [Bug 7468] make <table border="1" cellpadding="10" cellspacing="0"> conforming bugzilla@wiggum.w3.org
- [Bug 9233] Incorporate a Link to UAAG with appropriate wording into browser sections bugzilla@wiggum.w3.org
- [Bug 7034] authoring conformance requirements in the spec should either be removed or replaced bugzilla@wiggum.w3.org
- [Bug 7851] Some (perhaps all) scripts with a for="" attribute should be ignored bugzilla@wiggum.w3.org
- [Bug 8716] Replace img Guidance for Conformance Checkers with Suggested Text for Short Text Alternatives bugzilla@wiggum.w3.org
- [Bug 8646] Private communication exception bugzilla@wiggum.w3.org
- [Bug 9151] The first item in the list seems truncated or not in item list form. It ends "and," bugzilla@wiggum.w3.org
- [Bug 7034] authoring conformance requirements in the spec should either be removed or replaced bugzilla@wiggum.w3.org
- [Bug 6496] Allow <img aria-labelledby> to act as a text alternative bugzilla@wiggum.w3.org
- [Bug 9153] The element list isn't in alphabetical order (unlike the same element list further down). bugzilla@wiggum.w3.org
- [Bug 9249] Step 9.4 s/is are/are/ bugzilla@wiggum.w3.org
- [Bug 9233] Incorporate a Link to UAAG with appropriate wording into browser sections bugzilla@wiggum.w3.org
- [Bug 9215] Provide a Webcam example that is in accord with WCAG 2 or Defer to "HTML5: Techniques for providing useful text alternatives" bugzilla@wiggum.w3.org
- [Bug 9216] Provide a CAPTCHA example that is in accord with WCAG 2 or Defer to "HTML5: Techniques for providing useful text alternatives" bugzilla@wiggum.w3.org
- [Bug 9152] The list of elements doesn't include elements like input, select (and probably others) that are includes in MSIE. bugzilla@wiggum.w3.org
- [Bug 9225] lax interpretation of legacy encoding decl allows attackers to change encoding of a page bugzilla@wiggum.w3.org
- [Bug 9217] Remove the Paragraph-Section-Heading loophole for not providing a text alternative. bugzilla@wiggum.w3.org
- [Bug 9213] HTML5 Lacks a Way to Programmatically-Determine Missing Text Alternatives bugzilla@wiggum.w3.org
- [Bug 9071] Handling of "[" in between-doctype-public-and-system-identifiers-state may not be ideal bugzilla@wiggum.w3.org
- [Bug 9098] Correct the img element definition. Replace with suggested text. bugzilla@wiggum.w3.org
- [Bug 9218] Enable Automatic Validators to Programmatically Determine the Presence or Absence of a Set of Text Alternatives bugzilla@wiggum.w3.org
- [Bug 9241] Explicitly state, "For guidance on accessibility requirements for text alternatives authors should consult WCAG 2.0" and link to WCAG 2.0 bugzilla@wiggum.w3.org
- [Bug 9212] Change the Generator Mechanism for img from Document Level to Element Level bugzilla@wiggum.w3.org
- [Bug 9188] Fix the references in the txt version to have URLs. bugzilla@wiggum.w3.org
- [Bug 9207] Anything else: This part of the spec is problematic, for example, a query string variable &lang_id=1 in as part of an attribute of say an img tag, will get converted into an character token when it shouldn't be. Why is the set of characters a-z, A-Z, 0- bugzilla@wiggum.w3.org
- [Bug 9214] Allow role="presentation" on img bugzilla@wiggum.w3.org
- [Bug 9177] Can the script element please allow the scope attribute in the same semantic way as the style element? The dom would be limited to only elements under that node. bugzilla@wiggum.w3.org
- [Bug 9179] <body><section> results in <section> being associated with the <body> element's section. I'd expect <section> to be associated with its own section. bugzilla@wiggum.w3.org
- [Bug 9180] "The event thus is not to be fired faster than about 66Hz or slower than 4Hz." - unless the event handler is still running, in which case it could be slower bugzilla@wiggum.w3.org
- [Bug 7525] meta/@name=keywords should be specified (and made conforming) bugzilla@wiggum.w3.org
- [Bug 9253] New: Calling putImageData() should force browsers to render the canvas to screen, otherwise animations won't work. bugzilla@wiggum.w3.org
- [Bug 9207] Anything else: This part of the spec is problematic, for example, a query string variable &lang_id=1 in as part of an attribute of say an img tag, will get converted into an character token when it shouldn't be. Why is the set of characters a-z, A-Z, 0- bugzilla@wiggum.w3.org
- [Bug 8872] split out and modify parts of Section 4.8.2.1 the img element bugzilla@wiggum.w3.org
- [Bug 9239] specify a convention for preventing vendor-specific non-standard extensions from clashing with themselves and future standard development bugzilla@wiggum.w3.org
- [Bug 9239] specify a convention for preventing vendor-specific non-standard extensions from clashing with themselves and future standard development bugzilla@wiggum.w3.org
- [Bug 7034] authoring conformance requirements in the spec should either be removed or replaced bugzilla@wiggum.w3.org
- [Bug 5846] Accessing Object Parameters from an Embedded SVG bugzilla@wiggum.w3.org
Monday, 15 March 2010
- [Bug 5846] Accessing Object Parameters from an Embedded SVG bugzilla@wiggum.w3.org
- [Bug 7034] authoring conformance requirements in the spec should either be removed or replaced bugzilla@wiggum.w3.org
- [Bug 5846] Accessing Object Parameters from an Embedded SVG bugzilla@wiggum.w3.org
- [Bug 9251] "When content fails to load (e.g. due to a network error), then the user agent must queue a task to fire a simple event named error at the element instead." is pretty vague (e.g. do bad URLs fire onerror? cross-domain failures?) Same applies to <frame>. bugzilla@wiggum.w3.org
- [Bug 9251] New: "When content fails to load (e.g. due to a network error), then the user agent must queue a task to fire a simple event named error at the element instead." is pretty vague (e.g. do bad URLs fire onerror? cross-domain failures?) Same applies to <frame>. bugzilla@wiggum.w3.org
- [Bug 9249] New: Step 9.4 s/is are/are/ bugzilla@wiggum.w3.org
- [Bug 5758] <audio> and <video> do not have sufficient support for synchronized accessibility content bugzilla@wiggum.w3.org
- [Bug 5758] <audio> and <video> do not have sufficient support for synchronized accessibility content bugzilla@wiggum.w3.org
- [Bug 7056] <caption> and <figure><legend> elements should allow flow content children bugzilla@wiggum.w3.org
- [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 bugzilla@wiggum.w3.org
- [Bug 7056] <caption> and <figure><legend> elements should allow flow content children bugzilla@wiggum.w3.org
- [Bug 7056] <caption> and <figure><legend> elements should allow flow content children bugzilla@wiggum.w3.org
- [Bug 7056] <caption> and <figure><legend> elements should allow flow content children bugzilla@wiggum.w3.org
- [Bug 7056] <caption> and <figure><legend> elements should allow flow content children bugzilla@wiggum.w3.org
- [Bug 7056] <caption> and <figure><legend> elements should allow flow content children bugzilla@wiggum.w3.org
- [Bug 8716] Replace img Guidance for Conformance Checkers with Suggested Text for Short Text Alternatives bugzilla@wiggum.w3.org
- [Bug 7056] <caption> and <figure><legend> elements should allow flow content children bugzilla@wiggum.w3.org
- [Bug 7056] <caption> and <figure><legend> elements should allow flow content children bugzilla@wiggum.w3.org
- [Bug 7056] <caption> and <figure><legend> elements should allow flow content children bugzilla@wiggum.w3.org
- [Bug 7056] <caption> and <figure><legend> elements should allow flow content children bugzilla@wiggum.w3.org
- [Bug 7076] Client-side image maps attributes missing on the a element bugzilla@wiggum.w3.org
- [Bug 7056] <caption> and <figure><legend> elements should allow flow content children bugzilla@wiggum.w3.org
- [Bug 8611] Consider adding a full schema to H:TML bugzilla@wiggum.w3.org
- [Bug 9247] New: last note states small does not de-emphasize. This naturally leads to the question what does. Answer that question bugzilla@wiggum.w3.org
- [Bug 9246] test est bugzilla@wiggum.w3.org
- [Bug 7546] "HTML 5" Editor's draft misnamed and suboptimal for HTML content authors unless refactored into HTML (main) and DOM API (appendix). bugzilla@wiggum.w3.org
- [Bug 9246] New: test est bugzilla@wiggum.w3.org
- [Bug 7735] perhaps open could be an int rather than boolean, indicating which content area was open to make using this model for tabs easier bugzilla@wiggum.w3.org
- [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) bugzilla@wiggum.w3.org
- [Bug 7471] JimJJewett gmail: Make explicit reasons for *not* exposing aspect ratio/clipping. (Security vs simplification). Deals with http://www.w3.org/AudioVideo/2007/12/SMIL-AudioVideoControlConcepts.html#L2398 note1 bugzilla@wiggum.w3.org
- [Bug 7076] Client-side image maps attributes missing on the a element bugzilla@wiggum.w3.org
- [Bug 7076] Client-side image maps attributes missing on the a element bugzilla@wiggum.w3.org
- [Bug 7468] make <table border="1" cellpadding="10" cellspacing="0"> conforming bugzilla@wiggum.w3.org
- [Bug 7034] authoring conformance requirements in the spec should either be removed or replaced bugzilla@wiggum.w3.org
Sunday, 14 March 2010
- [Bug 7546] "HTML 5" Editor's draft misnamed and suboptimal for HTML content authors unless refactored into HTML (main) and DOM API (appendix). bugzilla@wiggum.w3.org
- [Bug 7468] make <table border="1" cellpadding="10" cellspacing="0"> conforming bugzilla@wiggum.w3.org
- [Bug 7034] authoring conformance requirements in the spec should either be removed or replaced bugzilla@wiggum.w3.org
- [Bug 7034] authoring conformance requirements in the spec should either be removed or replaced bugzilla@wiggum.w3.org
- [Bug 7851] Some (perhaps all) scripts with a for="" attribute should be ignored bugzilla@wiggum.w3.org
- [Bug 8800] Cut/copy/paste should use dedicated events instead of overloading drag and drop bugzilla@wiggum.w3.org
- [Bug 8554] <progress> element should be labelable with a label bugzilla@wiggum.w3.org
- [Bug 7391] Reference to WEBADDRESS should be replaced with reference to IRIbis bugzilla@wiggum.w3.org
- [Bug 8731] Consider expanding buffering control for media elements bugzilla@wiggum.w3.org
- [Bug 7034] authoring conformance requirements in the spec should either be removed or replaced bugzilla@wiggum.w3.org
- [Bug 6763] Inconsistent use of American and British English bugzilla@wiggum.w3.org
- [Bug 7034] authoring conformance requirements in the spec should either be removed or replaced bugzilla@wiggum.w3.org
- [Bug 7150] Why do these examples have uppercase elements? bugzilla@wiggum.w3.org
- [Bug 7386] SharedWorkerGlobalScope bugzilla@wiggum.w3.org
- [Bug 7386] SharedWorkerGlobalScope bugzilla@wiggum.w3.org
- [Bug 7034] authoring conformance requirements in the spec should either be removed or replaced bugzilla@wiggum.w3.org
- [Bug 7386] SharedWorkerGlobalScope bugzilla@wiggum.w3.org
- [Bug 6684] Disregard of RFC 4329 and IANA MIME Media Types bugzilla@wiggum.w3.org
- [Bug 6763] Inconsistent use of American and British English bugzilla@wiggum.w3.org
- [Bug 7386] SharedWorkerGlobalScope bugzilla@wiggum.w3.org
- [Bug 7386] SharedWorkerGlobalScope bugzilla@wiggum.w3.org
- [Bug 7056] <caption> and <figure><legend> elements should allow flow content children bugzilla@wiggum.w3.org
- [Bug 8716] Replace img Guidance for Conformance Checkers with Suggested Text for Short Text Alternatives bugzilla@wiggum.w3.org
- [Bug 7056] <caption> and <figure><legend> elements should allow flow content children bugzilla@wiggum.w3.org
- [Bug 7056] <caption> and <figure><legend> elements should allow flow content children bugzilla@wiggum.w3.org
- [Bug 7633] The use of @summary should be encouraged when circumstances warrant bugzilla@wiggum.w3.org
- [Bug 7633] The use of @summary should be encouraged when circumstances warrant bugzilla@wiggum.w3.org
- [Bug 7633] The use of @summary should be encouraged when circumstances warrant bugzilla@wiggum.w3.org
- [Bug 7056] <caption> and <figure><legend> elements should allow flow content children bugzilla@wiggum.w3.org
- [Bug 7056] <caption> and <figure><legend> elements should allow flow content children bugzilla@wiggum.w3.org
- [Bug 7736] add tooltip attribute & keep title for other uses bugzilla@wiggum.w3.org
- [Bug 7747] Attribute language not allowed on element script at this point bugzilla@wiggum.w3.org
- [Bug 7741] First set of examples of alternative stylesheets have stylesheet titles marked up with href attributes rather than title attributes bugzilla@wiggum.w3.org
- [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. bugzilla@wiggum.w3.org
- [Bug 7748] Does it have to be an absolute path or can it be a relative one, too? bugzilla@wiggum.w3.org
- [Bug 7739] Add ids to author notes to allow direct linking bugzilla@wiggum.w3.org
- [Bug 7735] perhaps open could be an int rather than boolean, indicating which content area was open to make using this model for tabs easier bugzilla@wiggum.w3.org
- [Bug 7745] Shouldn't the spec state that it is the second (or third) versin of XHTML, known as XHTML5 as there haven't been version 3 or 4. bugzilla@wiggum.w3.org
- [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 bugzilla@wiggum.w3.org
- [Bug 7744] Is sniffing required? bugzilla@wiggum.w3.org
- [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 bugzilla@wiggum.w3.org
- [Bug 7727] legacy doc type does not need to be discouraged by "SHOULD NOT" bugzilla@wiggum.w3.org
- [Bug 7740] Authoring advice for canvas is bad for accessibility bugzilla@wiggum.w3.org
- [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 bugzilla@wiggum.w3.org
- [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. bugzilla@wiggum.w3.org
- [Bug 7723] duplicate word ("first first") should be "first five" bugzilla@wiggum.w3.org
- [Bug 7733] Too simplistic to handle used cases with more complex controls than toggle, like carousel, tabs. It could work for accordians. bugzilla@wiggum.w3.org
- [Bug 7721] Drag and Drop is not keyboard accessible bugzilla@wiggum.w3.org
- [Bug 7712] oncontextmenu bugzilla@wiggum.w3.org
- [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?) bugzilla@wiggum.w3.org
- [Bug 7730] The note starting "The algorithm described..." should end with the word "limitations" or "constraints" or something bugzilla@wiggum.w3.org
- [Bug 7710] "Any byte or sequences of bytes [...] that is misinterpreted [...]" - s/sequences/sequence/ bugzilla@wiggum.w3.org
- [Bug 7726] legacy doctype syntax allows <!DOCTYPE HTML SYSTEM"about:legacy-compat"> bugzilla@wiggum.w3.org
- [Bug 7708] Include some documentation here (or link to) how the time element with a pubdate attribute applies to article. bugzilla@wiggum.w3.org
- [Bug 7706] This section should reference "matches a fallback namespace" in step 3. bugzilla@wiggum.w3.org
- [Bug 7704] It is better to implement canvas.clear() method and allow to resize canvas without clearing it bugzilla@wiggum.w3.org
- [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 bugzilla@wiggum.w3.org
- [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 bugzilla@wiggum.w3.org
- [Bug 7699] define reset event bugzilla@wiggum.w3.org
- [Bug 7714] the diagram image says "tokeniser"; should be "tokenizer" bugzilla@wiggum.w3.org
- [Bug 7711] The "strong native semantics" are worded very similarly -- but not quite the same -- for input type=Number, input type=range, and progressbar. bugzilla@wiggum.w3.org
- [Bug 7705] What use of providing both "embed" and "object" elements? They play nearly same role. bugzilla@wiggum.w3.org
- [Bug 7709] Prevent PUT/DELETE cross-origin bugzilla@wiggum.w3.org
- [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 bugzilla@wiggum.w3.org
- [Bug 7694] object@classid is missing from list of Content attributes, even though it is essential bugzilla@wiggum.w3.org
- [Bug 7691] each of which 'has', not 'have' bugzilla@wiggum.w3.org
- [Bug 7680] Add an 'angle' element to HTML5 bugzilla@wiggum.w3.org
- [Bug 7703] HTML document conformance should explicitly depend on foreign content conformance bugzilla@wiggum.w3.org
- [Bug 7688] 'input type=time' forbids legitimate use case bugzilla@wiggum.w3.org
- [Bug 7693] The term "Draft Standard" means something different in IETF than meant here, which adds to the confusion. "Editor's Draft" would be better. bugzilla@wiggum.w3.org
- [Bug 7687] Use "representation" instead of "resource" in �6.9 bugzilla@wiggum.w3.org
- [Bug 7700] define abort event bugzilla@wiggum.w3.org
- [Bug 7682] link tag: rel: associate pages about the same organization across many sites bugzilla@wiggum.w3.org
- [Bug 7696] zxcszxczxc bugzilla@wiggum.w3.org
- [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 bugzilla@wiggum.w3.org
- [Bug 7668] 7.9.6 should explain which events are actually dispatched when copying/cutting/pasting bugzilla@wiggum.w3.org
- [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? bugzilla@wiggum.w3.org
- [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". bugzilla@wiggum.w3.org
- [Bug 7689] Cache-defeating semantics are not defined bugzilla@wiggum.w3.org
- [Bug 7663] search bugzilla@wiggum.w3.org
- [Bug 7661] status bugzilla@wiggum.w3.org
- [Bug 7681] link tag: rel: associate pages about the same person across many sites bugzilla@wiggum.w3.org
- [Bug 7645] associate printable pages and less-convenient-to-print pages with link rel value "print" bugzilla@wiggum.w3.org
- [Bug 7644] The first example for footnotes is actually an example of a dialogue. bugzilla@wiggum.w3.org
- [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. bugzilla@wiggum.w3.org
- [Bug 7659] Clarify what "other applicable specifications" means to say http://lists.w3.org/Archives/Public/www-tag/2009Sep/0045.html bugzilla@wiggum.w3.org
- [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. bugzilla@wiggum.w3.org
- [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 bugzilla@wiggum.w3.org
- [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 bugzilla@wiggum.w3.org
- [Bug 7662] When images are disabled arguably fallback content of the <canvas> element should be shown. bugzilla@wiggum.w3.org
- [Bug 7637] Where is HTMLAnchorElement.name defined? I don't see it here nor in the main interface definition bugzilla@wiggum.w3.org
- [Bug 7652] Is it fine for <nav> to link to a bunch of external pages? E.g. your Flickr/Facebook/Twitter/etc. profiles? bugzilla@wiggum.w3.org
- [Bug 7642] which attribute wins if both pointsize and size are specified? bugzilla@wiggum.w3.org
- [Bug 7646] Media Queries bugzilla@wiggum.w3.org
- [Bug 7639] Please remove "dc" and "ds" from the parser bugzilla@wiggum.w3.org
- [Bug 7658] s/the requisite element/the requested element/ bugzilla@wiggum.w3.org
- [Bug 7633] The use of @summary should be encouraged when circumstances warrant bugzilla@wiggum.w3.org
- [Bug 7623] It'd be really nice if you specified if the angle argument to context.rotate accepts degrees, radians, or what. bugzilla@wiggum.w3.org
- [Bug 7629] When the dd element is used inside figure and details it should probably not have margin by default. bugzilla@wiggum.w3.org
- [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 bugzilla@wiggum.w3.org
- [Bug 7627] Cross-reference more occurrences of "being rendered". bugzilla@wiggum.w3.org
- [Bug 7626] Spec says: "Note: Removing an event handler content attribute does not reset the corresponding event handler attribute.". In fact browsers will remove or "deactivate" the listener when you remove the HTML attribute. Some browsers reset it to null or undef bugzilla@wiggum.w3.org
- [Bug 7608] Rendering–Introduction: s/normaly/normally bugzilla@wiggum.w3.org
- [Bug 7636] shouldn't dom-table-summary be part of the HTMLTableElement interface proper? bugzilla@wiggum.w3.org
- [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. bugzilla@wiggum.w3.org
- [Bug 7621] editorial: add example for pushState() - it's not clear what to use as the data bugzilla@wiggum.w3.org
- [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 bugzilla@wiggum.w3.org
- [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 bugzilla@wiggum.w3.org
- [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? bugzilla@wiggum.w3.org
- [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. bugzilla@wiggum.w3.org
- [Bug 7614] why was this changed again? bugzilla@wiggum.w3.org
- [Bug 7601] refer to pronunciations for TTS PLS with link rel value "pronunciation" bugzilla@wiggum.w3.org
- [Bug 7617] editorial: "reflect" under HTMLDocument should be a link bugzilla@wiggum.w3.org
- [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 bugzilla@wiggum.w3.org
- [Bug 7602] "Note: Playback of any previously " is listed as a step 12 of HTMLMediaElement.load() bugzilla@wiggum.w3.org
- [Bug 7603] If the attributes list is supposed to be sorted alphabetically, @hidden needs to be placed before @id. bugzilla@wiggum.w3.org
- [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 bugzilla@wiggum.w3.org
- [Bug 7595] editorial: "represents" should be a link bugzilla@wiggum.w3.org
- [Bug 7593] Use of the "q.v." abbreviation here, while correct, is fairly obscure. Consider dropping "q.v." or rephrasing. bugzilla@wiggum.w3.org
- [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). bugzilla@wiggum.w3.org
- [Bug 7591] disabled <fieldset> bugzilla@wiggum.w3.org
- [Bug 7585] Link relations should refer to IANA registry (draft-nottingham-http-link-header) bugzilla@wiggum.w3.org
- [Bug 7594] "Otherwise, the the body element is null. Append the new value to the root element.": Append it where? At the end? bugzilla@wiggum.w3.org
- [Bug 7581] Should the select() method set focus? MSIE+Opera does not. FF+Chrome sets focus. It should probably be specified to set focus. bugzilla@wiggum.w3.org
- [Bug 7579] Could "interactive widget" in the context of a web application be defined, expanded upon or an example provided? This seems too vague. bugzilla@wiggum.w3.org
- [Bug 7590] The sentence about HTMLUnknownElement should s/this specification/this specification (or other appliciable specifications)/ to allow delta specs to define HTML elements bugzilla@wiggum.w3.org
- [Bug 7578] "If the defer attribute may be specified": this phrasing is confusing, should "may be specified" be "is specified" bugzilla@wiggum.w3.org
- [Bug 7584] The <meter> example doesn't have any highlighting, whereas all the other elements do bugzilla@wiggum.w3.org
- [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. bugzilla@wiggum.w3.org
- [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 bugzilla@wiggum.w3.org
- [Bug 7561] There's no UA conformance criteria for <meta name>, in particular nothing about case-insensitivity. bugzilla@wiggum.w3.org
- [Bug 7575] <meter> example isn't highlighted bugzilla@wiggum.w3.org
- [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" bugzilla@wiggum.w3.org
- [Bug 7557] add "type" attribute to <nav> to distinguish between primary and secondary navigation bugzilla@wiggum.w3.org
- [Bug 7558] "MIME type" not xreffed in "and any MIME type ending ..." bugzilla@wiggum.w3.org
- [Bug 7556] Where is it defined that only the first <base> element is to be taken into account? Surely that should not be part of iri-bis. bugzilla@wiggum.w3.org
- [Bug 7552] Add <article> examples illustrating how to use the element, without an unnecessary <section> wrapper inside. bugzilla@wiggum.w3.org
- [Bug 7559] What happens when an "option" element has its "selected" attribute removed? bugzilla@wiggum.w3.org
- [Bug 7577] meta/@name=descriptions vs invisible metadata bugzilla@wiggum.w3.org
- [Bug 7547] on .drawImage() negative widths or heights should flip/mirror the image. There's no easy way of fliping images in canvas bugzilla@wiggum.w3.org
- [Bug 7549] define how to parse a MIME type bugzilla@wiggum.w3.org
- [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. bugzilla@wiggum.w3.org
- [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. bugzilla@wiggum.w3.org
- [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 bugzilla@wiggum.w3.org
- [Bug 7548] replace <dialog> with advice bugzilla@wiggum.w3.org
- [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? bugzilla@wiggum.w3.org
- [Bug 7546] "HTML 5" Editor's draft misnamed and suboptimal for HTML content authors unless refactored into HTML (main) and DOM API (appendix). bugzilla@wiggum.w3.org
- [Bug 7523] Treat <metadata> like <title> in SVG foreign content bugzilla@wiggum.w3.org
- [Bug 7525] meta/@name=keywords should be specified (and made conforming) bugzilla@wiggum.w3.org
- [Bug 7540] Spec for metadata extensions does not define which states are allowed/conforming bugzilla@wiggum.w3.org
- [Bug 7522] <math> should also be phrasing and flow content, like <img> and <svg>. bugzilla@wiggum.w3.org
- [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"). bugzilla@wiggum.w3.org
- [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 bugzilla@wiggum.w3.org
- [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. bugzilla@wiggum.w3.org
- [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 bugzilla@wiggum.w3.org
- [Bug 7508] <dialog> needs a way to add non-speech related information bugzilla@wiggum.w3.org
- [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. bugzilla@wiggum.w3.org
- [Bug 7507] Firefox 3.5 does NOT clear a canvas if its width is set to itself bugzilla@wiggum.w3.org
- [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. bugzilla@wiggum.w3.org
- [Bug 7512] suggested "replacement" for head/@profile does not work bugzilla@wiggum.w3.org
- [Bug 7499] <keygen> should not be defined as a requirement for a conforming HTML5 user agent and should be removed from the spec bugzilla@wiggum.w3.org
- [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. bugzilla@wiggum.w3.org
- [Bug 7509] Consider <dl type="dialog"> instead of <dialog> bugzilla@wiggum.w3.org
- [Bug 7493] I want to know meta information on media src. Name of a song, work name, name of singer, and etc... bugzilla@wiggum.w3.org
- [Bug 7505] interface HTMLIFrameElement : HTMLElement { attribute DOMString src; attribute DOMString name; attribute DOMString sandbox; attribute boolean seamless; attribute DOMString width; attribute bugzilla@wiggum.w3.org
- [Bug 7504] Occurrences of the terms "Raw text elements", "RCDATA elements", "Foreign elements" and "Normal elements" in the prose of this section should link to their definitions in the definition list above. bugzilla@wiggum.w3.org
- [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 bugzilla@wiggum.w3.org
- [Bug 7485] obsolete permitted DOCTYPEs link is broken in author view bugzilla@wiggum.w3.org
- [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 bugzilla@wiggum.w3.org
- [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. bugzilla@wiggum.w3.org
- [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". bugzilla@wiggum.w3.org
- [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." bugzilla@wiggum.w3.org
- [Bug 7497] Add an example to <aside> that shows it being used to hold a blogroll. bugzilla@wiggum.w3.org
- [Bug 7479] The content attribute should be all-lowercase: formnovalidate bugzilla@wiggum.w3.org
- [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." bugzilla@wiggum.w3.org
- [Bug 7475] Semantics of rel=first and rel=index breaks specs and implementations bugzilla@wiggum.w3.org
- [Bug 7460] Under "JavaScript": The note containing a "willful violation" doesn't contain the words "willful violation" as promised by section 1.5.2. bugzilla@wiggum.w3.org
- [Bug 7476] typo in the last example of section 4.6.9: "lt;/time>" where "</time>" is intended. -Tantek bugzilla@wiggum.w3.org
- [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 bugzilla@wiggum.w3.org
- [Bug 7484] head/@profile holds a white-space separated list of URIs bugzilla@wiggum.w3.org
- [Bug 7483] The footer element desperately needs to be able to contain sectioning content descendents, most importantly "nav". Under the current specification, I will just end up using div class="footer" so my footers can contain sectioning content. bugzilla@wiggum.w3.org
- [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) bugzilla@wiggum.w3.org
- [Bug 7480] use of keygen should trigger a warning. bugzilla@wiggum.w3.org
- [Bug 7471] JimJJewett gmail: Make explicit reasons for *not* exposing aspect ratio/clipping. (Security vs simplification). Deals with http://www.w3.org/AudioVideo/2007/12/SMIL-AudioVideoControlConcepts.html#L2398 note1 bugzilla@wiggum.w3.org
- [Bug 7472] JimJJewett gmail: Annotations for assistive technology products (ARIA) -- add the "ARIA", like 3.4 mentions XPATH and XSLT bugzilla@wiggum.w3.org
- [Bug 7454] Please do not remove these useful features - or are alternative mechanisms planned? bugzilla@wiggum.w3.org
- [Bug 7469] Is it really necessary to have sections on what HTML5 does not cover? bugzilla@wiggum.w3.org
- [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. bugzilla@wiggum.w3.org
- [Bug 7461] List of space characters should include U+000B LINE TABULATION (VT) or should note why it is not included. bugzilla@wiggum.w3.org
- [Bug 7474] Shouldn't the listener be added AFTER the function is defined? bugzilla@wiggum.w3.org
- [Bug 7459] Nitpicking: an XML document is always well-formed and therefore cannot have syntax errors (including minor). bugzilla@wiggum.w3.org
- [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. bugzilla@wiggum.w3.org
- [Bug 7458] inconsistent definition of "up" relation bugzilla@wiggum.w3.org
- [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. bugzilla@wiggum.w3.org
- [Bug 7465] "a IDL attribute" -> "an IDL attribute" (here and elsewhere) bugzilla@wiggum.w3.org
- [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. bugzilla@wiggum.w3.org
- [Bug 7455] The example codes don't have double quotes bugzilla@wiggum.w3.org
- [Bug 7468] make <table border="1" cellpadding="10" cellspacing="0"> conforming bugzilla@wiggum.w3.org
- [Bug 7452] "The collection of Documents is the browsing context's session history. " -- What do you mean by "the collection of documents" ? not clear bugzilla@wiggum.w3.org
- [Bug 7444] EUC-JP and ISO-2022-JP also need replacement encodings: CP51932 (or eucJP-ms) and CP50221. bugzilla@wiggum.w3.org
- [Bug 7449] editorial: hyperlinked "represents" on the id attribute definition bugzilla@wiggum.w3.org
- [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 bugzilla@wiggum.w3.org
- [Bug 7451] "In the example above" should be "In the example below" bugzilla@wiggum.w3.org
- [Bug 7446] editorial: last paragraph should probably have class=impl bugzilla@wiggum.w3.org
- [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. bugzilla@wiggum.w3.org
- [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 bugzilla@wiggum.w3.org
- [Bug 7440] The markup of the example does not use <th> for Legs and Tails like the actual table does. bugzilla@wiggum.w3.org
- [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. bugzilla@wiggum.w3.org
- [Bug 7439] Where it says "in the example above" when introducing attributes the example is actually below. bugzilla@wiggum.w3.org
- [Bug 7443] maybe list role and aria-* here bugzilla@wiggum.w3.org
- [Bug 7442] Java applets are never conforming, and sometimes don't work bugzilla@wiggum.w3.org
- [Bug 7435] Fichier XML de mise à jour mal formé (200) bugzilla@wiggum.w3.org
- [Bug 7437] The link for "mutable" points to textareas - no mention made of radio, button, input, password types bugzilla@wiggum.w3.org
- [Bug 7436] Fichier XML de mise à jour mal formé (200) bugzilla@wiggum.w3.org
- [Bug 7448] editorial: The ":" in "Author requirements:" should also be marked as class=impl bugzilla@wiggum.w3.org
- [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. bugzilla@wiggum.w3.org
- [Bug 7433] maybe tiny typo in example with figure: the last <figure> should be </figure> ? bugzilla@wiggum.w3.org
- [Bug 7417] Why use radians as opposed to degrees? Does this mean I can never draw a complete circle because I don't have enough bits to represent 2pi? bugzilla@wiggum.w3.org
- [Bug 7438] refine Status section to clarify difference between editor's bug list and the working-group issue list bugzilla@wiggum.w3.org
- [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". bugzilla@wiggum.w3.org
- [Bug 7425] comments hould be after the root node bugzilla@wiggum.w3.org
- [Bug 7423] why deprecate s, u, strike, acronym? It makes no sense. bugzilla@wiggum.w3.org
- [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. bugzilla@wiggum.w3.org
- [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. bugzilla@wiggum.w3.org
- [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" bugzilla@wiggum.w3.org
- [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. bugzilla@wiggum.w3.org
- [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(). bugzilla@wiggum.w3.org
- [Bug 7421] azsxdcfvghjk bugzilla@wiggum.w3.org
- [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." bugzilla@wiggum.w3.org
- [Bug 7420] dfghjxdcfvbnm,,k sdfghjk gfdsdfgh fghj bugzilla@wiggum.w3.org
- [Bug 7422] Add definition of <a name> bugzilla@wiggum.w3.org
- [Bug 7414] Please add a history section bugzilla@wiggum.w3.org
- [Bug 7411] :invalid and :out-of-range shouldn't match until the user has consciously interacted with the form. Roughly, after the input fires a change event. If, say, <input required> matches :invalid immediately on pageload, it becomes basically useless. bugzilla@wiggum.w3.org
- [Bug 7406] Layout system for HTML bugzilla@wiggum.w3.org
- [Bug 7400] "as part" instead of "sa part" bugzilla@wiggum.w3.org
- [Bug 7416] IDNA has not been previously used or defined. It is not an obvious term. Please expand it or reference a definition on first use. bugzilla@wiggum.w3.org
- [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? bugzilla@wiggum.w3.org
- [Bug 7408] "This sample how the getItems() method" is missing a "shows". bugzilla@wiggum.w3.org
- [Bug 7412] Add definition of <meta scheme> bugzilla@wiggum.w3.org
- [Bug 7397] in xref names, s|td/th|tdth|g in obsolete section bugzilla@wiggum.w3.org
- [Bug 7405] Looks good! bugzilla@wiggum.w3.org
- [Bug 7409] It's not clear what labeled control is in cases with > 1 control as a child of the <label> bugzilla@wiggum.w3.org
- [Bug 7404] "but only if the element is being rendered" needs to take into account <canvas> descendants if we're making them focusable bugzilla@wiggum.w3.org
- [Bug 7413] Add definition of <html profile> bugzilla@wiggum.w3.org
- [Bug 7395] "value associated with that denominator punctuation character" didn't get xrefed bugzilla@wiggum.w3.org
- [Bug 7396] shouldn't it be "if the defer attribute is specified, the src attribute must also be specified bugzilla@wiggum.w3.org
- [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 bugzilla@wiggum.w3.org
- [Bug 7398] the-basic-syntax bugzilla@wiggum.w3.org
- [Bug 7393] парпрп bugzilla@wiggum.w3.org
- [Bug 7383] drawImage(video) and createPattern(video) should say that the aspect-ratio-corrected dimensions must be used bugzilla@wiggum.w3.org
- [Bug 7391] Reference to WEBADDRESS should be replaced with reference to IRIbis bugzilla@wiggum.w3.org
- [Bug 7402] The x and y arguments should be better explained. bugzilla@wiggum.w3.org
- [Bug 7386] SharedWorkerGlobalScope bugzilla@wiggum.w3.org
- [Bug 7401] Looking For this bugzilla@wiggum.w3.org
- [Bug 7384] editorial: " (either an HTMLImageElement or an HTMLCanvasElement)" is missing HTMLVideoElement bugzilla@wiggum.w3.org
- [Bug 7379] HTML5 should reference SVG1.1 as well as SVG1.2T bugzilla@wiggum.w3.org
- [Bug 7382] U+000D CARRIAGE RETURN in escaping text spans bugzilla@wiggum.w3.org
- [Bug 7377] s/Dahltröm/Dahlström/ bugzilla@wiggum.w3.org
- [Bug 7381] Clarify default encoding wording and add some examples for non-latin locales. bugzilla@wiggum.w3.org
- [Bug 7392] Please use some term other than "URL" for Web Addresses bugzilla@wiggum.w3.org
- [Bug 7378] element name case fixup table is missing two SVG1.2T entries bugzilla@wiggum.w3.org
- [Bug 7387] small element should have same content model as a, ins, del bugzilla@wiggum.w3.org
- [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. bugzilla@wiggum.w3.org
- [Bug 7373] Need to fix "If a Document or image was returned by the XMLHttpRequest API" now that the document pointer concept is gone. bugzilla@wiggum.w3.org
- [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? bugzilla@wiggum.w3.org
- [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. bugzilla@wiggum.w3.org
- [Bug 7375] Incorrect specification for window.postMessage()'s handling of unentangled ports bugzilla@wiggum.w3.org
- [Bug 7374] legend as child of details, figure is unstylable and thus unusable bugzilla@wiggum.w3.org
- [Bug 7362] inclusion of the title as a case where the alt may be omitted is problematic bugzilla@wiggum.w3.org
- [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.). bugzilla@wiggum.w3.org
- [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. bugzilla@wiggum.w3.org
- [Bug 7348] add examples for <menu type=context> and contextmenu= bugzilla@wiggum.w3.org
- [Bug 7349] add examples here bugzilla@wiggum.w3.org
- [Bug 7367] The HTMLEmbedElement interface needs to have the name and align DOM attributes as well. Web browsers do too. bugzilla@wiggum.w3.org
- [Bug 7346] add examples here bugzilla@wiggum.w3.org
- [Bug 7345] add examples here bugzilla@wiggum.w3.org
- [Bug 7344] add examples here bugzilla@wiggum.w3.org
- [Bug 7347] add examples for <command> bugzilla@wiggum.w3.org
- [Bug 7342] add examples here bugzilla@wiggum.w3.org
- [Bug 7339] add examples here bugzilla@wiggum.w3.org
- [Bug 7340] add examples here bugzilla@wiggum.w3.org
- [Bug 7343] add examples here bugzilla@wiggum.w3.org
- [Bug 7338] add examples here bugzilla@wiggum.w3.org
- [Bug 7336] add examples here bugzilla@wiggum.w3.org
- [Bug 7334] add examples here bugzilla@wiggum.w3.org
- [Bug 7333] add examples here bugzilla@wiggum.w3.org
- [Bug 7341] add examples here bugzilla@wiggum.w3.org
- [Bug 7331] add examples here bugzilla@wiggum.w3.org
- [Bug 7332] add examples here bugzilla@wiggum.w3.org
- [Bug 7328] add examples here bugzilla@wiggum.w3.org
- [Bug 7326] add examples here bugzilla@wiggum.w3.org
- [Bug 7329] add examples here bugzilla@wiggum.w3.org
- [Bug 7337] add examples here bugzilla@wiggum.w3.org
- [Bug 7330] add examples here bugzilla@wiggum.w3.org
- [Bug 7335] add examples here bugzilla@wiggum.w3.org
- [Bug 7324] add examples here bugzilla@wiggum.w3.org
- [Bug 7322] add examples here bugzilla@wiggum.w3.org
- [Bug 7320] add examples here bugzilla@wiggum.w3.org
- [Bug 7323] add examples here bugzilla@wiggum.w3.org
- [Bug 7327] add examples here bugzilla@wiggum.w3.org
- [Bug 7318] add examples here bugzilla@wiggum.w3.org
- [Bug 7316] add examples here bugzilla@wiggum.w3.org
- [Bug 7317] add examples here bugzilla@wiggum.w3.org
- [Bug 7325] add examples here bugzilla@wiggum.w3.org
- [Bug 7312] add examples for tables bugzilla@wiggum.w3.org
- [Bug 7321] add examples here bugzilla@wiggum.w3.org
- [Bug 7310] add examples here bugzilla@wiggum.w3.org
- [Bug 7314] add examples here bugzilla@wiggum.w3.org
- [Bug 7319] add examples here bugzilla@wiggum.w3.org
- [Bug 7306] add examples here bugzilla@wiggum.w3.org
- [Bug 7315] add examples here bugzilla@wiggum.w3.org
- [Bug 7307] add examples here bugzilla@wiggum.w3.org
- [Bug 7311] add examples here bugzilla@wiggum.w3.org
- [Bug 7308] add examples here bugzilla@wiggum.w3.org
- [Bug 7304] add examples here bugzilla@wiggum.w3.org
- [Bug 7302] add examples here bugzilla@wiggum.w3.org
- [Bug 7313] add examples here bugzilla@wiggum.w3.org
- [Bug 7295] add examples here bugzilla@wiggum.w3.org
- [Bug 7300] add examples here bugzilla@wiggum.w3.org
- [Bug 7309] add examples here bugzilla@wiggum.w3.org
- [Bug 7298] add examples here bugzilla@wiggum.w3.org
- [Bug 7296] add examples here bugzilla@wiggum.w3.org
- [Bug 7294] add examples here bugzilla@wiggum.w3.org
- [Bug 7305] add examples here bugzilla@wiggum.w3.org
- [Bug 7293] add examples here bugzilla@wiggum.w3.org
- [Bug 7301] add examples here bugzilla@wiggum.w3.org
- [Bug 7303] add examples here bugzilla@wiggum.w3.org
- [Bug 7292] add examples here bugzilla@wiggum.w3.org
- [Bug 7290] add examples here bugzilla@wiggum.w3.org
- [Bug 7299] mark up examples bugzilla@wiggum.w3.org
- [Bug 7291] add examples here bugzilla@wiggum.w3.org
- [Bug 7297] add examples here bugzilla@wiggum.w3.org
- [Bug 7288] add examples here bugzilla@wiggum.w3.org
- [Bug 7281] <script language="javascript" type="text/javascript"> bugzilla@wiggum.w3.org
- [Bug 7286] add examples here bugzilla@wiggum.w3.org
- [Bug 7282] add dummy willValidate() and company to object bugzilla@wiggum.w3.org
- [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 bugzilla@wiggum.w3.org
- [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 bugzilla@wiggum.w3.org
- [Bug 7289] add examples here bugzilla@wiggum.w3.org
- [Bug 7280] new comment bugzilla@wiggum.w3.org
- [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 № bugzilla@wiggum.w3.org
- [Bug 7287] add examples here bugzilla@wiggum.w3.org
- [Bug 7285] add examples here bugzilla@wiggum.w3.org
- [Bug 7284] add examples here bugzilla@wiggum.w3.org
- [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 bugzilla@wiggum.w3.org
- [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 bugzilla@wiggum.w3.org
- [Bug 7283] add examples here bugzilla@wiggum.w3.org
- [Bug 7265] the HTML5 validator says maxlength is not allowed on textarea bugzilla@wiggum.w3.org
- [Bug 7268] contradicts 4.7.1 wrt implied paragraph boundaries (should not in 4.7.1, not good practice in 4.7.4). dont repeat example or simplify bugzilla@wiggum.w3.org
- [Bug 7266] Section states twice in green that other specs can define other event loops, can remove one of those bugzilla@wiggum.w3.org
- [Bug 7261] In the third code example, a code element is opened but a </cite> tag closes it. The opening tag should be <cite>. bugzilla@wiggum.w3.org
- [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 bugzilla@wiggum.w3.org
- [Bug 7276] "tree order" -- is this a section that can assume formal compsci training, or should a short (4 nodes?) example be given? JimJJewett@gmail bugzilla@wiggum.w3.org
- [Bug 7264] make <% start a bogus comment bugzilla@wiggum.w3.org
- [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.. bugzilla@wiggum.w3.org
- [Bug 7256] "which is not a real time zone currently" --> which is not currently a real time zone bugzilla@wiggum.w3.org
- [Bug 7259] dfgsgdfsg dgf bugzilla@wiggum.w3.org
- [Bug 7272] The explanatory text and the diagram suggest that legs and tails should be th, rather than td -- but the example has td. JimJJewett@gmail bugzilla@wiggum.w3.org
- [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. bugzilla@wiggum.w3.org
- [Bug 7255] "This will either return a year and month" --> "This will return either a year and month" bugzilla@wiggum.w3.org
- [Bug 7246] Add examples for <keygen> bugzilla@wiggum.w3.org
- [Bug 7245] canvas bugzilla@wiggum.w3.org
- [Bug 7248] sxdfsdf bugzilla@wiggum.w3.org
- [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. bugzilla@wiggum.w3.org
- [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? bugzilla@wiggum.w3.org
- [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. bugzilla@wiggum.w3.org
- [Bug 7237] Let current outlinee be null. (It holds the element whose outline is being created.) Spelling. Outline with one "e" bugzilla@wiggum.w3.org
- [Bug 7232] add <iframe> to list of CDATA elements in the "Writing HTML documents" section bugzilla@wiggum.w3.org
- [Bug 7238] more examples bugzilla@wiggum.w3.org
- [Bug 7227] using both "conforming but obsolete" (12.1) and "obsolete but conforming" (12.1.1) - consistency in terminology may be helpful bugzilla@wiggum.w3.org
- [Bug 7225] http://www.w3.org/Bugs/Public/show_bug.cgi?id=7224 bugzilla@wiggum.w3.org
- [Bug 7222] http://abu---wisam.ahlamontada.net bugzilla@wiggum.w3.org
- [Bug 7243] no mension of h3c? bugzilla@wiggum.w3.org
- [Bug 7221] www.abu---wisam.ahlamontada.net bugzilla@wiggum.w3.org
- [Bug 7234] review 123 bugzilla@wiggum.w3.org
- [Bug 7215] character encodings and XML bugzilla@wiggum.w3.org
- [Bug 7226] has enabled --> have enabled bugzilla@wiggum.w3.org
- [Bug 7229] input.files should return the same object bugzilla@wiggum.w3.org
- [Bug 7213] todataurl bugzilla@wiggum.w3.org
- [Bug 7199] microformat bugzilla@wiggum.w3.org
- [Bug 7224] Crash in application C++ exception Unsupported file format header 46466c17 bugzilla@wiggum.w3.org
- [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. bugzilla@wiggum.w3.org
- [Bug 7185] itemprop needs to be after item; no longer a-z ordered due to the name change prolly. bugzilla@wiggum.w3.org
- [Bug 7219] http://abu---wisam.ahlamontada.net bugzilla@wiggum.w3.org
- [Bug 7189] how to use "item" in xhtml5? item="item" ?! bugzilla@wiggum.w3.org
- [Bug 7211] define "positive integer" and use it consistently, instead of "non-negative integer greater than zero" bugzilla@wiggum.w3.org
- [Bug 7220] http://abu---wisam.ahlamontada.net bugzilla@wiggum.w3.org
- [Bug 7183] Hum, ham eu acho que... sei, bom, acho que é isso mesmo, meu comentario é: ronaldo! bugzilla@wiggum.w3.org
- [Bug 7214] Typo: "When an input element's type attribute is in the *Telphone* state" bugzilla@wiggum.w3.org
- [Bug 7186] oppo n iuniu in niun iun lin in liunniuniuniun i bugzilla@wiggum.w3.org
- [Bug 7176] The link to [GREGORIAN] doesn't seem to work... bugzilla@wiggum.w3.org
- [Bug 7171] Is this missing a comment as to how the type attribute is quoted wrt:codecs? "''" + '""' bugzilla@wiggum.w3.org
- [Bug 7158] this is a discribing comment bugzilla@wiggum.w3.org
- [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. bugzilla@wiggum.w3.org
- [Bug 7188] how to use "item" in xhtml5? item="item" ?! bugzilla@wiggum.w3.org
- [Bug 7157] I would like to see theora/vorbis as HTML5 standard. I'm tired of codec patents. bugzilla@wiggum.w3.org
- [Bug 7179] <xmp> should close <p> (does in IE and WebKit) bugzilla@wiggum.w3.org
- [Bug 7145] Valid date strings should accept ambiguous inputs, like "2009" or "2007-01". bugzilla@wiggum.w3.org
- [Bug 7156] I would like to see theora/vorbis as HTML5 standard. I'm tired of codec patents. bugzilla@wiggum.w3.org
- [Bug 7175] clearTimeout and clearInterval are not in the dom-intro box bugzilla@wiggum.w3.org
- [Bug 7151] s/users/user bugzilla@wiggum.w3.org
- [Bug 7164] teste bugzilla@wiggum.w3.org
- [Bug 7147] s#one of the optional U+002F SOLIDUS (/) characters#the optional U+002F SOLIDUS (/) character# bugzilla@wiggum.w3.org
- [Bug 7161] If a heading has title text and then an image below it, then more text, how is the figure element handled in header and hgroup elements? bugzilla@wiggum.w3.org
- [Bug 7142] Shouldn't SERIALISE_ERR be SERIALIZE_ERR ? bugzilla@wiggum.w3.org
- [Bug 7139] test bugzilla@wiggum.w3.org
- [Bug 7137] Need to fill in the references section. bugzilla@wiggum.w3.org
- [Bug 7153] Want standardization of .naturalWidth and .naturalHeight, which some browsers already have bugzilla@wiggum.w3.org
- [Bug 7141] Typo: "A members..." bugzilla@wiggum.w3.org
- [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 :) bugzilla@wiggum.w3.org
- [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. bugzilla@wiggum.w3.org
- [Bug 7150] Why do these examples have uppercase elements? bugzilla@wiggum.w3.org
- [Bug 7146] goog bugzilla@wiggum.w3.org
- [Bug 7105] Default fallback behaviour for unsupported tags in browsers! bugzilla@wiggum.w3.org
- [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 bugzilla@wiggum.w3.org
- [Bug 7140] test bugzilla@wiggum.w3.org
- [Bug 7089] CDATA escapes need to close upon --\s*!> bugzilla@wiggum.w3.org
- [Bug 7084] <ul><li>A<ul></li>B is parsed backwards-incompatibly bugzilla@wiggum.w3.org
- [Bug 7062] replace terms "CDATA element" and "RCDATA element" with... something better bugzilla@wiggum.w3.org
- [Bug 7138] Need to get window.mediaMode into another spec bugzilla@wiggum.w3.org
- [Bug 7079] Inconsistency in algorithm descriptions for parsing integers bugzilla@wiggum.w3.org
- [Bug 7133] minor microdata example typo bugzilla@wiggum.w3.org
- [Bug 7061] clarify definition of "sectioning content" bugzilla@wiggum.w3.org
- [Bug 7086] <a> should be </a> in section 4.5.3 of the HTML5 specification bugzilla@wiggum.w3.org
- [Bug 7103] Content-Language marked as non-conforming bugzilla@wiggum.w3.org
- [Bug 7035] clarify what the use case is for first illustration under "3.4 Content models" bugzilla@wiggum.w3.org
- [Bug 7075] The embed element should be deprecated bugzilla@wiggum.w3.org
- [Bug 7080] Grammatical error in DOM trees section bugzilla@wiggum.w3.org
- [Bug 7030] Define "Text" content model bugzilla@wiggum.w3.org
- [Bug 7034] authoring conformance requirements in the spec should either be removed or replaced bugzilla@wiggum.w3.org
- [Bug 7032] Sandboxing and Referer bugzilla@wiggum.w3.org
- [Bug 7056] <caption> and <figure><legend> elements should allow flow content children bugzilla@wiggum.w3.org
- [Bug 7076] Client-side image maps attributes missing on the a element bugzilla@wiggum.w3.org
- [Bug 7003] Typos bugzilla@wiggum.w3.org
- [Bug 7059] Forking XPath bugzilla@wiggum.w3.org
- [Bug 7051] add new extended attribute to IDLs with DOM attributes that reflect content attributes bugzilla@wiggum.w3.org
- [Bug 6977] Unnecessary sentence in <cite> presentation bugzilla@wiggum.w3.org
- [Bug 6978] Mark eof-terminated script elements as malformed bugzilla@wiggum.w3.org
- [Bug 7011] [in off-bug discussion] canvas accessible fallback provision is under specified bugzilla@wiggum.w3.org
- [Bug 6976] Image Map Example fails Validation bugzilla@wiggum.w3.org
- [Bug 6993] Tell authoring tools to use UTF-8 bugzilla@wiggum.w3.org
- [Bug 6973] Support <textarea>.textLength bugzilla@wiggum.w3.org
- [Bug 6937] BibTeX author and editor don't fit DRY HTML bugzilla@wiggum.w3.org
- [Bug 6949] Don't use colon shorthand when talking about language-related attributes bugzilla@wiggum.w3.org
- [Bug 6992] Title of Web IDL misspelled as WebIDL bugzilla@wiggum.w3.org
- [Bug 6999] Adding tag <NSFW> bugzilla@wiggum.w3.org
- [Bug 6898] Case shifting terminology is confusing bugzilla@wiggum.w3.org
- [Bug 6858] More details needed for "ASCII-compatible encoding" bugzilla@wiggum.w3.org
- [Bug 6974] Please be explicit about inheritance of scripting flag when setting innerHTML bugzilla@wiggum.w3.org
- [Bug 6842] make it possible/easy to link to tables documenting <input> element keywords/states and attributes/methods bugzilla@wiggum.w3.org
- [Bug 6953] clearly specify that misnested tags are an authoring-conformance error bugzilla@wiggum.w3.org
- [Bug 6835] The multiple attribute on datagrid bugzilla@wiggum.w3.org
- [Bug 6942] Define how to handle failed 'resolve a url' steps in microdata algorithms bugzilla@wiggum.w3.org
- [Bug 6902] Note incompatibilities with RDF serializations bugzilla@wiggum.w3.org
- [Bug 6894] add statement that the "checked" attribute on <input> is a boolean attribute bugzilla@wiggum.w3.org
- [Bug 6834] add more number bases to form inputs? bugzilla@wiggum.w3.org
- [Bug 6854] if attribute values enumerated, allow case-sensitivity for meta content values bugzilla@wiggum.w3.org
- [Bug 6853] restore meta keywords, search engines use them bugzilla@wiggum.w3.org
- [Bug 6832] <datagrid> content model is silly bugzilla@wiggum.w3.org
- [Bug 6812] Typo: JavsScript bugzilla@wiggum.w3.org
- [Bug 5758] insufficient accessibility fallback for <audio> or <video> bugzilla@wiggum.w3.org
- [Bug 5758] insufficient accessibility fallback for <audio> or <video> bugzilla@wiggum.w3.org
- [Bug 6790] object element with usemap attribute should be in "Interactive content" category bugzilla@wiggum.w3.org
- [Bug 6796] <keygen> in <select> bugzilla@wiggum.w3.org
- [Bug 6778] Note the XPath implications of assigning HTML elements into the http://www.w3.org/1999/xhtml namespace bugzilla@wiggum.w3.org
- [Bug 6784] WebStorage should include Window IDL for Storage APIs bugzilla@wiggum.w3.org
- [Bug 6774] <mark> element: restrict insertion by other servers bugzilla@wiggum.w3.org
- [Bug 6776] Note the XSLT implications of assigning HTML elements into the http://www.w3.org/1999/xhtml namespace bugzilla@wiggum.w3.org
- [Bug 6779] Clarify the difference between elements and tags bugzilla@wiggum.w3.org
- [Bug 6771] Sectioning Content Use versus DIV bugzilla@wiggum.w3.org
- [Bug 6770] Term emphasis inconsistencies in Terminology section bugzilla@wiggum.w3.org
- [Bug 6769] Grammar mistake: "element element"? bugzilla@wiggum.w3.org
- [Bug 6768] 4.8.10.3 Media types -- unclear note bugzilla@wiggum.w3.org
- [Bug 6767] <time> warning regarding Gregorian calendar bugzilla@wiggum.w3.org
- [Bug 6766] document.all definition missing bugzilla@wiggum.w3.org
- [Bug 6765] Poor wording in 4.8.2.1.12 General guidelines bugzilla@wiggum.w3.org
- [Bug 6764] Section 2.4.4.1 Non-negative integers - Step 9.4 refers to incorrect step bugzilla@wiggum.w3.org
- [Bug 6763] Inconsistent use of American and British English bugzilla@wiggum.w3.org
- [Bug 6762] Typos and spelling mistakes bugzilla@wiggum.w3.org
- [Bug 6760] "string" misspelled as "stirng" bugzilla@wiggum.w3.org
- [Bug 6759] event queueing rules for <img> are nonsensical bugzilla@wiggum.w3.org
- [Bug 6746] case-insensitivity of other than a-z and A-Z, e.g., diacritics bugzilla@wiggum.w3.org
- [Bug 6742] pre-encoded form values should be restorable as submitted bugzilla@wiggum.w3.org
- [Bug 6736] dfn.js doesn't handle class="impl" bugzilla@wiggum.w3.org
- [Bug 6670] Allow unescaped &s, at least in attributes that accept URLs bugzilla@wiggum.w3.org
- [Bug 6729] Attribute getters/setters should lower case argument on HTML elements in HTML docs bugzilla@wiggum.w3.org
- [Bug 6656] make clear that Referer headers track the pushState()d URL bugzilla@wiggum.w3.org
- [Bug 6662] Make clearer that "the script's encoding" doesn't refer to the encoding of the script file itself bugzilla@wiggum.w3.org
- [Bug 6689] [blocked on web dom core] Element.setAttributeNode() shouldn't modify the attribute node bugzilla@wiggum.w3.org
- [Bug 6690] Document.renameNode() is not part of Web DOM bugzilla@wiggum.w3.org
- [Bug 6659] textarea also needs text-indent:initial bugzilla@wiggum.w3.org
- [Bug 6614] Restricting multiple character encoding declarations per document bugzilla@wiggum.w3.org
- [Bug 6684] Disregard of RFC 4329 and IANA MIME Media Types bugzilla@wiggum.w3.org
- [Bug 6628] WebSocket.URL and EventSource.URL should return the absolute URL bugzilla@wiggum.w3.org
- [Bug 6630] Optionalness of start tags when element is empty bugzilla@wiggum.w3.org
- [Bug 6652] spellcheck should allow empty string bugzilla@wiggum.w3.org
- [Bug 6618] </body> and </html> early on handled in a Gecko/WebKit/Presto-inconsisten way bugzilla@wiggum.w3.org
- [Bug 6613] Allow <meta charset="UTF-8"/> in XHTML bugzilla@wiggum.w3.org
- [Bug 6610] add a preventable forced-fragment method bugzilla@wiggum.w3.org
- [Bug 6609] negative keywords-not meta tags bugzilla@wiggum.w3.org
- [Bug 6606] generic 3rd-party <mark>, Smart Tags, and Accelerators prevention bugzilla@wiggum.w3.org
- [Bug 6608] please undeprecate <center> for older browsers bugzilla@wiggum.w3.org
- [Bug 6590] character encoding mapping needs to be used for form submission too bugzilla@wiggum.w3.org
- [Bug 6563] Specify if innerHTML setting should use the quirkiness of the document bugzilla@wiggum.w3.org
- [Bug 6543] Mint a new element for figure captions bugzilla@wiggum.w3.org
- [Bug 6529] value DOM attribute for input element in File Upload state bugzilla@wiggum.w3.org
- [Bug 6536] Time element examples should be in the context of a goal-oriented microformat use case bugzilla@wiggum.w3.org
- [Bug 6516] obsolete attributes on HTMLDocument assume there is a body element bugzilla@wiggum.w3.org
- [Bug 6515] the body element event handler attributes and missing Window object bugzilla@wiggum.w3.org
- [Bug 6493] Use encoding of POSTing document for POST response if meta prescan fails bugzilla@wiggum.w3.org
- [Bug 6491] <textarea wrap=off> not supported bugzilla@wiggum.w3.org
- [Bug 6476] cross-origin media element loads and progress events bugzilla@wiggum.w3.org
- [Bug 6461] Fix the definition of "Origin" for Documents from javascript: URLs bugzilla@wiggum.w3.org
- [Bug 6460] Handle onerror feedback for Workers bugzilla@wiggum.w3.org
- [Bug 6457] registerContentHandler() and sniffing bugzilla@wiggum.w3.org
- [Bug 6440] To which elements applies the formatBlock command? bugzilla@wiggum.w3.org
- [Bug 6438] Error in step 9.4 of the internal algorithm for scanning and assigning header cells bugzilla@wiggum.w3.org
- [Bug 6437] document.location should update when the browsing context is navigated without the Document changing bugzilla@wiggum.w3.org
- [Bug 6434] plugins inside fallback content shouldn't be instantiated bugzilla@wiggum.w3.org
- [Bug 6423] Names of confidence flag states inconsistent bugzilla@wiggum.w3.org
- [Bug 6390] Add a note about reaching after head state and the fragment mode bugzilla@wiggum.w3.org
- [Bug 6351] Add event handler attributes for all events defined in HTML5 bugzilla@wiggum.w3.org
- [Bug 6356] 00:99:00 is a valid time string bugzilla@wiggum.w3.org
- [Bug 6389] Avoid double parse error on EOF in DOCTYPE state bugzilla@wiggum.w3.org
- [Bug 6370] Float exponent part unclear about length of sequence bugzilla@wiggum.w3.org
- [Bug 6349] Rewrite the entire script processing model again bugzilla@wiggum.w3.org
- [Bug 6357] <script> start tag parsing bugzilla@wiggum.w3.org
- [Bug 6352] Port acknowledgements from WF2 to HTML5 bugzilla@wiggum.w3.org
- [Bug 6350] Port examples from WF2 to HTML5 bugzilla@wiggum.w3.org
- [Bug 6294] Date microsyntax defines incorrect range for month and day fields bugzilla@wiggum.w3.org
- [Bug 6336] XSLT-compat doctype only allowed for use by XSLT bugzilla@wiggum.w3.org
- [Bug 6339] Define how to deal with onload, ononline, and other document/window-level events bugzilla@wiggum.w3.org
- [Bug 6293] specify that the value attribute on <input type=url> must be an absolute URL bugzilla@wiggum.w3.org
- [Bug 6258] Changing the encoding doesn't cover non-idempotent navigation bugzilla@wiggum.w3.org
- [Bug 6182] WebIDL - strokeStyle and fillStyle should be of type 'any' not 'DOMObject' bugzilla@wiggum.w3.org
- [Bug 6300] [references] reference RFC 5322 instead of RFC 2822 bugzilla@wiggum.w3.org
- [Bug 6236] scroll bar placement in frames bugzilla@wiggum.w3.org
- [Bug 6257] Please specify document.write()-safe points in the parse bugzilla@wiggum.w3.org
- [Bug 6177] Process Workers feedback bugzilla@wiggum.w3.org
- [Bug 6181] Process table feedback (including headers='" issue) bugzilla@wiggum.w3.org
- [Bug 6256] Mutation event behavior on document.open() unspecified bugzilla@wiggum.w3.org
- [Bug 6153] Process <eventsource> feedback bugzilla@wiggum.w3.org
- [Bug 6143] Linkify "pending external script" bugzilla@wiggum.w3.org
- [Bug 6127] Deal with origin details in WebSocket and postMessage feedback bugzilla@wiggum.w3.org
- [Bug 6104] <video> and <audio> should prevent cross-origin media loads bugzilla@wiggum.w3.org
- [Bug 6102] Please do not break applet element in HTML 5 bugzilla@wiggum.w3.org
- [Bug 6176] Process WebSocket feedback bugzilla@wiggum.w3.org
- [Bug 6101] media elements - ready states - events should be async bugzilla@wiggum.w3.org
- [Bug 6099] Process notification feedback bugzilla@wiggum.w3.org
- [Bug 6134] Run-on sentence in HTML5 spec bugzilla@wiggum.w3.org
- [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' bugzilla@wiggum.w3.org
- [Bug 6037] Elaborate on Web compat characteristics of task queue interaction bugzilla@wiggum.w3.org
- [Bug 6103] video section editorial issues bugzilla@wiggum.w3.org
- [Bug 6100] Process postMessage feedback bugzilla@wiggum.w3.org
- [Bug 6098] input type=foo as an element-level section bugzilla@wiggum.w3.org
- [Bug 6052] Should propagate uncaught exceptions from workers to their owner bugzilla@wiggum.w3.org
- [Bug 6038] "noframes", "script", "style", "title" in 'after head' mode pop prematurely bugzilla@wiggum.w3.org
- [Bug 6035] Process appcache feedback bugzilla@wiggum.w3.org
- [Bug 6034] Process <video> feedback bugzilla@wiggum.w3.org
- [Bug 6033] Forms section bugzilla@wiggum.w3.org
- [Bug 5997] Define script execution for XHTML5 bugzilla@wiggum.w3.org
- [Bug 5994] add note in syntax section bugzilla@wiggum.w3.org
- [Bug 5991] workers bugzilla@wiggum.w3.org
- [Bug 5990] SVG in HTML bugzilla@wiggum.w3.org
- [Bug 5989] alt="" bugzilla@wiggum.w3.org
- [Bug 5974] Language tag sameness should probably be ASCII case-insensitive bugzilla@wiggum.w3.org
- [Bug 5944] Unclear wording, section 8.2.3.1 bugzilla@wiggum.w3.org
- [Bug 5937] make cache manifest syntax more extensible bugzilla@wiggum.w3.org
- [Bug 5936] Offline cache syntax section needs an example bugzilla@wiggum.w3.org
- [Bug 5883] data: URLs bugzilla@wiggum.w3.org
- [Bug 5881] Make tokeniser data states headers visible in table of contents bugzilla@wiggum.w3.org
- [Bug 5866] SVG in HTML bugzilla@wiggum.w3.org
- [Bug 5863] Tokeniser: "Bogus comment" state unclear bugzilla@wiggum.w3.org
- [Bug 5927] WF2: HTMLInputElement need some improvements bugzilla@wiggum.w3.org
- [Bug 5909] Need a solution for replaceable properties bugzilla@wiggum.w3.org
- [Bug 5851] Consider adding .toArray() on NodeList and HTMLCollection bugzilla@wiggum.w3.org
- [Bug 5850] JS global object bugzilla@wiggum.w3.org
- [Bug 5858] Case marked as fragment when it can occur at other times bugzilla@wiggum.w3.org
- [Bug 5859] Spec doesn't handle unknown schemes bugzilla@wiggum.w3.org
- [Bug 5856] height/width DOM attributes in combination with display:none bugzilla@wiggum.w3.org
- [Bug 5848] Write the "fetching" section bugzilla@wiggum.w3.org
- [Bug 5846] Accessing Object Parameters from an Embedded SVG bugzilla@wiggum.w3.org
- [Bug 5839] Work on Worker Threads bugzilla@wiggum.w3.org
- [Bug 5835] no apparent mechanism for applying a caption to a fieldset bugzilla@wiggum.w3.org
- [Bug 5834] <area alt=""> has no author-level conformance requirement bugzilla@wiggum.w3.org
- [Bug 5833] Work on standalone apps ideas bugzilla@wiggum.w3.org
- [Bug 5831] WebIDL: mark up constructors in IDL bugzilla@wiggum.w3.org
- [Bug 5830] Work on video bugzilla@wiggum.w3.org
- [Bug 5823] Scope allowable on a td bugzilla@wiggum.w3.org
- [Bug 5820] Work on WebSockets bugzilla@wiggum.w3.org
- [Bug 5815] foreignObject in the SVG namespace should be scoping bugzilla@wiggum.w3.org
- [Bug 5814] WebIDL: Resolve the callback issue bugzilla@wiggum.w3.org
- [Bug 5809] Mitigate data loss when conforming documents are coerced to XML 1.0 bugzilla@wiggum.w3.org
- [Bug 5807] User Agent display of title attribute content not defined bugzilla@wiggum.w3.org
- [Bug 5803] HTML5 serialization is not compatible with XSLT bugzilla@wiggum.w3.org
- [Bug 5801] Conformance rules for xmlns unintuitively different for HTML and foreign content bugzilla@wiggum.w3.org
- [Bug 5802] No mention of %uXXXX escapes bugzilla@wiggum.w3.org
- [Bug 5773] Authors need more control over handling of linked resources bugzilla@wiggum.w3.org
- [Bug 5798] Deferring end tag eating to after head gives weird errors bugzilla@wiggum.w3.org
- [Bug 5796] <li><div><p><li> no longer matches IE bugzilla@wiggum.w3.org
- [Bug 5793] Cross-reference "as if" bugzilla@wiggum.w3.org
- [Bug 5792] li/dd/dt end tag in body when no corresponding elt on stack bugzilla@wiggum.w3.org
- [Bug 5777] referencing subordinate text or asides should be through an alternate attribute bugzilla@wiggum.w3.org
- [Bug 5776] Authors need more control over handling of embedded resources bugzilla@wiggum.w3.org
- [Bug 5772] [blocked on sandbox="" implementations] ID scoping for content aggregators (<iframe doc="">) bugzilla@wiggum.w3.org
- [Bug 5758] insufficient accessibility fallback for <audio> or <video> bugzilla@wiggum.w3.org
- [Bug 5757] MediaElement features are needed on OBJECT element bugzilla@wiggum.w3.org
- [Bug 5756] Need interactive UA norms for exposing (non-displayed) HTML document data bugzilla@wiggum.w3.org
- [Bug 5755] Need to expose media metadata properties bugzilla@wiggum.w3.org
- [Bug 5754] List elements content model issues bugzilla@wiggum.w3.org
- [Bug 5753] parsing issues with legacy UAs bugzilla@wiggum.w3.org
- [Bug 9239] specify a convention for preventing vendor-specific non-standard extensions from clashing with themselves and future standard development bugzilla@wiggum.w3.org
- [Bug 9245] New: Poster should somehow also be able to define a frame (or timeline position) to be used as the frame. bugzilla@wiggum.w3.org
- [Bug 9242] It is not clear whether "shortcut icon" is a valid keyword; it is widely used and seems to validate in the experimental HTML5 validator. bugzilla@wiggum.w3.org
- [Bug 9244] New: "if the values used are not allowed according to the definitions in this specification, then the element does not define a link": What should happen if one value is valid and one isn't? bugzilla@wiggum.w3.org
- [Bug 9243] New: This section should print the character in addition to its unicode number. bugzilla@wiggum.w3.org
Saturday, 13 March 2010
- [Bug 9233] Incorporate a Link to UAAG with appropriate wording into browser sections bugzilla@wiggum.w3.org
- [Bug 9233] Incorporate a Link to UAAG with appropriate wording into browser sections bugzilla@wiggum.w3.org
- [Bug 9233] Incorporate a Link to UAAG with appropriate wording into browser sections bugzilla@wiggum.w3.org
- [Bug 9242] New: It is not clear whether "shortcut icon" is a valid keyword; it is widely used and seems to validate in the experimental HTML5 validator. bugzilla@wiggum.w3.org
- [Bug 9241] New: Explicitly state, "For guidance on accessibility requirements for text alternatives authors should consult WCAG 2.0" and link to WCAG 2.0 bugzilla@wiggum.w3.org
- [Bug 9233] Incorporate a Link to UAAG with appropriate wording into browser sections bugzilla@wiggum.w3.org
- [Bug 9233] Incorporate a Link to UAAG with appropriate wording into browser sections bugzilla@wiggum.w3.org
- [Bug 9233] Incorporate a Link to UAAG with appropriate wording into browser sections bugzilla@wiggum.w3.org
- [Bug 9230] Név: C:\Documents and Settings\bb\Dokumentumok\Videók\amator-tini-punci (77).jpg Formátum: JPG - Joint Photographic Experts Group Méret: 10.86 KB Dátum: 2010. március 12., 11:32:42 Szélesség: 325 Pixels Magasság: 425 Pixels Színmélység: 24 B bugzilla@wiggum.w3.org
- [Bug 9228] The i and b elements should not be included. Fundamentally they are visual markup elements and that should be accomplished in CSS, not using element. bugzilla@wiggum.w3.org
- [Bug 9222] If this state does not conform to RFC 5322, how IS it of practical use? bugzilla@wiggum.w3.org
- [Bug 9240] New: rules for td[align=center] are missing bugzilla@wiggum.w3.org
- [Bug 9239] New: specify a convention for preventing vendor-specific non-standard extensions from clashing with themselves and future standard development bugzilla@wiggum.w3.org
- [Bug 9231] Use a more conservative algorithm for crawling the properties of an item bugzilla@wiggum.w3.org
Friday, 12 March 2010
- [Bug 9236] Add Path objects and intersects() function bugzilla@wiggum.w3.org
- [Bug 9237] html5 bugzilla@wiggum.w3.org
- [Bug 9098] Correct the img element definition. Replace with suggested text. bugzilla@wiggum.w3.org
- [Bug 9237] New: html5 bugzilla@wiggum.w3.org
- [Bug 9233] Incorporate a Link to UAAG with appropriate wording into browser sections bugzilla@wiggum.w3.org
- [Bug 9236] Add Path objects and intersects() function bugzilla@wiggum.w3.org
- [Bug 9236] New: Add Path objects and intersects() function bugzilla@wiggum.w3.org
- [Bug 9235] An additional useful transformation would be Perspective. bugzilla@wiggum.w3.org
- [Bug 9235] New: An additional useful transformation would be Perspective. bugzilla@wiggum.w3.org
- [Bug 9234] some comment bugzilla@wiggum.w3.org
- [Bug 9234] New: some comment bugzilla@wiggum.w3.org
- [Bug 9233] Incorporate a Link to UAAG with appropriate wording into browser sections bugzilla@wiggum.w3.org
- [Bug 9233] New: Incorporate a Link to UAAG with appropriate wording into browser sections bugzilla@wiggum.w3.org
- [Bug 9227] Setting IDL attributes that map enumerated content attributes to invalid values should not throw bugzilla@wiggum.w3.org
- [Bug 9232] New: name=size should also be highlighted bugzilla@wiggum.w3.org
- [Bug 9231] New: fix loopiness as per http://lists.w3.org/Archives/Public/public-html/2010Feb/0030.html bugzilla@wiggum.w3.org
- [Bug 9230] New: Név: C:\Documents and Settings\bb\Dokumentumok\Videók\amator-tini-punci (77).jpg Formátum: JPG - Joint Photographic Experts Group Méret: 10.86 KB Dátum: 2010. március 12., 11:32:42 Szélesség: 325 Pixels Magasság: 425 Pixels Színmélység: 24 B bugzilla@wiggum.w3.org
- [Bug 9227] Setting IDL attributes that map enumerated content attributes to invalid values should not throw bugzilla@wiggum.w3.org
- [Bug 9228] New: The i and b elements should not be included. Fundamentally they are visual markup elements and that should be accomplished in CSS, not using element. bugzilla@wiggum.w3.org
- [Bug 9227] New: Setting IDL attributes that map enumerated content attributes to invalid values should not throw bugzilla@wiggum.w3.org
Thursday, 11 March 2010
- [Bug 8646] Private communication exception bugzilla@wiggum.w3.org
- [Bug 9226] New: The subcategories of form-associated elements should have consistent naming. Probably all of them should end in "elements". bugzilla@wiggum.w3.org
- [Bug 9224] It should be mentioned that setting playbackRate can be ignored. I.e. if playing backwards is not supported by the codec, if hardware acceleration does not support it, etc. bugzilla@wiggum.w3.org
- [Bug 9225] New: lax interpretation of legacy encoding decl allows attackers to change encoding of a page bugzilla@wiggum.w3.org
- [Bug 9224] It should be mentioned that setting playbackRate can be ignored. I.e. if playing backwards is not supported by the codec, if hardware acceleration does not support it, etc. bugzilla@wiggum.w3.org
- [Bug 9224] New: It should be mentioned that setting playbackRate can be ignored. I.e. if playing backwards is not supported by the codec, if hardware acceleration does not support it, etc. bugzilla@wiggum.w3.org
- [Bug 8896] Clarify that anyone who is dissatisfied with a bug resolution may reopen or escalate bugzilla@wiggum.w3.org
- [Bug 8896] Clarify that anyone who is dissatisfied with a bug resolution may reopen or escalate bugzilla@wiggum.w3.org
Wednesday, 10 March 2010
- [Bug 9187] Need transparency in issue and bug status in databases & document. bugzilla@wiggum.w3.org
- [Bug 8896] Clarify that anyone who is dissatisfied with a bug resolution may reopen or escalate bugzilla@wiggum.w3.org
- [Bug 9187] Need transparency in issue and bug status in databases & document. bugzilla@wiggum.w3.org
- [Bug 9187] Need transparency in issue and bug status in databases & document. bugzilla@wiggum.w3.org
- [Bug 9187] Need transparency in issue and bug status in databases & document. bugzilla@wiggum.w3.org
- [Bug 8896] Clarify that anyone who is dissatisfied with a bug resolution may reopen or escalate bugzilla@wiggum.w3.org
- [Bug 9187] Need transparency in issue and bug status in databases & document. bugzilla@wiggum.w3.org
- [Bug 8894] Document process for counter-proposals and alternate proposals bugzilla@wiggum.w3.org
- [Bug 9187] Need transparency in issue and bug status in databases & document. bugzilla@wiggum.w3.org
- [Bug 9093] </p>text would ignore </p>, but it does not on IE8. bugzilla@wiggum.w3.org
- [Bug 9092] </br><frameset>text would generate a frameset per spec, since the frameset-ok flag should be ok after </br> is seen. But an IE8 test shows otherwise bugzilla@wiggum.w3.org
- [Bug 9172] "© Copyright 2004-2009" - s/2009/2010/ [pt] bugzilla@wiggum.w3.org
- [Bug 8716] Replace img Guidance for Conformance Checkers with Suggested Text for Short Text Alternatives bugzilla@wiggum.w3.org
- [Bug 6496] Allow <img aria-labelledby> to act as a text alternative bugzilla@wiggum.w3.org
- [Bug 8646] Private communication exception bugzilla@wiggum.w3.org
- [Bug 8716] Replace img Guidance for Conformance Checkers with Suggested Text for Short Text Alternatives bugzilla@wiggum.w3.org
- [Bug 9223] New: It is unlikely this will work on mobile as you cannot make tcp connections into a mobile phone. They will be blocked by the operator's firewall and this is very unlikely to change. Of course, this isn't a reason not to specify this, but it's good to be aw bugzilla@wiggum.w3.org
- [Bug 9022] spec author names bugzilla@wiggum.w3.org
- [Bug 8646] Private communication exception bugzilla@wiggum.w3.org
- [Bug 8646] Private communication exception bugzilla@wiggum.w3.org
- [Bug 6496] Allow <img aria-labelledby> to act as a text alternative bugzilla@wiggum.w3.org
- [Bug 9001] Consistent "Status" sections for Microdata and RDFa bugzilla@wiggum.w3.org
- [Bug 9001] Consistent "Status" sections for Microdata and RDFa bugzilla@wiggum.w3.org
- [Bug 9001] Consistent "Status" sections for Microdata and RDFa bugzilla@wiggum.w3.org
- [Bug 9001] Consistent "Status" sections for Microdata and RDFa bugzilla@wiggum.w3.org
- [Bug 8835] Clarifcation of the purpose of "Markup" spec and possible renaming of it. bugzilla@wiggum.w3.org
- [Bug 8871] Empty attribute syntax definition seems incorrect. bugzilla@wiggum.w3.org
- [Bug 9222] New: If this state does not conform to RFC 5322, how IS it of practical use? bugzilla@wiggum.w3.org
- [Bug 9001] Consistent "Status" sections for Microdata and RDFa bugzilla@wiggum.w3.org
- [Bug 9219] Language values should be defined by BCP 47 bugzilla@wiggum.w3.org
- [Bug 6505] should h:tml draft describe for authors how relative URLs are resolved? bugzilla@wiggum.w3.org
Tuesday, 9 March 2010
- [Bug 9221] New: still unclear definition of "plugin" bugzilla@wiggum.w3.org
- [Bug 9187] Need transparency in issue and bug status in databases & document. bugzilla@wiggum.w3.org
- [Bug 6504] description of what target attribute represents should not use term "browsing context" bugzilla@wiggum.w3.org
- [Bug 9010] There are one or more alternate methods of adding data without using RDFa, such as [microdata]. bugzilla@wiggum.w3.org
- [Bug 9187] Need transparency in issue and bug status in databases & document. bugzilla@wiggum.w3.org
- [Bug 9187] Need transparency in issue and bug status in databases & document. bugzilla@wiggum.w3.org
Monday, 8 March 2010
- [Bug 9220] New: xref doesn't work for "bgcolor" in "When a body, table, thead, tbody, tfoot, tr, td, or th element has a bgcolor attribute set" bugzilla@wiggum.w3.org
- [Bug 9219] New: Language values should be defined by BCP 47 bugzilla@wiggum.w3.org
- [Bug 9218] New: Enable Automatic Validators to Programmatically Determine the Presence or Absence of a Set of Text Alternatives bugzilla@wiggum.w3.org
- [Bug 9217] New: Remove the Paragraph-Section-Heading loophole for not providing a text alternative. bugzilla@wiggum.w3.org
- [Bug 9216] New: Provide a CAPTCHA example that is in accord with WCAG 2 or Defer to "HTML5: Techniques for providing useful text alternatives" bugzilla@wiggum.w3.org
- [Bug 9215] New: Provide a Webcam example that is in accord with WCAG 2 or Defer to "HTML5: Techniques for providing useful text alternatives" bugzilla@wiggum.w3.org
- [Bug 9214] New: Allow role="presentation" on img bugzilla@wiggum.w3.org
- [Bug 9213] New: HTML5 Lacks a Way to Programmatically-Determine Missing Text Alternatives bugzilla@wiggum.w3.org
- [Bug 9212] New: Change the Generator Mechanism for img from Document Level to Element Level bugzilla@wiggum.w3.org
- [Bug 9187] Need transparency in issue and bug status in databases & document. bugzilla@wiggum.w3.org
- [Bug 9211] New: slotIndices (new IDL attribute): collection of all col-row intersections (slots) the cell spans bugzilla@wiggum.w3.org
- [Bug 9210] New: colSpan: there is no default value (rowSpan has one) bugzilla@wiggum.w3.org
- [Bug 9209] New: sectionRowIndex: check text in parentheses, seems redundant bugzilla@wiggum.w3.org
- [Bug 9208] New: “isn't” – either “s not” or “isn’t” bugzilla@wiggum.w3.org
- [Bug 9207] Anything else: This part of the spec is problematic, for example, a query string variable &lang_id=1 in as part of an attribute of say an img tag, will get converted into an character token when it shouldn't be. Why is the set of characters a-z, A-Z, 0- bugzilla@wiggum.w3.org
- [Bug 9207] Anything else: This part of the spec is problematic, for example, a query string variable &lang_id=1 in as part of an attribute of say an img tag, will get converted into an character token when it shouldn't be. Why is the set of characters a-z, A-Z, 0- bugzilla@wiggum.w3.org
- [Bug 9207] New: Anything else: This part of the spec is problematic, for example, a query string variable &lang_id=1 in as part of an attribute of say an img tag, will get converted into an character token when it shouldn't be. Why is the set of characters a-z, A-Z, 0- bugzilla@wiggum.w3.org
Sunday, 7 March 2010
- [Bug 9030] Add more dfns (more helpful list coming) bugzilla@wiggum.w3.org
- [Bug 9206] New: "datetime content attribute" xref is dead bugzilla@wiggum.w3.org
Saturday, 6 March 2010
- [Bug 9205] New: I'm missing a specification on the relation between onreadystatechange and onload. Will they be used interchangeably? When will they fire? Will onreadystatechange fire multiple times during downloading an external resource (readystate="loading")? bugzilla@wiggum.w3.org
- [Bug 9204] New: The onload event is missing a description on when it fires. Particularly on elements downloading auxiliary documents (img, script, link) it is important to specify when exactly that event is fired. Same for onerror and onabort events (and similar). bugzilla@wiggum.w3.org
- [Bug 9030] Add more dfns (more helpful list coming) bugzilla@wiggum.w3.org
- [Bug 9202] New: This comment overlays found text in my Firefox 3.0.18, which is bad. bugzilla@wiggum.w3.org
- [Bug 9201] New: xref getElementById() bugzilla@wiggum.w3.org
- [Bug 9200] New: xref document.getElementById(), and clarify on which document it should be called. bugzilla@wiggum.w3.org
- [Bug 9199] New: [a-urn] xref "href" bugzilla@wiggum.w3.org
- [Bug 9198] New: <embed hspace> and <embed vspace> should not be allowed bugzilla@wiggum.w3.org
Friday, 5 March 2010
- [Bug 9187] Need transparency in issue and bug status in databases & document. bugzilla@wiggum.w3.org
- [Bug 9195] the icns format does not support such ridiculously huge icon sizes! Where can I get an 8k x 8k screen please? printing would use the SVG anyway. bugzilla@wiggum.w3.org
- [Bug 9194] hello android bugzilla@wiggum.w3.org
- [Bug 9192] test sdgfdsfg dfsgdfsg dsgd bugzilla@wiggum.w3.org
- [Bug 9197] Remove unnecessary editorialization in acknowledgement section bugzilla@wiggum.w3.org
- [Bug 9197] New: Remove unnecessary editorialization in acknowledgement section bugzilla@wiggum.w3.org
- [Bug 9195] New: the icns format does not support such ridiculously huge icon sizes! Where can I get an 8k x 8k screen please? printing would use the SVG anyway. bugzilla@wiggum.w3.org
- [Bug 9194] New: hello android bugzilla@wiggum.w3.org
- [Bug 9145] steps 1 to 3 could be merged into "A string that is an ASCII case-insensitive match for the string "<!DOCTYPE"" bugzilla@wiggum.w3.org
- [Bug 9185] typo: search for |(such as Cookie")| bugzilla@wiggum.w3.org
- [Bug 9185] typo: search for |(such as Cookie")| bugzilla@wiggum.w3.org
- [Bug 9193] New: "If hash changed is true, then, if the new URL has a fragment identifier, scroll to the fragment identifier." is wrong. It should scroll if it's a new entry that hasn't been traversed to before, even if it's the same fragid as before; and it should _not_ bugzilla@wiggum.w3.org
Thursday, 4 March 2010
- [Bug 9192] New: test sdgfdsfg dfsgdfsg dsgd bugzilla@wiggum.w3.org
- [Bug 9191] Is there a way to get the text back out? e.g., context.getTexts returning an array of the character strings ever added with fillText and strokeText? -jJ bugzilla@wiggum.w3.org
- [Bug 9191] New: Is there a way to get the text back out? e.g., context.getTexts returning an array of the character strings ever added with fillText and strokeText? -jJ bugzilla@wiggum.w3.org
- [Bug 9190] New: What effects do fillText and strokeText have on the accessibility fallback (ADOM?)? Should they take a default to also adding it, as by canvas.appendChild(document.createTextNode(s))? (Then maybe add a 5th parameter to allow turning it off) -jJ bugzilla@wiggum.w3.org
- [Bug 9189] New: CanvasGradient should use parameters at the time of drawing bugzilla@wiggum.w3.org
- [Bug 9188] New: Fix the references in the txt version to have URLs. bugzilla@wiggum.w3.org
- [Bug 9187] New: Need transparency in issue and bug status in databases & document. bugzilla@wiggum.w3.org
- [Bug 9186] New: @abbr (td/th): may authors use @title instead? bugzilla@wiggum.w3.org
- [Bug 8722] focus behaviour should be same for canvas regions as for elements bugzilla@wiggum.w3.org
- [Bug 9185] New: typo: search for |(such as Cookie")| bugzilla@wiggum.w3.org
Wednesday, 3 March 2010
- [Bug 9184] New: "COOKIES" reference references old Internet Draft bugzilla@wiggum.w3.org
- [Bug 9182] New: Can I nest <ruby> elements? I think that you should add content model of the <ruby> element, "but there must be no ruby element descendants.". bugzilla@wiggum.w3.org
- [Bug 8893] Clarify how Change Proposals get reviewed and what happens to Change Proposals that do not meet requirements bugzilla@wiggum.w3.org
- [Bug 8895] Document policy for First Public Working Drafts bugzilla@wiggum.w3.org
- [Bug 9181] New: Find the effectAllowed line bugzilla@wiggum.w3.org
- [Bug 9180] New: "The event thus is not to be fired faster than about 66Hz or slower than 4Hz." - unless the event handler is still running, in which case it could be slower bugzilla@wiggum.w3.org
- [Bug 8611] Consider adding a full schema to H:TML bugzilla@wiggum.w3.org
- [Bug 8611] Consider adding a full schema to H:TML bugzilla@wiggum.w3.org
Tuesday, 2 March 2010
- [Bug 9155] "The attribute must be ignored if the autoplay attribute is present." - seems wrong when the user has set a pref to make autoplay="" not autoplay bugzilla@wiggum.w3.org
- [Bug 9179] New: <body><section> results in <section> being associated with the <body> element's section. I'd expect <section> to be associated with its own section. bugzilla@wiggum.w3.org
- [Bug 9157] What does this mean for <a>? What does it mean for <a target=_blank>? Following links should probably always work. bugzilla@wiggum.w3.org
- [Bug 9178] New: add definition of "conforming document" bugzilla@wiggum.w3.org
- [Bug 9177] New: Can the script element please allow the scope attribute in the same semantic way as the style element? The dom would be limited to only elements under that node. bugzilla@wiggum.w3.org
Monday, 1 March 2010
- [Bug 8357] Possible Compromise solution for namespaces in HTML5 bugzilla@wiggum.w3.org
- [Bug 8611] Consider adding a full schema to H:TML bugzilla@wiggum.w3.org
- [Bug 9176] New: typo in 4th |th|: ‘per _c_ent’ (or rather ‘percent’) and please be metric, not inchic bugzilla@wiggum.w3.org
- [Bug 9175] New: should clearly say that cellIndex is not necessarily the same as slot_x (and there should be easy access to slot_x and slot_y) bugzilla@wiggum.w3.org
- [Bug 9170] Too good bugzilla@wiggum.w3.org
- [Bug 9174] New: Consider adding a Webcam example bugzilla@wiggum.w3.org
- [Bug 9173] New: This section should have a stable id so that http://dev.w3.org/html5/tests/submission/Microsoft/windowobject/security_location_0.htm can link to it bugzilla@wiggum.w3.org
- [Bug 9172] New: "© Copyright 2004-2009" - s/2009/2010/ [pt] bugzilla@wiggum.w3.org

Last message date: Wednesday, 31 March 2010 22:44:10 GMT
Archived on: Wednesday, 31 March 2010 22:44:29 GMT

public-html-bugzilla@w3.org from March 2010 by date