Sunday, 28 February 2010
- [Bug 9169] Consider adding a CAPTCHA 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 9170] New: Too good bugzilla@wiggum.w3.org
- [Bug 9169] New: Consider adding a CAPTCHA example bugzilla@wiggum.w3.org
- [Bug 9167] Must not contain periods(".") de id and class, (and posible not #, :, {) because is not accesible from CSS . example in html id="name.last" in CSS selectors is imposible to select it because will search form id name class last. In html is possible use bugzilla@wiggum.w3.org
- [Bug 9167] Must not contain periods(".") de id and class, (and posible not #, :, {) because is not accesible from CSS . example in html id="name.last" in CSS selectors is imposible to select it because will search form id name class last. In html is possible use bugzilla@wiggum.w3.org
- [Bug 9166] Must not contain periods(".") de id and class, (and posible not #, :, {) because is not accesible from CSS . example in html id="name.last" in CSS selectors is imposible to select it because will search form id name class last. bugzilla@wiggum.w3.org
- [Bug 9167] Must not contain periods(".") de id and class, (and posible not #, :, {) because is not accesible from CSS . example in html id="name.last" in CSS selectors is imposible to select it because will search form id name class last. In html is possible use bugzilla@wiggum.w3.org
- [Bug 9165] Must not contain periods(".") de id and class, (and posible not #, :, {) because is not accesible from CSS bugzilla@wiggum.w3.org
- [Bug 9168] New: iframeborder -> frameborder bugzilla@wiggum.w3.org
Saturday, 27 February 2010
- [Bug 9167] New: Must not contain periods(".") de id and class, (and posible not #, :, {) because is not accesible from CSS . example in html id="name.last" in CSS selectors is imposible to select it because will search form id name class last. In html is possible use bugzilla@wiggum.w3.org
- [Bug 9166] New: Must not contain periods(".") de id and class, (and posible not #, :, {) because is not accesible from CSS . example in html id="name.last" in CSS selectors is imposible to select it because will search form id name class last. bugzilla@wiggum.w3.org
- [Bug 9165] New: Must not contain periods(".") de id and class, (and posible not #, :, {) because is not accesible from CSS bugzilla@wiggum.w3.org
- [Bug 9164] New: 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] New: The domintro box only has document.dir, and ought to have element.dir too. [pt] bugzilla@wiggum.w3.org
- [Bug 9162] New: please define authors' requirements and non-normative introduction for authors to HTML's fragment identifiers bugzilla@wiggum.w3.org
- [Bug 9161] New: it should explicitly say alt="" MUST NOT be blank unless it MAY be left blank bugzilla@wiggum.w3.org
- [Bug 9160] New: Constraint validation ought to match a radio group; that is, if any checkbox in the group is checked, the whole control is valid. Not only would this change make the API consistent for mutually-exclusive (radio) and mutually-inexclusive (checkbox) widget bugzilla@wiggum.w3.org
- [Bug 9159] New: 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
Friday, 26 February 2010
Thursday, 25 February 2010
- [Bug 9155] New: "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 9154] New: 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 9097] Add wbr { content: "\200B"; } (ZWSP)? 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 9071] Handling of "[" in between-doctype-public-and-system-identifiers-state may not be ideal bugzilla@wiggum.w3.org
- [Bug 9153] New: The element list isn't in alphabetical order (unlike the same element list further down). bugzilla@wiggum.w3.org
- [Bug 9152] New: The list of elements doesn't include elements like input, select (and probably others) that are includes in MSIE. bugzilla@wiggum.w3.org
- [Bug 9151] New: The first item in the list seems truncated or not in item list form. It ends "and," bugzilla@wiggum.w3.org
- [Bug 9149] New: Don't require set-cookie2; see <https://bugzilla.mozilla.org/show_bug.cgi?id=472529#c129> bugzilla@wiggum.w3.org
- [Bug 9128] It seems a bad idea to willfully violate the character model specification for a new standard. New HTML documents should have the correct encoding and should not need to be mis-interpreted. Why not specify mandatory UTF-8 anyway? bugzilla@wiggum.w3.org
- [Bug 9146] is this useful? bugzilla@wiggum.w3.org
- [Bug 9148] New: "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 9146] New: is this useful? bugzilla@wiggum.w3.org
- [Bug 9097] Add wbr { content: "\200B"; } (ZWSP)? bugzilla@wiggum.w3.org
- [Bug 9096] Mapping U+0000 to U+FFFD regresses rendering of pages bugzilla@wiggum.w3.org
- [Bug 9094] It should be stylable (thru CSS markup) 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 9091] <span itemprop="fn">David Junger</span> 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 9082] Step 20. "the table" seems to be repeated unnecessarily bugzilla@wiggum.w3.org
- [Bug 9082] Step 20. "the table" seems to be repeated unnecessarily bugzilla@wiggum.w3.org
- [Bug 9145] New: 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 9144] New: should expand to CR bugzilla@wiggum.w3.org
- [Bug 9143] New: I notice that under the definition for the-i-element it says "Authors are encouraged to use the class attribute on the i element to identify why the element is being used", but there's no similar text for b. Given the Note on both, it seems you'd want to bugzilla@wiggum.w3.org
- [Bug 9083] This should mention that it includes framing overhead. bugzilla@wiggum.w3.org
- [Bug 9083] This should mention that it includes framing overhead. bugzilla@wiggum.w3.org
- [Bug 8731] Consider expanding buffering control for media elements bugzilla@wiggum.w3.org
- [Bug 8731] Consider expanding buffering control for media elements bugzilla@wiggum.w3.org
- [Bug 9043] Must the href attribute of <base> be a full URL, including http://...; if so, what is the correct terminology for that? I tried following the "valid URL" link and it goes down a rabbit hole to http://www.w3.org/html/wg/href/draft, which does not define "v bugzilla@wiggum.w3.org
- [Bug 9045] The term "valid URL" is used here, but following the link does not lead to a definition bugzilla@wiggum.w3.org
- [Bug 9049] What is the correct behavior if a <meta http-equiv="Content-Type"> conflicts with <meta charset>? bugzilla@wiggum.w3.org
- [Bug 9049] What is the correct behavior if a <meta http-equiv="Content-Type"> conflicts with <meta charset>? bugzilla@wiggum.w3.org
- [Bug 9055] There is no direct replacement for a frameset. This supports some functionality and features that can't be emulated 100% by other methods. Server side includes cannot dynamically udpate pages, nor can new pages be loaded with javascript. This is a crit bugzilla@wiggum.w3.org
- [Bug 9073] "Configuring o form"? [pt] bugzilla@wiggum.w3.org
- [Bug 9072] There's inconsistent quoting of attributes between the highlighted and non-highlited parts of this section bugzilla@wiggum.w3.org
- [Bug 9068] Windows-31J preferred name is with the "W" uppercase, not as given in the overrides where it is lowercase. (w00t! consistency!) bugzilla@wiggum.w3.org
- [Bug 9068] Windows-31J preferred name is with the "W" uppercase, not as given in the overrides where it is lowercase. (w00t! consistency!) bugzilla@wiggum.w3.org
- [Bug 9066] You state "many users disable scripting"... the most reliable stats I can find indicate that at most 1-2% of users have JS diabled. So using "many" is rather misleading. bugzilla@wiggum.w3.org
- [Bug 9053] Should the "name=size" attributes in the "Pizza Size" radio buttons also be included in the <strong> markup which immediately follows them? bugzilla@wiggum.w3.org
- [Bug 9053] Should the "name=size" attributes in the "Pizza Size" radio buttons also be included in the <strong> markup which immediately follows them? 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 9071] Handling of "[" in between-doctype-public-and-system-identifiers-state may not be ideal 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 9071] Handling of "[" in between-doctype-public-and-system-identifiers-state may not be ideal bugzilla@wiggum.w3.org
- [Bug 7616] Move requirement about obsolete doctypes bugzilla@wiggum.w3.org
- [Bug 7616] Move requirement about obsolete doctypes bugzilla@wiggum.w3.org
- [Bug 9016] Make parameters on applet use the same rules as object (except for codebase="") bugzilla@wiggum.w3.org
- [Bug 9016] Make parameters on applet use the same rules as object (except for codebase="") 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 9060] Add "in" into: "the user agent must act as if the element was" ...in... "a stack of open elements." bugzilla@wiggum.w3.org
- [Bug 9060] Add "in" into: "the user agent must act as if the element was" ...in... "a stack of open elements." bugzilla@wiggum.w3.org
- [Bug 8722] focus behaviour should be same for canvas regions as for elements bugzilla@wiggum.w3.org
- [Bug 9052] All DOCTYPE variants that trigger standards mode pre-HTML5 should continue to trigger standards mode in HTML5 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 9071] Handling of "[" in between-doctype-public-and-system-identifiers-state may not be ideal bugzilla@wiggum.w3.org
- [Bug 8818] Remove the srcdoc attribute bugzilla@wiggum.w3.org
- [Bug 8966] Consider "<svg><desc><div><svg><desc><b>X" — Should we change "Pop elements from the stack of open elements until the current node is in the HTML namespace." in the in-foreign-content mode to actually be "Pop elements until there's no element in scope t bugzilla@wiggum.w3.org
- [Bug 8767] <svg><font>x</font>y</svg>z is not parsed as intended. the in body insertion mode processes </font> as HTML formatting element, not as a foreign element's tag. bugzilla@wiggum.w3.org
- [Bug 8767] <svg><font>x</font>y</svg>z is not parsed as intended. the in body insertion mode processes </font> as HTML formatting element, not as a foreign element's tag. bugzilla@wiggum.w3.org
Wednesday, 24 February 2010
Tuesday, 23 February 2010
- [Bug 9085] "If the playback has ended, seek to the earliest possible position of the media resource." - should also check if direction is forwards, since if direction is backwards we're already at the earliest position bugzilla@wiggum.w3.org
- [Bug 9085] "If the playback has ended, seek to the earliest possible position of the media resource." - should also check if direction is forwards, since if direction is backwards we're already at the earliest position bugzilla@wiggum.w3.org
- [Bug 9057] status section, ref to "HTML specifications" bugzilla@wiggum.w3.org
- [Bug 9057] status section, ref to "HTML specifications" bugzilla@wiggum.w3.org
- [Bug 9133] New: "if it is a number between 0.0 and 1.0" - does 'between' mean inclusive or exclusive? bugzilla@wiggum.w3.org
- [Bug 9132] New: "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 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 9131] New: 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 9051] feed autodiscovery for main feed on posts bugzilla@wiggum.w3.org
- [Bug 9127] As others have pointed out: why have so many willfull violations to support legacy content if there is *no legacy HTML5 content to support?* bugzilla@wiggum.w3.org
- [Bug 9127] As others have pointed out: why have so many willfull violations to support legacy content if there is *no legacy HTML5 content to support?* bugzilla@wiggum.w3.org
- [Bug 9129] New: The terms used from the DOM specification need some <code> love. bugzilla@wiggum.w3.org
- [Bug 9128] New: It seems a bad idea to willfully violate the character model specification for a new standard. New HTML documents should have the correct encoding and should not need to be mis-interpreted. Why not specify mandatory UTF-8 anyway? bugzilla@wiggum.w3.org
- [Bug 9127] New: As others have pointed out: why have so many willfull violations to support legacy content if there is *no legacy HTML5 content to support?* bugzilla@wiggum.w3.org
- [Bug 9035] Interfaces for URL manipulation: concept of "hierarchical" 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 8784] politics in <param> example 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 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
- [Bug 9126] New: 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
- [Bug 9124] missing formatBlock candidates bugzilla@wiggum.w3.org
- [Bug 9125] missing formatBlock candidates bugzilla@wiggum.w3.org
- [Bug 9125] New: missing formatBlock candidates bugzilla@wiggum.w3.org
- [Bug 9124] New: missing formatBlock candidates bugzilla@wiggum.w3.org
- [Bug 8784] politics in <param> example bugzilla@wiggum.w3.org
- [Bug 9059] can I use wildcards to cache the whole directory? bugzilla@wiggum.w3.org
- [Bug 9059] can I use wildcards to cache the whole directory? 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 7896] Specify pageshow and pagehide events bugzilla@wiggum.w3.org
- [Bug 7896] Specify pageshow and pagehide events bugzilla@wiggum.w3.org
- [Bug 9017] The origin argument should be used to determine whether Referer is to be omitted for XMLHttpRequest. I'm not a 100% sure at the moment when that would matter, but it seems safer. bugzilla@wiggum.w3.org
- [Bug 9048] "If either name, http-equiv, or itemprop is specified, then the content attribute must also be specified. Otherwise, it must be omitted." Might be more clearly stated as "If charset is specified, then the content attribute must be omitted. Otherwise it mu bugzilla@wiggum.w3.org
- [Bug 9047] Should UAs print a page in a <link media=print> if no stylesheet with media=print is provided? bugzilla@wiggum.w3.org
- [Bug 9046] What, if anything, are UAs allowed to do with the advisory "type" attribute of <link>? bugzilla@wiggum.w3.org
- [Bug 9044] The context of <base> is "In a head element containing no other base elements" -- there are additional restrictions specified below that are not reflected here bugzilla@wiggum.w3.org
- [Bug 9042] In neither section 4.2.1 or 4.8.2 is the reason for leaving out the title in an iframe srcdoc clarified. Is this because it's inherited from the parent? Because it's irrelevant? What does document.title return in this case? bugzilla@wiggum.w3.org
- [Bug 9041] Is it worth mentioning that while there's no DOM API for the "manifest" attribute itself, there is an API for the cache manifest? bugzilla@wiggum.w3.org
- [Bug 9041] Is it worth mentioning that while there's no DOM API for the "manifest" attribute itself, there is an API for the cache manifest? bugzilla@wiggum.w3.org
- [Bug 9040] "Wherever a subdocument fragment is allowed in a compound document" -- What's an example of this? bugzilla@wiggum.w3.org
- [Bug 9036] Can we explain what setAttribute and setAttributeNode actually do? bugzilla@wiggum.w3.org
- [Bug 9039] Can we explain what getElementsByTagName does (and specifically, that it returns a NodeList)? bugzilla@wiggum.w3.org
- [Bug 9037] can we explain what getAttribute and and getAttributeNode do? bugzilla@wiggum.w3.org
- [Bug 8936] A summary table of the types of content and what elements belong to each would be helpful bugzilla@wiggum.w3.org
- [Bug 8936] A summary table of the types of content and what elements belong to each would be helpful bugzilla@wiggum.w3.org
- [Bug 9115] What's this bar? bugzilla@wiggum.w3.org
- [Bug 9035] Interfaces for URL manipulation: concept of "hierarchical" bugzilla@wiggum.w3.org
- [Bug 9035] Interfaces for URL manipulation: concept of "hierarchical" bugzilla@wiggum.w3.org
- [Bug 9035] Interfaces for URL manipulation: concept of "hierarchical" bugzilla@wiggum.w3.org
- [Bug 9035] Interfaces for URL manipulation: concept of "hierarchical" bugzilla@wiggum.w3.org
- [Bug 8937] setAttribute should specify the parameters (at least how many, but probably also a short description of each) bugzilla@wiggum.w3.org
- [Bug 9034] Is there any "white-space avoiding rule"? If not, Some HTML Editor may insert evil-poorlooked white-space. bugzilla@wiggum.w3.org
- [Bug 9033] In the green box, please clarify that event.state contains a clone of the object passed to pushState bugzilla@wiggum.w3.org
- [Bug 9033] In the green box, please clarify that event.state contains a clone of the object passed to pushState bugzilla@wiggum.w3.org
- [Bug 9024] fetch should be referenced from algorithms in Web workers. bugzilla@wiggum.w3.org
- [Bug 8747] Defining how a license applies to elements bugzilla@wiggum.w3.org
- [Bug 8752] Allow user to manage focus changes bugzilla@wiggum.w3.org
- [Bug 8716] Replace img Guidance for Conformance Checkers with Suggested Text for Short Text Alternatives bugzilla@wiggum.w3.org
- [Bug 8738] Role-based navigation bugzilla@wiggum.w3.org
- [Bug 8723] image map is underspecified bugzilla@wiggum.w3.org
- [Bug 8754] Overflow when text is resized bugzilla@wiggum.w3.org
- [Bug 8750] User able to override the hidden attribute in incorrectly rendered pages bugzilla@wiggum.w3.org
- [Bug 8751] User should have ability to override automatic scrolling bugzilla@wiggum.w3.org
- [Bug 8743] Auditory icons clashing with AT bugzilla@wiggum.w3.org
- [Bug 8652] what to display when images are not available is not well specified bugzilla@wiggum.w3.org
- [Bug 8740] How do pseudo-class selectors interact with WAI-ARIA? bugzilla@wiggum.w3.org
- [Bug 8753] Undo for drag and drop bugzilla@wiggum.w3.org
- [Bug 8716] Replace img Guidance for Conformance Checkers with Suggested Text for Short Text Alternatives bugzilla@wiggum.w3.org
- [Bug 9029] Steps 2 and 3 should be in the relevant specifications, rather than inline bugzilla@wiggum.w3.org
- [Bug 8644] Fallback mechanism for embedded content bugzilla@wiggum.w3.org
- [Bug 9029] Steps 2 and 3 should be in the relevant specifications, rather than inline bugzilla@wiggum.w3.org
- [Bug 9028] "(either because of a fatal error during load that's about to be reported, or because the load() method was invoked while the resource selection algorithm was already running, in which case it is fired synchronously during the load() method call)." - empt bugzilla@wiggum.w3.org
- [Bug 9028] "(either because of a fatal error during load that's about to be reported, or because the load() method was invoked while the resource selection algorithm was already running, in which case it is fired synchronously during the load() method call)." - empt bugzilla@wiggum.w3.org
- [Bug 9027] doubled "as possible" bugzilla@wiggum.w3.org
- [Bug 9025] "the first five character removed" - should be "characters". [pt] bugzilla@wiggum.w3.org
- [Bug 9025] "the first five character removed" - should be "characters". [pt] bugzilla@wiggum.w3.org
- [Bug 9023] Dependency on Document does not work for Web Workers. bugzilla@wiggum.w3.org
- [Bug 9024] fetch should be referenced from algorithms in Web workers. bugzilla@wiggum.w3.org
- [Bug 9021] perhaps mention here semantic alternatives to common use cases: <strike> → <del>, <tt> → <code>, &c. bugzilla@wiggum.w3.org
- [Bug 9020] "When a control has a pattern attribute,": xref pattern bugzilla@wiggum.w3.org
- [Bug 9020] "When a control has a pattern attribute,": xref pattern 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 9018] Should "origin" be marked up as "<i>origin</i>" just like the synchronous flag? bugzilla@wiggum.w3.org
- [Bug 9017] The origin argument should be used to determine whether Referer is to be omitted for XMLHttpRequest. I'm not a 100% sure at the moment when that would matter, but it seems safer. bugzilla@wiggum.w3.org
Monday, 22 February 2010
Sunday, 21 February 2010
Saturday, 20 February 2010
Friday, 19 February 2010
- [Bug 9094] New: It should be stylable (thru CSS markup) bugzilla@wiggum.w3.org
- [Bug 9093] New: </p>text would ignore </p>, but it does not on IE8. bugzilla@wiggum.w3.org
- [Bug 9092] New: </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 9091] New: <span itemprop="fn">David Junger</span> bugzilla@wiggum.w3.org
- [Bug 9086] "If the playback has ended, seek to the earliest possible position of the media resource." - should also check if direction is forwards, since if direction is backwards we're already at the earliest position bugzilla@wiggum.w3.org
- [Bug 9085] "If the playback has ended, seek to the earliest possible position of the media resource." - should also check if direction is forwards, since if direction is backwards we're already at the earliest position bugzilla@wiggum.w3.org
- [Bug 9000] datasrc, <script event>, <script for> and so on are missing bugzilla@wiggum.w3.org
- [Bug 9000] datasrc, <script event>, <script for> and so on are missing bugzilla@wiggum.w3.org
- [Bug 9088] test test test test bugzilla@wiggum.w3.org
- [Bug 9088] New: test test test test bugzilla@wiggum.w3.org
- [Bug 9000] datasrc, <script event>, <script for> and so on are missing 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 9057] status section, ref to "HTML specifications" 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 9086] New: "If the playback has ended, seek to the earliest possible position of the media resource." - should also check if direction is forwards, since if direction is backwards we're already at the earliest position bugzilla@wiggum.w3.org
- [Bug 9085] New: "If the playback has ended, seek to the earliest possible position of the media resource." - should also check if direction is forwards, since if direction is backwards we're already at the earliest position bugzilla@wiggum.w3.org
- [Bug 9084] New: 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 9082] Step 20. "the table" seems to be repeated unnecessarily bugzilla@wiggum.w3.org
- [Bug 9083] New: This should mention that it includes framing overhead. bugzilla@wiggum.w3.org
- [Bug 9082] Step 20. "the table" seems to be repeated unnecessarily bugzilla@wiggum.w3.org
- [Bug 9082] Step 20. "the table" seems to be repeated unnecessarily bugzilla@wiggum.w3.org
- [Bug 9082] New: Step 20. "the table" seems to be repeated unnecessarily bugzilla@wiggum.w3.org
- [Bug 9081] New: Confusing alt text in the fourth The Lady of Shalott example bugzilla@wiggum.w3.org
- [Bug 9080] New: Confusing alt text in the second The Lady of Shalott example bugzilla@wiggum.w3.org
- [Bug 9079] New: Mis-use of <h2> in The Lady of Shalott examples bugzilla@wiggum.w3.org
- [Bug 9078] New: "only the first verse is included in this snippet" inaccurate bugzilla@wiggum.w3.org
- [Bug 9077] New: Lady of Shalott example doesn't really "enhance the themes or subject matter of the page content" bugzilla@wiggum.w3.org
- [Bug 8731] Consider expanding buffering control for media elements bugzilla@wiggum.w3.org
Thursday, 18 February 2010
- [Bug 8727] registration procedure for meta/@name values bugzilla@wiggum.w3.org
- [Bug 9057] status section, ref to "HTML specifications" bugzilla@wiggum.w3.org
- [Bug 9049] What is the correct behavior if a <meta http-equiv="Content-Type"> conflicts with <meta charset>? bugzilla@wiggum.w3.org
- [Bug 9055] There is no direct replacement for a frameset. This supports some functionality and features that can't be emulated 100% by other methods. Server side includes cannot dynamically udpate pages, nor can new pages be loaded with javascript. This is a crit bugzilla@wiggum.w3.org
- [Bug 9054] There is no direct replacement for a frameset. This supports some functionality and features that can't be emulated 100% by other methods. bugzilla@wiggum.w3.org
- [Bug 9074] Ogg Theora and Vorbis should be set as standard. bugzilla@wiggum.w3.org
- [Bug 8731] Consider expanding buffering control for media elements bugzilla@wiggum.w3.org
- [Bug 9074] New: Ogg Theora and Vorbis should be set as standard. bugzilla@wiggum.w3.org
- [Bug 8835] Clarifcation of the purpose of "Markup" spec and possible renaming of it. bugzilla@wiggum.w3.org
- [Bug 8835] Clarifcation of the purpose of "Markup" spec and possible renaming of it. bugzilla@wiggum.w3.org
- [Bug 8946] H:TML title is confusing bugzilla@wiggum.w3.org
- [Bug 8871] Empty attribute syntax definition seems incorrect. bugzilla@wiggum.w3.org
- [Bug 9073] New: "Configuring o form"? [pt] bugzilla@wiggum.w3.org
- [Bug 6506] should h:tml draft include descriptions of element-specific APIs? bugzilla@wiggum.w3.org
- [Bug 6503] to what degree should formalisms be used (if at all) in the h:tml draft? bugzilla@wiggum.w3.org
- [Bug 6502] should the canvas element be omitted from h:tml draft? bugzilla@wiggum.w3.org
- [Bug 9072] New: There's inconsistent quoting of attributes between the highlighted and non-highlited parts of this section 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 9071] New: Handling of "[" in between-doctype-public-and-system-identifiers-state may not be ideal bugzilla@wiggum.w3.org
- [Bug 6501] should obsolete elements be omitted from h:tml draft? bugzilla@wiggum.w3.org
- [Bug 9068] New: Windows-31J preferred name is with the "W" uppercase, not as given in the overrides where it is lowercase. (w00t! consistency!) bugzilla@wiggum.w3.org
- [Bug 9066] New: You state "many users disable scripting"... the most reliable stats I can find indicate that at most 1-2% of users have JS diabled. So using "many" is rather misleading. bugzilla@wiggum.w3.org
- [Bug 7744] Is sniffing required? bugzilla@wiggum.w3.org
- [Bug 8731] Consider expanding buffering control for media elements bugzilla@wiggum.w3.org
- [Bug 9053] Should the "name=size" attributes in the "Pizza Size" radio buttons also be included in the <strong> markup which immediately follows them? bugzilla@wiggum.w3.org
- [Bug 8806] iframe srcdoc examples bugzilla@wiggum.w3.org
- [Bug 9061] New: allow image maps on the canvas element. bugzilla@wiggum.w3.org
- [Bug 7616] Move requirement about obsolete doctypes bugzilla@wiggum.w3.org
- [Bug 9016] Make parameters on applet use the same rules as object (except for codebase="") bugzilla@wiggum.w3.org
- [Bug 9060] New: Add "in" into: "the user agent must act as if the element was" ...in... "a stack of open elements." bugzilla@wiggum.w3.org
- [Bug 9037] can we explain what getAttribute and and getAttributeNode do? bugzilla@wiggum.w3.org
- [Bug 9038] can we explain what getAttribute and and getAttributeNode do? bugzilla@wiggum.w3.org
- [Bug 9016] Make parameters on applet use the same rules as object (except for codebase="") bugzilla@wiggum.w3.org
- [Bug 9015] Opera now sends PARAM:"" to the plugin for compat with mozilla bugzilla@wiggum.w3.org
- [Bug 9015] Opera now sends PARAM:"" to the plugin for compat with mozilla bugzilla@wiggum.w3.org
- [Bug 9014] should probably wait with instantiating a plugin until the end tag has been parsed, otherwise the <param>s might not have been parsed yet bugzilla@wiggum.w3.org
- [Bug 9014] should probably wait with instantiating a plugin until the end tag has been parsed, otherwise the <param>s might not have been parsed yet bugzilla@wiggum.w3.org
- [Bug 9052] All DOCTYPE variants that trigger standards mode pre-HTML5 should continue to trigger standards mode in HTML5 bugzilla@wiggum.w3.org
- [Bug 8722] focus behaviour should be same for canvas regions as for elements bugzilla@wiggum.w3.org
- [Bug 8953] URL decomp. IDL attributes when parsing fails bugzilla@wiggum.w3.org
- [Bug 8953] URL decomp. IDL attributes when parsing fails bugzilla@wiggum.w3.org
- [Bug 8953] URL decomp. IDL attributes when parsing fails bugzilla@wiggum.w3.org
- [Bug 9052] All DOCTYPE variants that trigger standards mode pre-HTML5 should continue to trigger standards mode in HTML5 bugzilla@wiggum.w3.org
- [Bug 8818] Remove the srcdoc attribute bugzilla@wiggum.w3.org
- [Bug 8953] URL decomp. IDL attributes when parsing fails bugzilla@wiggum.w3.org
- [Bug 8953] URL decomp. IDL attributes when parsing fails bugzilla@wiggum.w3.org
- [Bug 8953] URL decomp. IDL attributes when parsing fails bugzilla@wiggum.w3.org
- [Bug 8953] URL decomp. IDL attributes when parsing fails bugzilla@wiggum.w3.org
- [Bug 8953] URL decomp. IDL attributes when parsing fails bugzilla@wiggum.w3.org
- [Bug 8953] URL decomp. IDL attributes when parsing fails bugzilla@wiggum.w3.org
- [Bug 9013] "Empty attribute syntax" doesn't actually say that the value is the empty string. bugzilla@wiggum.w3.org
- [Bug 8953] URL decomp. IDL attributes when parsing fails bugzilla@wiggum.w3.org
- [Bug 9013] "Empty attribute syntax" doesn't actually say that the value is the empty string. bugzilla@wiggum.w3.org
- [Bug 8966] Consider "<svg><desc><div><svg><desc><b>X" — Should we change "Pop elements from the stack of open elements until the current node is in the HTML namespace." in the in-foreign-content mode to actually be "Pop elements until there's no element in scope t bugzilla@wiggum.w3.org
- [Bug 9002] @sandbox should not allow content with text/html MIME type to force authors to change type to secure one. bugzilla@wiggum.w3.org
- [Bug 9000] datasrc, <script event>, <script for> and so on are missing bugzilla@wiggum.w3.org
- [Bug 9000] datasrc, <script event>, <script for> and so on are missing bugzilla@wiggum.w3.org
- [Bug 8953] URL decomp. IDL attributes when parsing fails bugzilla@wiggum.w3.org
- [Bug 8784] politics in <param> example bugzilla@wiggum.w3.org
- [Bug 8920] "sandboxed into a unique origin" means in an iframe with the seamless attribute? Are there other cases? bugzilla@wiggum.w3.org
- [Bug 8920] "sandboxed into a unique origin" means in an iframe with the seamless attribute? Are there other cases? bugzilla@wiggum.w3.org
- [Bug 8806] iframe srcdoc examples bugzilla@wiggum.w3.org
- [Bug 8999] Change the .cookie API to be based on the actual Origin of the document (vs its URL) and not on the sandboxed origin flag, so that text/html-sandboxed is handled as well. (But beware that data: URLs still have to fail silent, not throw SECURITY_ERR.) bugzilla@wiggum.w3.org
- [Bug 8999] Change the .cookie API to be based on the actual Origin of the document (vs its URL) and not on the sandboxed origin flag, so that text/html-sandboxed is handled as well. (But beware that data: URLs still have to fail silent, not throw SECURITY_ERR.) bugzilla@wiggum.w3.org
- [Bug 8953] URL decomp. IDL attributes when parsing fails bugzilla@wiggum.w3.org
- [Bug 8953] URL decomp. IDL attributes when parsing fails bugzilla@wiggum.w3.org
- [Bug 8798] It seems Opera and Firefox now have coordinate (0,0) at the content edge instead of the border edge (and allow negative coordinates if clicking on the border). Consider revising this requirement to match Opera and Firefox. (Haven't tested IE.) [sp] bugzilla@wiggum.w3.org
- [Bug 8917] This could use an introduction. What does "resource metadata management" mean? bugzilla@wiggum.w3.org
- [Bug 8798] It seems Opera and Firefox now have coordinate (0,0) at the content edge instead of the border edge (and allow negative coordinates if clicking on the border). Consider revising this requirement to match Opera and Firefox. (Haven't tested IE.) [sp] bugzilla@wiggum.w3.org
- [Bug 8822] should make cookie setting dependent on whether the document has a URL, not on whether it has a browsing context; and should fail silently (set does nothing, get returns "") when there isn't one. bugzilla@wiggum.w3.org
- [Bug 8822] should make cookie setting dependent on whether the document has a URL, not on whether it has a browsing context; and should fail silently (set does nothing, get returns "") when there isn't one. bugzilla@wiggum.w3.org
- [Bug 8731] Consider expanding buffering control for media elements bugzilla@wiggum.w3.org
- [Bug 9001] Consistent "Status" sections for Microdata and RDFa bugzilla@wiggum.w3.org
- [Bug 8855] tel URI reference bugzilla@wiggum.w3.org
- [Bug 8855] tel URI reference bugzilla@wiggum.w3.org
- [Bug 8731] Consider expanding buffering control for media elements bugzilla@wiggum.w3.org
- [Bug 8731] Consider expanding buffering control for media elements bugzilla@wiggum.w3.org
- [Bug 8731] Consider expanding buffering control for media elements bugzilla@wiggum.w3.org
- [Bug 8934] The Atom specification example could be rewritten as: "For example, the Atom specification defines a content element. When its type element has the value xhtml, the specification requires that it contain a single HTML div element. Thus ..." bugzilla@wiggum.w3.org
- [Bug 8934] The Atom specification example could be rewritten as: "For example, the Atom specification defines a content element. When its type element has the value xhtml, the specification requires that it contain a single HTML div element. Thus ..." bugzilla@wiggum.w3.org
- [Bug 8974] Check why the last sentence of "script's URL character encoding" is an xref error (same with the next <dd> too). bugzilla@wiggum.w3.org
- [Bug 8973] Make sure "script's browsing context" is not used to define an origin, since browsing contexts don't have origins. It has to be the script's browsing context's active document. bugzilla@wiggum.w3.org
- [Bug 8974] Check why the last sentence of "script's URL character encoding" is an xref error (same with the next <dd> too). bugzilla@wiggum.w3.org
- [Bug 8973] Make sure "script's browsing context" is not used to define an origin, since browsing contexts don't have origins. It has to be the script's browsing context's active document. bugzilla@wiggum.w3.org
- [Bug 8972] Would a <figcaption> that is the last element of a <figure> be a candidate for this list? The validator doesn't think so, but I it would be convenient. bugzilla@wiggum.w3.org
- [Bug 8837] Initial about:blank should fire DOMFrameContentLoaded and load events when not navigated immediately bugzilla@wiggum.w3.org
- [Bug 8837] Initial about:blank should fire DOMFrameContentLoaded and load events when not navigated immediately bugzilla@wiggum.w3.org
- [Bug 8837] Initial about:blank should fire DOMFrameContentLoaded and load events when not navigated immediately bugzilla@wiggum.w3.org
- [Bug 9059] New: can I use wildcards to cache the whole directory? bugzilla@wiggum.w3.org
- [Bug 8971] Keygen example <form> has type in enctype - should be "multipart/form-data", not "multipart/formdata". bugzilla@wiggum.w3.org
- [Bug 8971] Keygen example <form> has type in enctype - should be "multipart/form-data", not "multipart/formdata". bugzilla@wiggum.w3.org
- [Bug 8970] Should "Empty the Document's Window's list of active timeouts and its list of active intervals." actually happen if the document is to be salvaged? bugzilla@wiggum.w3.org
- [Bug 8970] Should "Empty the Document's Window's list of active timeouts and its list of active intervals." actually happen if the document is to be salvaged? bugzilla@wiggum.w3.org
- [Bug 8969] "If the entry in the list of active timeouts that was added in the earlier step has been cleared, then abort this algorithm" should be done in the task that is queued, not before the task is queued. Same for setInterval(). bugzilla@wiggum.w3.org
- [Bug 8969] "If the entry in the list of active timeouts that was added in the earlier step has been cleared, then abort this algorithm" should be done in the task that is queued, not before the task is queued. Same for setInterval(). bugzilla@wiggum.w3.org
- [Bug 8784] politics in <param> example bugzilla@wiggum.w3.org
- [Bug 8784] politics in <param> example bugzilla@wiggum.w3.org
Wednesday, 17 February 2010
- [Bug 8600] include header and footer when printing bugzilla@wiggum.w3.org
- [Bug 8968] typo: "comparedi" should, I presume, be "compared". bugzilla@wiggum.w3.org
- [Bug 8968] typo: "comparedi" should, I presume, be "compared". bugzilla@wiggum.w3.org
- [Bug 8806] iframe srcdoc examples 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 8767] <svg><font>x</font>y</svg>z is not parsed as intended. the in body insertion mode processes </font> as HTML formatting element, not as a foreign element's tag. bugzilla@wiggum.w3.org
- [Bug 9058] there is not CURIE or PREFIX? bugzilla@wiggum.w3.org
- [Bug 9058] New: there is not CURIE or PREFIX? bugzilla@wiggum.w3.org
- [Bug 8238] Add support for X3D bugzilla@wiggum.w3.org
- [Bug 8964] is INDEX_SIZE_ERR fired if value is less than zero also? bugzilla@wiggum.w3.org
- [Bug 8958] The constraint on "low" and "high" should be expressed as the others: "low ≤ high (if low and high are both specified)" bugzilla@wiggum.w3.org
- [Bug 8958] The constraint on "low" and "high" should be expressed as the others: "low ≤ high (if low and high are both specified)" bugzilla@wiggum.w3.org
- [Bug 8959] Shouldn't the headers in the second example's comments be footers? "A footer typically contains information about its section such as who wrote it" makes it confusing. bugzilla@wiggum.w3.org
- [Bug 8959] Shouldn't the headers in the second example's comments be footers? "A footer typically contains information about its section such as who wrote it" makes it confusing. bugzilla@wiggum.w3.org
- [Bug 8957] comments about HTTP requirements on redirects bugzilla@wiggum.w3.org
- [Bug 8955] "were the only form with a validity constraint problem" should be the only form _control_. bugzilla@wiggum.w3.org
- [Bug 8749] Conveying the hierarchy or relationship between the links to AT bugzilla@wiggum.w3.org
- [Bug 8748] Differentiating hyperlinks referring to the same tag in different scopes bugzilla@wiggum.w3.org
- [Bug 8746] Text separator between links in markup example bugzilla@wiggum.w3.org
- [Bug 8953] URL decomp. IDL attributes when parsing fails bugzilla@wiggum.w3.org
- [Bug 8742] User informed when URI can#t be resolved bugzilla@wiggum.w3.org
- [Bug 8739] Link element with active pseudo-class bugzilla@wiggum.w3.org
- [Bug 8715] Scrolling elements into view bugzilla@wiggum.w3.org
- [Bug 8737] Allowing option with no value to be a command bugzilla@wiggum.w3.org
- [Bug 8646] Private communication exception bugzilla@wiggum.w3.org
- [Bug 8953] URL decomp. IDL attributes when parsing fails bugzilla@wiggum.w3.org
- [Bug 9057] New: status section, ref to "HTML specifications" bugzilla@wiggum.w3.org
- [Bug 8953] URL decomp. IDL attributes when parsing fails bugzilla@wiggum.w3.org
- [Bug 7744] Is sniffing required? bugzilla@wiggum.w3.org
- [Bug 7744] Is sniffing required? bugzilla@wiggum.w3.org
- [Bug 6630] Optionalness of start tags when element is empty bugzilla@wiggum.w3.org
- [Bug 7616] Move requirement about obsolete doctypes bugzilla@wiggum.w3.org
- [Bug 6630] Optionalness of start tags when element is empty bugzilla@wiggum.w3.org
- [Bug 8951] "When the labeled control is not being rendered, then the label element's activation behavior must be to do nothing." - doesn't match opera/webkit/firefox: http://software.hixie.ch/utilities/js/live-dom-viewer/saved/371 . (Regarding focus management, visi bugzilla@wiggum.w3.org
- [Bug 8951] "When the labeled control is not being rendered, then the label element's activation behavior must be to do nothing." - doesn't match opera/webkit/firefox: http://software.hixie.ch/utilities/js/live-dom-viewer/saved/371 . (Regarding focus management, visi bugzilla@wiggum.w3.org
- [Bug 9055] New: There is no direct replacement for a frameset. This supports some functionality and features that can't be emulated 100% by other methods. Server side includes cannot dynamically udpate pages, nor can new pages be loaded with javascript. This is a crit bugzilla@wiggum.w3.org
- [Bug 9054] New: There is no direct replacement for a frameset. This supports some functionality and features that can't be emulated 100% by other methods. bugzilla@wiggum.w3.org
- [Bug 8722] focus behaviour should be same for canvas regions as for elements bugzilla@wiggum.w3.org
- [Bug 9053] Should the "name=size" attributes in the "Pizza Size" radio buttons also be included in the <strong> markup which immediately follows them? bugzilla@wiggum.w3.org
- [Bug 9053] New: Should the "name=size" attributes in the "Pizza Size" radio buttons also be included in the <strong> markup which immediately follows them? bugzilla@wiggum.w3.org
- [Bug 8828] definition of "plugin" bugzilla@wiggum.w3.org
- [Bug 9052] All DOCTYPE variants that trigger standards mode pre-HTML5 should continue to trigger standards mode in HTML5 bugzilla@wiggum.w3.org
- [Bug 9052] New: All DOCTYPE variants that trigger standards mode pre-HTML5 should continue to trigger standards mode in HTML5 bugzilla@wiggum.w3.org
- [Bug 9051] New: feed autodiscovery for main feed on posts bugzilla@wiggum.w3.org
- [Bug 8722] focus behaviour should be same for canvas regions as for elements bugzilla@wiggum.w3.org
- [Bug 8722] focus behaviour should be same for canvas regions as for elements bugzilla@wiggum.w3.org
- [Bug 8722] focus behaviour should be same for canvas regions as for elements bugzilla@wiggum.w3.org
- [Bug 7896] Specify pageshow and pagehide events bugzilla@wiggum.w3.org
- [Bug 9049] New: What is the correct behavior if a <meta http-equiv="Content-Type"> conflicts with <meta charset>? bugzilla@wiggum.w3.org
- [Bug 9048] New: "If either name, http-equiv, or itemprop is specified, then the content attribute must also be specified. Otherwise, it must be omitted." Might be more clearly stated as "If charset is specified, then the content attribute must be omitted. Otherwise it mu bugzilla@wiggum.w3.org
- [Bug 9047] New: Should UAs print a page in a <link media=print> if no stylesheet with media=print is provided? bugzilla@wiggum.w3.org
- [Bug 9046] New: What, if anything, are UAs allowed to do with the advisory "type" attribute of <link>? bugzilla@wiggum.w3.org
- [Bug 9045] New: The term "valid URL" is used here, but following the link does not lead to a definition bugzilla@wiggum.w3.org
- [Bug 9044] New: The context of <base> is "In a head element containing no other base elements" -- there are additional restrictions specified below that are not reflected here bugzilla@wiggum.w3.org
- [Bug 9043] New: Must the href attribute of <base> be a full URL, including http://...; if so, what is the correct terminology for that? I tried following the "valid URL" link and it goes down a rabbit hole to http://www.w3.org/html/wg/href/draft, which does not define "v bugzilla@wiggum.w3.org
- [Bug 8325] Please remove requirements that errors "must be reported to the user" and "should be reported to the user" throughout; "may be reported to the user" is appropriate. [sp] bugzilla@wiggum.w3.org
- [Bug 8325] Please remove requirements that errors "must be reported to the user" and "should be reported to the user" throughout; "may be reported to the user" is appropriate. [sp] bugzilla@wiggum.w3.org
- [Bug 9042] New: In neither section 4.2.1 or 4.8.2 is the reason for leaving out the title in an iframe srcdoc clarified. Is this because it's inherited from the parent? Because it's irrelevant? What does document.title return in this case? bugzilla@wiggum.w3.org
- [Bug 8950] Apparently the codebase attribute on object should not be passed to the plugin. (This does not apply to embed or applet.) [sp] bugzilla@wiggum.w3.org
- [Bug 9041] New: Is it worth mentioning that while there's no DOM API for the "manifest" attribute itself, there is an API for the cache manifest? bugzilla@wiggum.w3.org
- [Bug 9040] New: "Wherever a subdocument fragment is allowed in a compound document" -- What's an example of this? bugzilla@wiggum.w3.org
- [Bug 9039] New: Can we explain what getElementsByTagName does (and specifically, that it returns a NodeList)? bugzilla@wiggum.w3.org
- [Bug 9038] New: can we explain what getAttribute and and getAttributeNode do? bugzilla@wiggum.w3.org
- [Bug 9037] New: can we explain what getAttribute and and getAttributeNode do? bugzilla@wiggum.w3.org
- [Bug 9036] New: Can we explain what setAttribute and setAttributeNode actually do? bugzilla@wiggum.w3.org
- [Bug 8936] A summary table of the types of content and what elements belong to each would be helpful bugzilla@wiggum.w3.org
- [Bug 8949] The exact behavior for links to external resources depends on the exact relationship, as defined for the relevant link type. Some of the attributes control whether or not the external resource is to be applied (as defined below). For external resources th bugzilla@wiggum.w3.org
- [Bug 8948] text/richtext is obsolete; it is inappropriate as an example bugzilla@wiggum.w3.org
- [Bug 8948] text/richtext is obsolete; it is inappropriate as an example bugzilla@wiggum.w3.org
- [Bug 8948] text/richtext is obsolete; it is inappropriate as an example bugzilla@wiggum.w3.org
- [Bug 8926] How does an author *get* an object implementing DOMHTMLImplementation? bugzilla@wiggum.w3.org
- [Bug 8926] How does an author *get* an object implementing DOMHTMLImplementation? bugzilla@wiggum.w3.org
- [Bug 8945] Missing <del> in the interfaces index (Thanks Mike) bugzilla@wiggum.w3.org
- [Bug 8945] Missing <del> in the interfaces index (Thanks Mike) bugzilla@wiggum.w3.org
- [Bug 8936] A summary table of the types of content and what elements belong to each would be helpful bugzilla@wiggum.w3.org
- [Bug 8944] "Where metadata content is expected" -- Where is that defined? bugzilla@wiggum.w3.org
- [Bug 9035] New: Interfaces for URL manipulation: concept of "hierarchical" bugzilla@wiggum.w3.org
- [Bug 8943] "Each browsing context, including nested browsing context, has a distinct session history." is missing an "s" in the middle clause. (Thanks DanC.) bugzilla@wiggum.w3.org
- [Bug 8942] "Only the newest application cache in an application cache group can have its completeness flag set to incomplete, the others are always all complete." s/,/;/ (thanks DanC) bugzilla@wiggum.w3.org
- [Bug 8941] "Wherever a subdocument fragment is allowed in a compound document" -- what cases are these exactly? bugzilla@wiggum.w3.org
- [Bug 8938] We should explicitly say that using document.write after a document has been fully parsed results in the document being replaced. It's currently implicit in "calls the open() method implicitly first" but it would be nice to be clearer bugzilla@wiggum.w3.org
- [Bug 8938] We should explicitly say that using document.write after a document has been fully parsed results in the document being replaced. It's currently implicit in "calls the open() method implicitly first" but it would be nice to be clearer bugzilla@wiggum.w3.org
- [Bug 8937] setAttribute should specify the parameters (at least how many, but probably also a short description of each) bugzilla@wiggum.w3.org
- [Bug 8936] A summary table of the types of content and what elements belong to each would be helpful bugzilla@wiggum.w3.org
- [Bug 9034] New: Is there any "white-space avoiding rule"? If not, Some HTML Editor may insert evil-poorlooked white-space. bugzilla@wiggum.w3.org
- [Bug 8933] Add a forms intro section that walks the user through creating a form, and discusses what would be submitted, and how to do client-side form validation. bugzilla@wiggum.w3.org
- [Bug 8933] Add a forms intro section that walks the user through creating a form, and discusses what would be submitted, and how to do client-side form validation. bugzilla@wiggum.w3.org
- [Bug 8933] Add a forms intro section that walks the user through creating a form, and discusses what would be submitted, and how to do client-side form validation. 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 9010] There are one or more alternate methods of adding data without using RDFa, such as [microdata]. 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 9010] There are one or more alternate methods of adding data without using RDFa, such as [microdata]. 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 9010] There are one or more alternate methods of adding data without using RDFa, such as [microdata]. bugzilla@wiggum.w3.org
Tuesday, 16 February 2010
- [Bug 9010] There are one or more alternate methods of adding data without using RDFa, such as [microdata]. 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 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 9033] New: In the green box, please clarify that event.state contains a clone of the object passed to pushState bugzilla@wiggum.w3.org
- [Bug 7260] Create testsuite for table headers association bugzilla@wiggum.w3.org
- [Bug 8449] Remove extraneous material from Table section bugzilla@wiggum.w3.org
- [Bug 6462] Self-reference and cyclic references in headers='' bugzilla@wiggum.w3.org
- [Bug 6181] Process table feedback (including headers='" issue) bugzilla@wiggum.w3.org
- [Bug 5823] Scope allowable on a td bugzilla@wiggum.w3.org
- [Bug 5822] The headers attribute should be able to reference a td bugzilla@wiggum.w3.org
- [Bug 8747] Defining how a license applies to elements bugzilla@wiggum.w3.org
- [Bug 8752] Allow user to manage focus changes bugzilla@wiggum.w3.org
- [Bug 8723] image map is underspecified bugzilla@wiggum.w3.org
- [Bug 8738] Role-based navigation bugzilla@wiggum.w3.org
- [Bug 8717] Usability and Element-level-focus-apis bugzilla@wiggum.w3.org
- [Bug 8682] Tab and reading order for context menus bugzilla@wiggum.w3.org
- [Bug 8622] Activation behaviour and pre-click activation bugzilla@wiggum.w3.org
- [Bug 8666] Keyboard accessible date pickers bugzilla@wiggum.w3.org
- [Bug 8647] Define tab order for IFrame bugzilla@wiggum.w3.org
- [Bug 8648] Title attribute on the IFrame element bugzilla@wiggum.w3.org
- [Bug 8671] Requiring the label attribute bugzilla@wiggum.w3.org
- [Bug 8554] <progress> element should be labelable with a label bugzilla@wiggum.w3.org
- [Bug 8750] User able to override the hidden attribute in incorrectly rendered pages bugzilla@wiggum.w3.org
- [Bug 8754] Overflow when text is resized bugzilla@wiggum.w3.org
- [Bug 8751] User should have ability to override automatic scrolling bugzilla@wiggum.w3.org
- [Bug 8657] Allow UA to reload fallback content if it fails to load bugzilla@wiggum.w3.org
- [Bug 8652] what to display when images are not available is not well specified bugzilla@wiggum.w3.org
- [Bug 8743] Auditory icons clashing with AT bugzilla@wiggum.w3.org
- [Bug 8673] Restriction on command element as part of a menu bugzilla@wiggum.w3.org
- [Bug 8144] Is a 'visibility: hidden' element being rendered? bugzilla@wiggum.w3.org
- [Bug 8740] How do pseudo-class selectors interact with WAI-ARIA? bugzilla@wiggum.w3.org
- [Bug 8698] add conformance criteria info to header/banner bugzilla@wiggum.w3.org
- [Bug 8701] modify main role conformance info bugzilla@wiggum.w3.org
- [Bug 8000] ARIA roles added to the a element should be conforming in HTML5 bugzilla@wiggum.w3.org
- [Bug 8700] modify contentinfo mapping and conformance bugzilla@wiggum.w3.org
- [Bug 8753] Undo for drag and drop 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 8722] focus behaviour should be same for canvas regions as for elements bugzilla@wiggum.w3.org
- [Bug 7740] Authoring advice for canvas is bad for accessibility 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 7011] [in off-bug discussion] canvas accessible fallback provision is under specified bugzilla@wiggum.w3.org
- [Bug 8645] Alt text for images bugzilla@wiggum.w3.org
- [Bug 8524] Guidance for Authoring Tool Markup Generators bugzilla@wiggum.w3.org
- [Bug 8171] Implement the text alternatives proposal from WAI bugzilla@wiggum.w3.org
- [Bug 8644] Fallback mechanism for embedded content 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 8716] Replace img Guidance for Conformance Checkers with Suggested Text for Short Text Alternatives bugzilla@wiggum.w3.org
- [Bug 8660] Context for areas on an image map 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 6496] [blocked on aria] Allow <img aria-labelledby> to act as a caption bugzilla@wiggum.w3.org
- [Bug 6494] Make the requiredness about alt more obvious bugzilla@wiggum.w3.org
- [Bug 9030] Add more dfns (more helpful list coming) bugzilla@wiggum.w3.org
- [Bug 9030] New: Add more dfns (more helpful list coming) bugzilla@wiggum.w3.org
- [Bug 9029] New: Steps 2 and 3 should be in the relevant specifications, rather than inline bugzilla@wiggum.w3.org
- [Bug 9003] Tag should be closed bugzilla@wiggum.w3.org
- [Bug 9006] help on mnie gryzie bugzilla@wiggum.w3.org
- [Bug 9008] canvas is sick bugzilla@wiggum.w3.org
- [Bug 9003] Tag should be closed bugzilla@wiggum.w3.org
- [Bug 9004] Tag should be closed bugzilla@wiggum.w3.org
- [Bug 9028] New: "(either because of a fatal error during load that's about to be reported, or because the load() method was invoked while the resource selection algorithm was already running, in which case it is fired synchronously during the load() method call)." - empt bugzilla@wiggum.w3.org
- [Bug 9027] New: doubled "as possible" 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 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 9025] New: "the first five character removed" - should be "characters". [pt] bugzilla@wiggum.w3.org
- [Bug 9024] New: fetch should be referenced from algorithms in Web workers. bugzilla@wiggum.w3.org
- [Bug 9023] New: Dependency on Document does not work for Web Workers. bugzilla@wiggum.w3.org
- [Bug 9022] New: spec author names bugzilla@wiggum.w3.org
- [Bug 9021] New: perhaps mention here semantic alternatives to common use cases: <strike> → <del>, <tt> → <code>, &c. bugzilla@wiggum.w3.org
- [Bug 8727] registration procedure for meta/@name values bugzilla@wiggum.w3.org
- [Bug 9020] New: "When a control has a pattern attribute,": xref pattern bugzilla@wiggum.w3.org
- [Bug 8845] Reference for (US-)ASCII bugzilla@wiggum.w3.org
- [Bug 8845] Reference for (US-)ASCII bugzilla@wiggum.w3.org
- [Bug 8929] In the assistive technology section, explicitly mention role and aria-* (as we do a few lines above for "custom data attributes") bugzilla@wiggum.w3.org
- [Bug 9018] New: Should "origin" be marked up as "<i>origin</i>" just like the synchronous flag? bugzilla@wiggum.w3.org
- [Bug 9017] New: The origin argument should be used to determine whether Referer is to be omitted for XMLHttpRequest. I'm not a 100% sure at the moment when that would matter, but it seems safer. 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 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 9016] New: Make parameters on applet use the same rules as object (except for codebase="") bugzilla@wiggum.w3.org
- [Bug 9015] New: Opera now sends PARAM:"" to the plugin for compat with mozilla bugzilla@wiggum.w3.org
- [Bug 9014] New: should probably wait with instantiating a plugin until the end tag has been parsed, otherwise the <param>s might not have been parsed yet bugzilla@wiggum.w3.org
- [Bug 8932] "The attribute has no defaults" is inconsistent with "otherwise, the element's directionality is the same as its parent element, or 'ltr' if there is no parent element" bugzilla@wiggum.w3.org
- [Bug 8932] "The attribute has no defaults" is inconsistent with "otherwise, the element's directionality is the same as its parent element, or 'ltr' if there is no parent element" bugzilla@wiggum.w3.org
- [Bug 8931] The description for getting the lang from an ancestor is different from the description for getting the title, even though it appears they would behave identically. bugzilla@wiggum.w3.org
- [Bug 8930] In HTML, an element's "home subtree" is the set of descendants from the HTML node. Perhaps say that? bugzilla@wiggum.w3.org
- [Bug 8930] In HTML, an element's "home subtree" is the set of descendants from the HTML node. Perhaps say that? bugzilla@wiggum.w3.org
- [Bug 8929] In the assistive technology section, explicitly mention role and aria-* (as we do a few lines above for "custom data attributes") bugzilla@wiggum.w3.org
- [Bug 8929] In the assistive technology section, explicitly mention role and aria-* (as we do a few lines above for "custom data attributes") 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 8928] A listing of which events were fired on which elements, and at what times, would be extremely useful. For instance, the table in http://www.whatwg.org/specs/web-apps/current-work/multipage/section-index.html#events-0 claims that the volumechange event is bugzilla@wiggum.w3.org
- [Bug 8927] Instead of a list of on* elements, perhaps have a general-purpose event table we can use over and over? And then describe the actual events here? bugzilla@wiggum.w3.org
- [Bug 8925] Can we link NodeList here to the NodeList specification? bugzilla@wiggum.w3.org
- [Bug 8925] Can we link NodeList here to the NodeList specification? bugzilla@wiggum.w3.org
- [Bug 8923] The "document's character encoding" link does not go anywhere. bugzilla@wiggum.w3.org
- [Bug 8922] "Returns what might be the user agent's default character encoding" -- when might it not be? What are the caveats here? bugzilla@wiggum.w3.org
- [Bug 8922] "Returns what might be the user agent's default character encoding" -- when might it not be? What are the caveats here? bugzilla@wiggum.w3.org
- [Bug 8921] Is there a way to get the time zone of the server? bugzilla@wiggum.w3.org
- [Bug 8921] Is there a way to get the time zone of the server? bugzilla@wiggum.w3.org
- [Bug 9013] New: "Empty attribute syntax" doesn't actually say that the value is the empty string. bugzilla@wiggum.w3.org
- [Bug 8833] Please allow the title of the spec currently known as "HTML5" to be changed to an accurate title. bugzilla@wiggum.w3.org
- [Bug 8833] Please allow the title of the spec currently known as "HTML5" to be changed to an accurate title. 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 9012] New: 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 9011] New: There are discussions of alternate extensibility mechanisms, covered in [issue-41], which might allow other ways of integrating RDFa. 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 9010] New: There are one or more alternate methods of adding data without using RDFa, such as [microdata]. bugzilla@wiggum.w3.org
- [Bug 8997] Sections 6 and 7 are informative but appear to give normative requirements bugzilla@wiggum.w3.org
- [Bug 8996] Typo in DOM processing rules bugzilla@wiggum.w3.org
- [Bug 8995] DOM processing of xmlns: attributes should look at namespace URI, not namespace prefix bugzilla@wiggum.w3.org
- [Bug 8994] HTML+RDFa will process attributes in the XHML namespace as well as the null namespace; XHTML+RDFa does not bugzilla@wiggum.w3.org
- [Bug 8993] Spec says that mapping from DOM to tree-model is not necessary, but later gives such a mapping bugzilla@wiggum.w3.org
- [Bug 8992] Coercion to Infoset extensions mean that HTML document could produce different infosets in an HTML5 UA and an HTML+RDFa UA bugzilla@wiggum.w3.org
- [Bug 8991] Change to "coercion to infoset" rules is underdefined bugzilla@wiggum.w3.org
- [Bug 8990] Attributes starting with xmlns: are conforming even if illegal per Namespaces in XML bugzilla@wiggum.w3.org
- [Bug 8989] Allowance for attributes starting with xmlns: should be stated as a requirement on documents and conformance checkers, not on the HTML5 spec bugzilla@wiggum.w3.org
- [Bug 8988] Extensions to HTML5 syntax should be described as extensions, not modifications bugzilla@wiggum.w3.org
- [Bug 8987] Processing requirements for attributes starting with xmlns: are undefined bugzilla@wiggum.w3.org
- [Bug 8986] Link to "Section 5.4, CURIE and URI Processing" points to the wrong place bugzilla@wiggum.w3.org
- [Bug 8985] Inclear if requirement to ensure namespace well-formed fragments is separate from other transformation requirements bugzilla@wiggum.w3.org
- [Bug 8984] Invalid XMLLiteral definition of namesspace-well-formed XML fragments is too weak bugzilla@wiggum.w3.org
- [Bug 8983] Section 4.1 is unclear about language requirements bugzilla@wiggum.w3.org
- [Bug 8982] Unclear what features are required for user agents bugzilla@wiggum.w3.org
- [Bug 8981] Conforming documents are not required to use RDFa constructs in a conforming way bugzilla@wiggum.w3.org
- [Bug 8980] HTML+RDFa has should-/may-level requirements for undefined constructs bugzilla@wiggum.w3.org
- [Bug 8979] Please reconsider should-level requirement for version attribute bugzilla@wiggum.w3.org
- [Bug 8978] Document conformance requirements does not state that extensions to HTML5 syntax are allowed bugzilla@wiggum.w3.org
- [Bug 8977] Some conformance keywords are used prior to the Conformance Requirements section 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 9001] Consistent "Status" sections for Microdata and RDFa bugzilla@wiggum.w3.org
- [Bug 9008] New: canvas is sick bugzilla@wiggum.w3.org
- [Bug 8998] There is no requirement that the values of attributes starting with xmlns: conform to Namespaces in XML bugzilla@wiggum.w3.org
Monday, 15 February 2010
Sunday, 14 February 2010
- [Bug 9000] New: datasrc, <script event>, <script for> and so on are missing bugzilla@wiggum.w3.org
- [Bug 8920] "sandboxed into a unique origin" means in an iframe with the seamless attribute? Are there other cases? bugzilla@wiggum.w3.org
- [Bug 8999] New: Change the .cookie API to be based on the actual Origin of the document (vs its URL) and not on the sandboxed origin flag, so that text/html-sandboxed is handled as well. (But beware that data: URLs still have to fail silent, not throw SECURITY_ERR.) bugzilla@wiggum.w3.org
- [Bug 8919] Should be clearer that the setter actually appends, and not replaces bugzilla@wiggum.w3.org
- [Bug 8918] Are there other cases than coming from no referrer (just typing into the UA) and the noreferrer link that will result in a blank document.referrer? bugzilla@wiggum.w3.org
- [Bug 8918] Are there other cases than coming from no referrer (just typing into the UA) and the noreferrer link that will result in a blank document.referrer? bugzilla@wiggum.w3.org
- [Bug 8917] This could use an introduction. What does "resource metadata management" mean? bugzilla@wiggum.w3.org
- [Bug 8916] "effective script origin" links to "Relaxing the same-origin restriction" but the term is not used. At the very least, the linked-to section should say that .domain sets the "effective script origin" -- perhaps a reference to the same origin policy here w bugzilla@wiggum.w3.org
- [Bug 8916] "effective script origin" links to "Relaxing the same-origin restriction" but the term is not used. At the very least, the linked-to section should say that .domain sets the "effective script origin" -- perhaps a reference to the same origin policy here w bugzilla@wiggum.w3.org
- [Bug 8915] "the active document of the script's browsing context" -- is there more author-friendly terminology we can use here (in addition to the existing) bugzilla@wiggum.w3.org
- [Bug 8914] Are there cases other than the fragment id where the current address can change during the lifetime of a Document bugzilla@wiggum.w3.org
- [Bug 8914] Are there cases other than the fragment id where the current address can change during the lifetime of a Document bugzilla@wiggum.w3.org
- [Bug 8924] Custom attribute names in dataset bugzilla@wiggum.w3.org
- [Bug 8822] should make cookie setting dependent on whether the document has a URL, not on whether it has a browsing context; and should fail silently (set does nothing, get returns "") when there isn't one. bugzilla@wiggum.w3.org
- [Bug 8924] Custom attribute names in dataset bugzilla@wiggum.w3.org
- [Bug 8924] Custom attribute names in dataset bugzilla@wiggum.w3.org
- [Bug 8924] Custom attribute names in dataset bugzilla@wiggum.w3.org
- [Bug 8866] definition of "same-origin policy" bugzilla@wiggum.w3.org
- [Bug 8866] definition of "same-origin policy" bugzilla@wiggum.w3.org
- [Bug 8912] Why can't defer be used on inline scripts? If the script execution is slow (which can include loading of preceeding style sheets), the browser will have to wait until it can continue parsing and start downloading subsequent external resources. bugzilla@wiggum.w3.org
- [Bug 8906] terminology "URL" bugzilla@wiggum.w3.org
- [Bug 8736] Decision to playback for media should be left to the user agent bugzilla@wiggum.w3.org
- [Bug 8904] synchronous version of fetch algorithm bugzilla@wiggum.w3.org
- [Bug 8911] "Pause until" if implemented literally would lock the browser up since fetch tasks can't be processed while paused. bugzilla@wiggum.w3.org
- [Bug 8910] "If the user has requested the user of particular focus rings" -- should probably be "requested the use"? bugzilla@wiggum.w3.org
- [Bug 8906] terminology "URL" bugzilla@wiggum.w3.org
- [Bug 8910] "If the user has requested the user of particular focus rings" -- should probably be "requested the use"? bugzilla@wiggum.w3.org
- [Bug 8906] terminology "URL" bugzilla@wiggum.w3.org
- [Bug 8717] Usability and Element-level-focus-apis bugzilla@wiggum.w3.org
- [Bug 8905] will we be able to stream data from a device through a socket? bugzilla@wiggum.w3.org
- [Bug 8717] Usability and Element-level-focus-apis bugzilla@wiggum.w3.org
- [Bug 8902] Sentence 2 "When ..." is unclear to me.For instance, what does 'that' refer to? bugzilla@wiggum.w3.org
- [Bug 8903] Algorithm given is missing a final check to reject strings with trailing non-digits, like "123A", which the initial definition appears to exclude. bugzilla@wiggum.w3.org
- [Bug 8902] Sentence 2 "When ..." is unclear to me.For instance, what does 'that' refer to? bugzilla@wiggum.w3.org
- [Bug 8357] Possible Compromise solution for namespaces in HTML5 bugzilla@wiggum.w3.org
- [Bug 8720] define rendering for wbr [sp] bugzilla@wiggum.w3.org
- [Bug 8720] define rendering for wbr [sp] bugzilla@wiggum.w3.org
- [Bug 8720] define rendering for wbr [sp] bugzilla@wiggum.w3.org
- [Bug 8727] registration procedure for meta/@name values bugzilla@wiggum.w3.org
- [Bug 8899] it should define how to parse or compare mime types because http spec does not define it but html UAs have to know how to treat invalid input such as type="text/css; incomplete-parameter" 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 8898] please make title element optional if higher-level protocol provides similar information (e.g. as email Subject: header field) bugzilla@wiggum.w3.org
- [Bug 8898] please make title element optional if higher-level protocol provides similar information (e.g. as email Subject: header field) bugzilla@wiggum.w3.org
- [Bug 8885] Fallback mechanism for embedded content bugzilla@wiggum.w3.org
- [Bug 8856] url parameter in register*Handler bugzilla@wiggum.w3.org
- [Bug 8855] tel URI reference bugzilla@wiggum.w3.org
- [Bug 8845] Reference for (US-)ASCII bugzilla@wiggum.w3.org
- [Bug 8897] note: W3C markup validation tool (for HTML5 and not HTML 4.01) gives two errors in the case of height = width = 0 bugzilla@wiggum.w3.org
- [Bug 8710] option . text: c/p'd too much; also add a line in the IDL [ms] 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 8727] registration procedure for meta/@name values bugzilla@wiggum.w3.org
- [Bug 8889] Web application APIs link points to Loading Web pages bugzilla@wiggum.w3.org
- [Bug 8889] Web application APIs link points to Loading Web pages bugzilla@wiggum.w3.org
- [Bug 8888] maybe this should have id="loading-web-pages" instead of id="browsers" 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 8659] Media events to indicate captions and audio descriptions bugzilla@wiggum.w3.org
- [Bug 8878] "Otherwise, the user agent must must split the attribute's value on spaces, and let keys be the resulting tokens." - Double "must" at the second point. bugzilla@wiggum.w3.org
- [Bug 8659] Media events to indicate captions and audio descriptions bugzilla@wiggum.w3.org
- [Bug 8878] "Otherwise, the user agent must must split the attribute's value on spaces, and let keys be the resulting tokens." - Double "must" at the second point. bugzilla@wiggum.w3.org
- [Bug 8800] Cut/copy/paste should use dedicated events instead of overloading drag and drop 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 8827] Inappropriate spec text and advice where images are not known bugzilla@wiggum.w3.org
- [Bug 8869] Fetch algorithm should specify that no Referer is sent when the origin is a unique identifier bugzilla@wiggum.w3.org
- [Bug 8869] Fetch algorithm should specify that no Referer is sent when the origin is a unique identifier bugzilla@wiggum.w3.org
- [Bug 8868] content model should say "if the span attribute is specified: empty. otherwise: zero or more col elements." [sp] bugzilla@wiggum.w3.org
- [Bug 8868] content model should say "if the span attribute is specified: empty. otherwise: zero or more col elements." [sp] bugzilla@wiggum.w3.org
- [Bug 8828] definition of "plugin" bugzilla@wiggum.w3.org
- [Bug 8828] definition of "plugin" bugzilla@wiggum.w3.org
- [Bug 8731] Consider expanding buffering control for media elements bugzilla@wiggum.w3.org
- [Bug 8865] The order of the attributes need to be the same as the source order when passing as parameters to the plugin, apparently. [sp] bugzilla@wiggum.w3.org
- [Bug 8865] The order of the attributes need to be the same as the source order when passing as parameters to the plugin, apparently. [sp] bugzilla@wiggum.w3.org
- [Bug 8864] If there are two <param>s with the same name, the last one should be used, apparently. [sp] bugzilla@wiggum.w3.org
- [Bug 8863] I need a way of interrogating features drawn onto a canvas. I would like to use a canvas to represent layers/groups of features...which i control wholistically as well as interrogate individually. Think of a map for example....it has layers...where each l bugzilla@wiggum.w3.org
- [Bug 8857] references to openDatabase and localStorage bugzilla@wiggum.w3.org
- [Bug 8857] references to openDatabase and localStorage bugzilla@wiggum.w3.org
- [Bug 8833] Please allow the title of the spec currently known as "HTML5" to be changed to an accurate title. bugzilla@wiggum.w3.org
- [Bug 8731] Consider expanding buffering control for media elements bugzilla@wiggum.w3.org
- [Bug 8833] Please allow the title of the spec currently known as "HTML5" to be changed to an accurate title. bugzilla@wiggum.w3.org
- [Bug 8731] Consider expanding buffering control for media elements bugzilla@wiggum.w3.org
- [Bug 8883] insert number bugzilla@wiggum.w3.org
- [Bug 8880] line feed bugzilla@wiggum.w3.org
- [Bug 8934] The Atom specification example could be rewritten as: "For example, the Atom specification defines a content element. When its type element has the value xhtml, the specification requires that it contain a single HTML div element. Thus ..." bugzilla@wiggum.w3.org
- [Bug 8935] The Atom specification example could be rewritten as: "For example, the Atom specification defines a content element. When its type element has the value xhtml, the specification requires that it contain a single HTML div element. Thus ..." bugzilla@wiggum.w3.org
- [Bug 8954] browser support bugzilla@wiggum.w3.org
- [Bug 8956] what is this? bugzilla@wiggum.w3.org
- [Bug 8963] img url bugzilla@wiggum.w3.org
- [Bug 8975] trees are good bugzilla@wiggum.w3.org
- [Bug 8998] New: There is no requirement that the values of attributes starting with xmlns: conform to Namespaces in XML bugzilla@wiggum.w3.org
- [Bug 8997] New: Sections 6 and 7 are informative but appear to give normative requirements bugzilla@wiggum.w3.org
- [Bug 8996] New: Typo in DOM processing rules bugzilla@wiggum.w3.org
- [Bug 8995] New: DOM processing of xmlns: attributes should look at namespace URI, not namespace prefix bugzilla@wiggum.w3.org
- [Bug 8994] HTML+RDFa will process attributes in the XHML namespace as well as the null namespace; XHTML+RDFa does not bugzilla@wiggum.w3.org
- [Bug 8994] New: HTML+RDFa will process attributes in the XHML namespace as well as the null namespace; XHTML+RDFa does not bugzilla@wiggum.w3.org
- [Bug 8993] New: Spec says that mapping from DOM to tree-model is not necessary, but later gives such a mapping bugzilla@wiggum.w3.org
- [Bug 8992] New: Coercion to Infoset extensions mean that HTML document could produce different infosets in an HTML5 UA and an HTML+RDFa UA bugzilla@wiggum.w3.org
- [Bug 8991] New: Change to "coercion to infoset" rules is underdefined bugzilla@wiggum.w3.org
- [Bug 8990] New: Attributes starting with xmlns: are conforming even if illegal per Namespaces in XML bugzilla@wiggum.w3.org
- [Bug 8989] New: Allowance for attributes starting with xmlns: should be stated as a requirement on documents and conformance checkers, not on the HTML5 spec bugzilla@wiggum.w3.org
- [Bug 8988] New: Extensions to HTML5 syntax should be described as extensions, not modifications bugzilla@wiggum.w3.org
- [Bug 8987] New: Processing requirements for attributes starting with xmlns: are undefined bugzilla@wiggum.w3.org
- [Bug 8856] url parameter in register*Handler bugzilla@wiggum.w3.org
- [Bug 8856] url parameter in register*Handler bugzilla@wiggum.w3.org
- [Bug 8986] New: Link to "Section 5.4, CURIE and URI Processing" points to the wrong place bugzilla@wiggum.w3.org
- [Bug 8985] New: Inclear if requirement to ensure namespace well-formed fragments is separate from other transformation requirements bugzilla@wiggum.w3.org
- [Bug 8984] New: Invalid XMLLiteral definition of namesspace-well-formed XML fragments is too weak bugzilla@wiggum.w3.org
- [Bug 8855] tel URI reference bugzilla@wiggum.w3.org
- [Bug 8731] Consider expanding buffering control for media elements bugzilla@wiggum.w3.org
- [Bug 8849] The ability for an author to completely disable javascript on their webpage - an html scripts="no" attribute bugzilla@wiggum.w3.org
- [Bug 8983] New: Section 4.1 is unclear about language requirements bugzilla@wiggum.w3.org
- [Bug 8851] "vevent" example: "dtend" value and accompanying text inconsistent? (20 vs 19) bugzilla@wiggum.w3.org
- [Bug 8982] New: Unclear what features are required for user agents bugzilla@wiggum.w3.org
- [Bug 8851] "vevent" example: "dtend" value and accompanying text inconsistent? (20 vs 19) bugzilla@wiggum.w3.org
- [Bug 8981] New: Conforming documents are not required to use RDFa constructs in a conforming way bugzilla@wiggum.w3.org
- [Bug 8731] Consider expanding buffering control for media elements bugzilla@wiggum.w3.org
- [Bug 8980] New: HTML+RDFa has should-/may-level requirements for undefined constructs bugzilla@wiggum.w3.org
- [Bug 8979] New: Please reconsider should-level requirement for version attribute bugzilla@wiggum.w3.org
- [Bug 8978] New: Document conformance requirements does not state that extensions to HTML5 syntax are allowed bugzilla@wiggum.w3.org
- [Bug 8977] New: Some conformance keywords are used prior to the Conformance Requirements section bugzilla@wiggum.w3.org
- [Bug 8850] “himself” assumes all authors are male, which is incorrect (and misogynistic). “themself” is correct. bugzilla@wiggum.w3.org
- [Bug 8976] New: Modifying the Input Document section is labeled as informative but include normative requirements bugzilla@wiggum.w3.org
- [Bug 8975] New: trees are good bugzilla@wiggum.w3.org
- [Bug 8490] Shouldn't postMessage throw SYNTAX_ERR when targetOrigin is a relative URL (e.g. '/')? [sp] bugzilla@wiggum.w3.org
- [Bug 8490] Shouldn't postMessage throw SYNTAX_ERR when targetOrigin is a relative URL (e.g. '/')? [sp] bugzilla@wiggum.w3.org
- [Bug 8974] New: Check why the last sentence of "script's URL character encoding" is an xref error (same with the next <dd> too). bugzilla@wiggum.w3.org
- [Bug 8973] New: Make sure "script's browsing context" is not used to define an origin, since browsing contexts don't have origins. It has to be the script's browsing context's active document. bugzilla@wiggum.w3.org
- [Bug 8972] New: Would a <figcaption> that is the last element of a <figure> be a candidate for this list? The validator doesn't think so, but I it would be convenient. bugzilla@wiggum.w3.org
- [Bug 8807] If the "body" attribute no longer exists, "body" should be removed from the list of IDL attributes that reflect their respective content attributes of the same name bugzilla@wiggum.w3.org
- [Bug 8807] If the "body" attribute no longer exists, "body" should be removed from the list of IDL attributes that reflect their respective content attributes of the same name bugzilla@wiggum.w3.org
- [Bug 8847] srcdoc should be listed after src, not autoplay; in attributes overview table bugzilla@wiggum.w3.org
- [Bug 8847] srcdoc should be listed after src, not autoplay; in attributes overview table bugzilla@wiggum.w3.org
- [Bug 8834] Please remove the subtitle from the spec known as "HTML5" bugzilla@wiggum.w3.org
- [Bug 8845] Reference for (US-)ASCII bugzilla@wiggum.w3.org
- [Bug 8844] Since this section is shared with the XML parser should this be its own generic section rather than a subsection of the HTML parser? [avk] bugzilla@wiggum.w3.org
- [Bug 8843] Is <pre> element a phrasing content? An example of <figure> element shows a <pre> element in <figure> element. bugzilla@wiggum.w3.org
- [Bug 8842] id="dome" should be id="home" bugzilla@wiggum.w3.org
- [Bug 8843] Is <pre> element a phrasing content? An example of <figure> element shows a <pre> element in <figure> element. bugzilla@wiggum.w3.org
- [Bug 8842] id="dome" should be id="home" bugzilla@wiggum.w3.org
- [Bug 8841] Section 2.7.8 Exceptions: The DOMException codes with code number >= 18 do not appear in the referenced document [DOMCORE]. So it should be noted that these codes were introduced by HTML5 bugzilla@wiggum.w3.org
- [Bug 8837] Initial about:blank should fire DOMFrameContentLoaded and load events when not navigated immediately bugzilla@wiggum.w3.org
- [Bug 8818] Remove the srcdoc attribute bugzilla@wiggum.w3.org
- [Bug 8830] cut-n-paste error: in the "agent" paragraph you can read: "Any number of properties with the name _logo_ may...." -- Gianmarco Armellin bugzilla@wiggum.w3.org
- [Bug 8836] "The Selectors specification, in conjunction with CSS, can be used to style text selections using the ::selection pseudo-element.": Not anymore. [ms] bugzilla@wiggum.w3.org
- [Bug 8818] Remove the srcdoc attribute bugzilla@wiggum.w3.org
- [Bug 8836] "The Selectors specification, in conjunction with CSS, can be used to style text selections using the ::selection pseudo-element.": Not anymore. [ms] bugzilla@wiggum.w3.org
- [Bug 8731] Consider expanding buffering control for media elements bugzilla@wiggum.w3.org
- [Bug 8830] cut-n-paste error: in the "agent" paragraph you can read: "Any number of properties with the name _logo_ may...." -- Gianmarco Armellin bugzilla@wiggum.w3.org
- [Bug 8830] cut-n-paste error: in the "agent" paragraph you can read: "Any number of properties with the name _logo_ may...." -- Gianmarco Armellin bugzilla@wiggum.w3.org
- [Bug 8825] "begin to use the bytes provided for the document as the input stream for that parser" is way too vague -- it should relate to the parsing tasks mentioned in the event loop section ("one per byte" etc) bugzilla@wiggum.w3.org
- [Bug 8825] "begin to use the bytes provided for the document as the input stream for that parser" is way too vague -- it should relate to the parsing tasks mentioned in the event loop section ("one per byte" etc) bugzilla@wiggum.w3.org
- [Bug 8825] "begin to use the bytes provided for the document as the input stream for that parser" is way too vague -- it should relate to the parsing tasks mentioned in the event loop section ("one per byte" etc) bugzilla@wiggum.w3.org
- [Bug 8826] about:blank should use standards mode bugzilla@wiggum.w3.org
- [Bug 8822] should make cookie setting dependent on whether the document has a URL, not on whether it has a browsing context; and should fail silently (set does nothing, get returns "") when there isn't one. bugzilla@wiggum.w3.org
- [Bug 8971] New: Keygen example <form> has type in enctype - should be "multipart/form-data", not "multipart/formdata". bugzilla@wiggum.w3.org
- [Bug 8970] Should "Empty the Document's Window's list of active timeouts and its list of active intervals." actually happen if the document is to be salvaged? bugzilla@wiggum.w3.org
- [Bug 8821] discarding a doc that hasn't gone through the unload steps should run the steps that clear timeouts, databases, etc bugzilla@wiggum.w3.org
- [Bug 8821] discarding a doc that hasn't gone through the unload steps should run the steps that clear timeouts, databases, etc bugzilla@wiggum.w3.org
- [Bug 8821] discarding a doc that hasn't gone through the unload steps should run the steps that clear timeouts, databases, etc bugzilla@wiggum.w3.org
- [Bug 8970] New: Should "Empty the Document's Window's list of active timeouts and its list of active intervals." actually happen if the document is to be salvaged? bugzilla@wiggum.w3.org
- [Bug 8969] New: "If the entry in the list of active timeouts that was added in the earlier step has been cleared, then abort this algorithm" should be done in the task that is queued, not before the task is queued. Same for setInterval(). bugzilla@wiggum.w3.org
- [Bug 8784] politics in <param> example bugzilla@wiggum.w3.org
- [Bug 8818] Remove the srcdoc attribute bugzilla@wiggum.w3.org
- [Bug 8608] W3C Validator errors reported on HTML5 spec bugzilla@wiggum.w3.org
- [Bug 8606] ambiguous ampersand does not include character references bugzilla@wiggum.w3.org
- [Bug 8600] include header and footer when printing bugzilla@wiggum.w3.org
- [Bug 8600] include header when printing bugzilla@wiggum.w3.org
- [Bug 8601] include footer when printing bugzilla@wiggum.w3.org
- [Bug 8590] can empty string be a valid keyword? bugzilla@wiggum.w3.org
- [Bug 8968] New: typo: "comparedi" should, I presume, be "compared". bugzilla@wiggum.w3.org
- [Bug 8784] politics in <param> example bugzilla@wiggum.w3.org
Saturday, 13 February 2010
Friday, 12 February 2010
Thursday, 11 February 2010
Wednesday, 10 February 2010
- [Bug 8946] New: H:TML title is confusing bugzilla@wiggum.w3.org
- [Bug 8926] How does an author *get* an object implementing DOMHTMLImplementation? bugzilla@wiggum.w3.org
- [Bug 8945] Missing <del> in the interfaces index (Thanks Mike) bugzilla@wiggum.w3.org
- [Bug 8945] New: Missing <del> in the interfaces index (Thanks Mike) bugzilla@wiggum.w3.org
- [Bug 8944] "Where metadata content is expected" -- Where is that defined? bugzilla@wiggum.w3.org
- [Bug 8944] New: "Where metadata content is expected" -- Where is that defined? bugzilla@wiggum.w3.org
- [Bug 8943] New: "Each browsing context, including nested browsing context, has a distinct session history." is missing an "s" in the middle clause. (Thanks DanC.) bugzilla@wiggum.w3.org
- [Bug 8942] New: "Only the newest application cache in an application cache group can have its completeness flag set to incomplete, the others are always all complete." s/,/;/ (thanks DanC) bugzilla@wiggum.w3.org
- [Bug 8941] New: "Wherever a subdocument fragment is allowed in a compound document" -- what cases are these exactly? bugzilla@wiggum.w3.org
- [Bug 8940] New: so nice bugzilla@wiggum.w3.org
- [Bug 8939] New: so nice bugzilla@wiggum.w3.org
- [Bug 8938] New: We should explicitly say that using document.write after a document has been fully parsed results in the document being replaced. It's currently implicit in "calls the open() method implicitly first" but it would be nice to be clearer bugzilla@wiggum.w3.org
- [Bug 8937] New: setAttribute should specify the parameters (at least how many, but probably also a short description of each) bugzilla@wiggum.w3.org
- [Bug 8723] image map is underspecified bugzilla@wiggum.w3.org
- [Bug 8936] New: A summary table of the types of content and what elements belong to each would be helpful bugzilla@wiggum.w3.org
- [Bug 8935] New: The Atom specification example could be rewritten as: "For example, the Atom specification defines a content element. When its type element has the value xhtml, the specification requires that it contain a single HTML div element. Thus ..." bugzilla@wiggum.w3.org
- [Bug 8652] what to display when images are not available is not well specified bugzilla@wiggum.w3.org
- [Bug 8934] New: The Atom specification example could be rewritten as: "For example, the Atom specification defines a content element. When its type element has the value xhtml, the specification requires that it contain a single HTML div element. Thus ..." bugzilla@wiggum.w3.org
- [Bug 8933] New: Add a forms intro section that walks the user through creating a form, and discusses what would be submitted, and how to do client-side form validation. bugzilla@wiggum.w3.org
- [Bug 8932] New: "The attribute has no defaults" is inconsistent with "otherwise, the element's directionality is the same as its parent element, or 'ltr' if there is no parent element" bugzilla@wiggum.w3.org
- [Bug 8931] New: The description for getting the lang from an ancestor is different from the description for getting the title, even though it appears they would behave identically. bugzilla@wiggum.w3.org
- [Bug 8930] New: In HTML, an element's "home subtree" is the set of descendants from the HTML node. Perhaps say that? bugzilla@wiggum.w3.org
- [Bug 8929] New: In the assistive technology section, explicitly mention role and aria-* (as we do a few lines above for "custom data attributes") bugzilla@wiggum.w3.org
- [Bug 8928] New: A listing of which events were fired on which elements, and at what times, would be extremely useful. For instance, the table in http://www.whatwg.org/specs/web-apps/current-work/multipage/section-index.html#events-0 claims that the volumechange event is bugzilla@wiggum.w3.org
- [Bug 8927] New: Instead of a list of on* elements, perhaps have a general-purpose event table we can use over and over? And then describe the actual events here? bugzilla@wiggum.w3.org
- [Bug 8926] New: How does an author *get* an object implementing DOMHTMLImplementation? bugzilla@wiggum.w3.org
- [Bug 8925] New: Can we link NodeList here to the NodeList specification? bugzilla@wiggum.w3.org
- [Bug 8924] New: Custom attribute names in dataset bugzilla@wiggum.w3.org
- [Bug 8866] definition of "same-origin policy" bugzilla@wiggum.w3.org
- [Bug 8923] New: The "document's character encoding" link does not go anywhere. bugzilla@wiggum.w3.org
- [Bug 8922] New: "Returns what might be the user agent's default character encoding" -- when might it not be? What are the caveats here? bugzilla@wiggum.w3.org
- [Bug 8921] New: Is there a way to get the time zone of the server? bugzilla@wiggum.w3.org
- [Bug 8920] New: "sandboxed into a unique origin" means in an iframe with the seamless attribute? Are there other cases? bugzilla@wiggum.w3.org
- [Bug 8919] New: Should be clearer that the setter actually appends, and not replaces bugzilla@wiggum.w3.org
- [Bug 8918] New: Are there other cases than coming from no referrer (just typing into the UA) and the noreferrer link that will result in a blank document.referrer? bugzilla@wiggum.w3.org
- [Bug 8917] New: This could use an introduction. What does "resource metadata management" mean? bugzilla@wiggum.w3.org
- [Bug 8916] New: "effective script origin" links to "Relaxing the same-origin restriction" but the term is not used. At the very least, the linked-to section should say that .domain sets the "effective script origin" -- perhaps a reference to the same origin policy here w bugzilla@wiggum.w3.org
- [Bug 8915] New: "the active document of the script's browsing context" -- is there more author-friendly terminology we can use here (in addition to the existing) bugzilla@wiggum.w3.org
- [Bug 8904] synchronous version of fetch algorithm bugzilla@wiggum.w3.org
- [Bug 8914] New: Are there cases other than the fragment id where the current address can change during the lifetime of a Document bugzilla@wiggum.w3.org
- [Bug 8912] Why can't defer be used on inline scripts? If the script execution is slow (which can include loading of preceeding style sheets), the browser will have to wait until it can continue parsing and start downloading subsequent external resources. bugzilla@wiggum.w3.org
- [Bug 8912] New: Why can't defer be used on inline scripts? If the script execution is slow (which can include loading of preceeding style sheets), the browser will have to wait until it can continue parsing and start downloading subsequent external resources. bugzilla@wiggum.w3.org
Tuesday, 9 February 2010
Monday, 8 February 2010
Sunday, 7 February 2010
Saturday, 6 February 2010
- [Bug 8892] HTML5 editor should propose changes within email list bugzilla@wiggum.w3.org
- [Bug 8722] focus behaviour should be same for canvas regions as for elements bugzilla@wiggum.w3.org
- [Bug 7657] Redefining dt and dd bugzilla@wiggum.w3.org
- [Bug 7669] Redefining dt and dd, recommend new element as caption for Figure bugzilla@wiggum.w3.org
- [Bug 7669] Redefining dt and dd, recommend new element as caption for Figure bugzilla@wiggum.w3.org
- [Bug 8892] HTML5 editor should propose changes within email list bugzilla@wiggum.w3.org
- [Bug 8892] New: HTML5 editor should propose changes within email list bugzilla@wiggum.w3.org
- [Bug 8891] No change or so-called zero edit proposals bugzilla@wiggum.w3.org
- [Bug 8891] New: No change or so-called zero edit proposals bugzilla@wiggum.w3.org
- [Bug 8710] option . text: c/p'd too much; also add a line in the IDL [ms] bugzilla@wiggum.w3.org
- [Bug 8729] dataTransfer for dragenter and dragover can't really be Empty if the drop target is to actually determine whether it can accept the drag. In an ideal world, files would exist but only make the mime type of the file available. bugzilla@wiggum.w3.org
- [Bug 8727] registration procedure for meta/@name values bugzilla@wiggum.w3.org
- [Bug 8728] s/<code title="attr-font-style">style</code>/<code title="attr-style">style</code>/ [ms] bugzilla@wiggum.w3.org
- [Bug 8728] s/<code title="attr-font-style">style</code>/<code title="attr-style">style</code>/ [ms] bugzilla@wiggum.w3.org
- [Bug 8727] registration procedure for meta/@name values bugzilla@wiggum.w3.org
- [Bug 8726] the <figure/> element should be under 4.5 Grouping content and not here (4.8 Embedded content) bugzilla@wiggum.w3.org
- [Bug 8726] the <figure/> element should be under 4.5 Grouping content and not here (4.8 Embedded content) bugzilla@wiggum.w3.org
- [Bug 8723] image map is underspecified bugzilla@wiggum.w3.org
- [Bug 8722] focus behaviour should be same for canvas regions as for elements bugzilla@wiggum.w3.org
- [Bug 8721] Getting an error that the local database can't be found..And how is the privacy being handled? And should i be worried about security leaks? bugzilla@wiggum.w3.org
- [Bug 8720] define rendering for wbr [sp] bugzilla@wiggum.w3.org
- [Bug 7386] SharedWorkerGlobalScope bugzilla@wiggum.w3.org
- [Bug 8718] Typo in "and thus typically encodings" should say "and thus typical encodings" bugzilla@wiggum.w3.org
- [Bug 8718] Typo in "and thus typically encodings" should say "and thus typical encodings" bugzilla@wiggum.w3.org
- [Bug 8717] Usability and Element-level-focus-apis bugzilla@wiggum.w3.org
- [Bug 8715] Scrolling elements into view bugzilla@wiggum.w3.org
- [Bug 8889] New: Web application APIs link points to Loading Web pages bugzilla@wiggum.w3.org
- [Bug 8888] New: maybe this should have id="loading-web-pages" instead of id="browsers" bugzilla@wiggum.w3.org
- [Bug 8710] option . text: c/p'd too much; also add a line in the IDL [ms] bugzilla@wiggum.w3.org
- [Bug 8710] option . text: c/p'd too much; also add a line in the IDL [ms] bugzilla@wiggum.w3.org
- [Bug 8711] Conversion of blockquote and q elements to RDF (sec 5.5.2, step 4) states that the subject should be the document address, but it should be an identifier for the quote. bugzilla@wiggum.w3.org
- [Bug 8709] "If the current outlinee is null." ends in a full-stop, the rest of the list does not. bugzilla@wiggum.w3.org
- [Bug 8709] "If the current outlinee is null." ends in a full-stop, the rest of the list does not. bugzilla@wiggum.w3.org
- [Bug 8704] please disallow attributes for form submission unless the |type| attribute is in the Submit Button state bugzilla@wiggum.w3.org
- [Bug 8704] please disallow attributes for form submission unless the |type| attribute is in the Submit Button state bugzilla@wiggum.w3.org
- [Bug 8703] please disallow charset parameter in type="" (it is disallowed in script's type="") bugzilla@wiggum.w3.org
- [Bug 8703] please disallow charset parameter in type="" (it is disallowed in script's type="") bugzilla@wiggum.w3.org
- [Bug 8702] "Within a single dl element, there should not be more than one dt element for each name" - intention of this requirement is unclear; is this a machine-checkable requirement, or a requirement on semantics? What will be used to compare "name"s, textContent bugzilla@wiggum.w3.org
- [Bug 8436] "granularity that is expected (and required) of the value, by limiting the allowed values" -- granularity requirments may often be different for validation versus usability/ui-control purposes. There should be a 'step' for possible GUI controls and an oth bugzilla@wiggum.w3.org
- [Bug 8701] modify main role conformance info bugzilla@wiggum.w3.org
- [Bug 8701] modify main role conformance info bugzilla@wiggum.w3.org
- [Bug 8700] modify contentinfo mapping and conformance bugzilla@wiggum.w3.org
- [Bug 8700] modify contentinfo mapping and conformance bugzilla@wiggum.w3.org
- [Bug 8699] the second note is not always true: script.innerHTML = '<!--' does raise a parse error if the "script data" state is used but does not if the PLAINTEXT state is used bugzilla@wiggum.w3.org
- [Bug 8699] the second note is not always true: script.innerHTML = '<!--' does raise a parse error if the "script data" state is used but does not if the PLAINTEXT state is used bugzilla@wiggum.w3.org
- [Bug 8698] add conformance criteria info to header/banner bugzilla@wiggum.w3.org
- [Bug 8698] add conformance criteria info to header/banner bugzilla@wiggum.w3.org
- [Bug 8696] "close tag" -> "end tag" for consistency bugzilla@wiggum.w3.org
- [Bug 8696] "close tag" -> "end tag" for consistency bugzilla@wiggum.w3.org
- [Bug 8695] Spec currently says " because the order is not particular important" - should say " because the order is not particularly important" or " because the order is not of particular importance" bugzilla@wiggum.w3.org
- [Bug 8692] |datagrid| is not commented out in Special set bugzilla@wiggum.w3.org
- [Bug 8695] Spec currently says " because the order is not particular important" - should say " because the order is not particularly important" or " because the order is not of particular importance" bugzilla@wiggum.w3.org
- [Bug 8692] |datagrid| is not commented out in Special set bugzilla@wiggum.w3.org
- [Bug 8691] Consider moving Timers, User prompts, System state and capabilities, and Offline Web applications into a "Web application APIs" section, and renaming the remaining material from that section to "Core" or some such, to split up that section and make it mor bugzilla@wiggum.w3.org
- [Bug 8691] Consider moving Timers, User prompts, System state and capabilities, and Offline Web applications into a "Web application APIs" section, and renaming the remaining material from that section to "Core" or some such, to split up that section and make it mor bugzilla@wiggum.w3.org
Friday, 5 February 2010
- [Bug 8690] move WindowProxy under the Window section rather than making it a peer, since it's just an implementation detail. bugzilla@wiggum.w3.org
- [Bug 8690] move WindowProxy under the Window section rather than making it a peer, since it's just an implementation detail. bugzilla@wiggum.w3.org
- [Bug 8689] Consider moving the Links subsection into the Elements section, since the Elements subsection these days has lots of processing model subsections. bugzilla@wiggum.w3.org
- [Bug 8689] Consider moving the Links subsection into the Elements section, since the Elements subsection these days has lots of processing model subsections. bugzilla@wiggum.w3.org
- [Bug 8357] Possible Compromise solution for namespaces in HTML5 bugzilla@wiggum.w3.org
- [Bug 8686] Space ship example: s/<code class="attr-class">class</code>/<code title="attr-class">class</code>/ [ms] bugzilla@wiggum.w3.org
- [Bug 8688] Second example uses ALLCAPS for elements bugzilla@wiggum.w3.org
- [Bug 8686] Space ship example: s/<code class="attr-class">class</code>/<code title="attr-class">class</code>/ [ms] bugzilla@wiggum.w3.org
- [Bug 8685] "JavaScript libraries may use the custom data attributes,": fix xref [ms] bugzilla@wiggum.w3.org
- [Bug 8685] "JavaScript libraries may use the custom data attributes,": fix xref [ms] bugzilla@wiggum.w3.org
- [Bug 8684] Ensuring user can always access UA's default context menus bugzilla@wiggum.w3.org
- [Bug 8683] UA context menu when author context menu shown bugzilla@wiggum.w3.org
- [Bug 8682] Tab and reading order for context menus bugzilla@wiggum.w3.org
- [Bug 8681] Separator menu items bugzilla@wiggum.w3.org
- [Bug 8680] Meaningful label in menu example bugzilla@wiggum.w3.org
- [Bug 8679] Menu example contains a violation of WCAG 2.0 bugzilla@wiggum.w3.org
- [Bug 8679] Menu example contains a violation of WCAG 2.0 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 8676] can the placeholder text be styled via css? for example, if I believe the shade of gray is too light, can I make it darker easily? bugzilla@wiggum.w3.org
- [Bug 8671] Requiring the label attribute bugzilla@wiggum.w3.org
- [Bug 8549] Define bgsound, multicol. [ms] bugzilla@wiggum.w3.org
- [Bug 8549] Define bgsound, multicol. [ms] bugzilla@wiggum.w3.org
- [Bug 8321] change controller for HTML media type bugzilla@wiggum.w3.org
- [Bug 8675] visibility:hidden and visibility:collapse should probably also mean it's not "being rendered" [sp] bugzilla@wiggum.w3.org
- [Bug 8675] visibility:hidden and visibility:collapse should probably also mean it's not "being rendered" [sp] bugzilla@wiggum.w3.org
- [Bug 8673] Restriction on command element as part of a menu bugzilla@wiggum.w3.org
- [Bug 8672] Synthetic clicks same as real clicks bugzilla@wiggum.w3.org
- [Bug 8670] Parent for radiobuttons with same radiogroup bugzilla@wiggum.w3.org
- [Bug 8665] Spec currently says "Here is an of a range control" - seems like it should say "Here is an example of a range control" bugzilla@wiggum.w3.org
- [Bug 8666] Keyboard accessible date pickers bugzilla@wiggum.w3.org
- [Bug 8664] Media error code typo bugzilla@wiggum.w3.org
- [Bug 8665] Spec currently says "Here is an of a range control" - seems like it should say "Here is an example of a range control" bugzilla@wiggum.w3.org
- [Bug 8664] Media error code typo bugzilla@wiggum.w3.org
- [Bug 8486] Define inheritance of lang, dir, style, and presatational attributes (HTML4 §11.3.2.1 "Inheritance of alignment specifications") [ms] bugzilla@wiggum.w3.org
- [Bug 8375] Mention that when in "in select in table", there is always a "select" element in table scope bugzilla@wiggum.w3.org
- [Bug 8652] what to display when images are not available is not well specified bugzilla@wiggum.w3.org
- [Bug 8650] Is there any need to add additional information about the video file (bitrate, for example) that would help the UA determine if it can play the file? 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 8649] Resize IFrame bugzilla@wiggum.w3.org
- [Bug 8648] Title attribute on the IFrame element bugzilla@wiggum.w3.org
- [Bug 8591] list document.html under DOM tree accessors? bugzilla@wiggum.w3.org
- [Bug 8647] Define tab order for IFrame bugzilla@wiggum.w3.org
- [Bug 8644] Fallback mechanism for embedded content bugzilla@wiggum.w3.org
- [Bug 8885] New: Fallback mechanism for embedded content bugzilla@wiggum.w3.org
- [Bug 8643] Headings out of sequence bugzilla@wiggum.w3.org
- [Bug 8641] use type="image/vnd.microsoft.icon" for windows.ico bugzilla@wiggum.w3.org
- [Bug 8641] use type="image/vnd.microsoft.icon" for windows.ico bugzilla@wiggum.w3.org
- [Bug 8639] queryCommandIndeterm() always returns false for all commands defined by the spec. So either remove the method or add a note explaining its purpose so that vendor extensions can use it in the way intended. bugzilla@wiggum.w3.org
- [Bug 8591] list document.html under DOM tree accessors? bugzilla@wiggum.w3.org
- [Bug 8638] typo: "is represents" right below the box of IDL bugzilla@wiggum.w3.org
- [Bug 8637] You mean HTMLDocument, not DocumentHTML, right? DocumentHTML appears twice in this section. bugzilla@wiggum.w3.org
- [Bug 8638] typo: "is represents" right below the box of IDL bugzilla@wiggum.w3.org
- [Bug 8637] You mean HTMLDocument, not DocumentHTML, right? DocumentHTML appears twice in this section. bugzilla@wiggum.w3.org
- [Bug 8634] typo: "was the most recently became" bugzilla@wiggum.w3.org
- [Bug 8633] In step 3 of the setTimeout() algorithm, either delete "either" or add an "or" clause to it. Also, in step 5, the context variable is undefined (unless the definition from the "get the timed task" subroutine applies here). bugzilla@wiggum.w3.org
- [Bug 8634] typo: "was the most recently became" bugzilla@wiggum.w3.org
- [Bug 8633] In step 3 of the setTimeout() algorithm, either delete "either" or add an "or" clause to it. Also, in step 5, the context variable is undefined (unless the definition from the "get the timed task" subroutine applies here). bugzilla@wiggum.w3.org
- [Bug 8632] typo: last line of 6.5.6.3 says "do nothing where where" bugzilla@wiggum.w3.org
- [Bug 8632] typo: last line of 6.5.6.3 says "do nothing where where" bugzilla@wiggum.w3.org
- [Bug 8883] New: insert number bugzilla@wiggum.w3.org
Thursday, 4 February 2010
Wednesday, 3 February 2010
Tuesday, 2 February 2010
Monday, 1 February 2010
Last message date: Sunday, 28 February 2010 19:32:26 UTC