public-html-bugzilla@w3.org from October 2009 by date

Saturday, 31 October 2009

• [Bug 8142] New: title: "abbr; dfn;" - remove ";" [ms] bugzilla@wiggum.w3.org
• [Bug 8141] New: Add hr color content attribute [ms] bugzilla@wiggum.w3.org
• [Bug 8140] New: Consider adding color IDL attribute (IE, Gecko). [ms] bugzilla@wiggum.w3.org
• [Bug 8139] New: In #the-section-element the graduation programme example code formatting is strange—closing brackets have been moved to the subsequent line, elements have been first-letter capitalised bugzilla@wiggum.w3.org
• [Bug 8138] New: in aside for blogrolls example <h1>My last post</h1> appears twice, 2nd one should probably be <h1>My first post</h1> bugzilla@wiggum.w3.org

Friday, 30 October 2009

• [Bug 8099] Update 9.5 (Parsing HTML Fragments) for "script data" tokenizer state bugzilla@wiggum.w3.org
• [Bug 7778] "interpreted as a character encoding" is not linked to a defined algorithm bugzilla@wiggum.w3.org
• [Bug 8137] In the scripting-enabled case, noscript outside head has to be conforming if replaced by its parsed text, but noscript inside head doesn't (so <noscript><meta bogus></noscript> is allowed); they ought to consistently require conformingness. [pt] bugzilla@wiggum.w3.org
• [Bug 8137] New: In the scripting-enabled case, noscript outside head has to be conforming if replaced by its parsed text, but noscript inside head doesn't (so <noscript><meta bogus></noscript> is allowed); they ought to consistently require conformingness. [pt] bugzilla@wiggum.w3.org
• [Bug 8136] New: "the DOM text attribute" - s/DOM/IDL/ [pt] bugzilla@wiggum.w3.org
• [Bug 8135] "The script element has a src attribute set where previously the element had no such attribute." - should probably only happen if the script is in a document at the time, else http://software.hixie.ch/utilities/js/live-dom-viewer/saved/298 would break (th bugzilla@wiggum.w3.org
• [Bug 8135] New: "The script element has a src attribute set where previously the element had no such attribute." - should probably only happen if the script is in a document at the time, else http://software.hixie.ch/utilities/js/live-dom-viewer/saved/298 would break (th bugzilla@wiggum.w3.org
• [Bug 8125] Can it be specified somewhere that script can define a variable named "top" with 'var top' in a global context? This is currently inconsistent across browsers. bugzilla@wiggum.w3.org
• [Bug 8126] gfgfdg bugzilla@wiggum.w3.org
• [Bug 8126] New: gfgfdg bugzilla@wiggum.w3.org
• [Bug 8107] I dont think that itemid should be prohibited if there is no itemtype. Several of the use cases would work fine with an id but no type bugzilla@wiggum.w3.org

Thursday, 29 October 2009

• [Bug 8125] Can it be specified somewhere that script can define a variable named "top" with 'var top' in a global context? This is currently inconsistent across browsers. bugzilla@wiggum.w3.org
• [Bug 5758] insufficient accessibility fallback for <audio> or <video> bugzilla@wiggum.w3.org
• [Bug 8122] This is a test bugzilla@wiggum.w3.org
• [Bug 8125] New: Can it be specified somewhere that script can define a variable named "top" with 'var top' in a global context? This is currently inconsistent across browsers. bugzilla@wiggum.w3.org
• [Bug 5758] insufficient accessibility fallback for <audio> or <video> bugzilla@wiggum.w3.org
• [Bug 8088] Change back the meaning of <meta http-equiv="Content-Language" content="FOO, BAR"> bugzilla@wiggum.w3.org
• [Bug 8088] Change back the meaning of <meta http-equiv="Content-Language" content="FOO, BAR"> bugzilla@wiggum.w3.org
• [Bug 8088] Change back the meaning of <meta http-equiv="Content-Language" content="FOO, BAR"> bugzilla@wiggum.w3.org
• [Bug 8107] I dont think that itemid should be prohibited if there is no itemtype. Several of the use cases would work fine with an id but no type bugzilla@wiggum.w3.org
• [Bug 8088] Change back the meaning of <meta http-equiv="Content-Language" content="FOO, BAR"> bugzilla@wiggum.w3.org
• [Bug 8122] New: This is a test bugzilla@wiggum.w3.org
• [Bug 8088] Change back the meaning of <meta http-equiv="Content-Language" content="FOO, BAR"> bugzilla@wiggum.w3.org

Wednesday, 28 October 2009

• [Bug 8121] New: what does this do? bugzilla@wiggum.w3.org
• [Bug 8120] New: Shoud their be any reason that two circles, pure white, alpha =1, drawn in xor mode, do not overlap each other perfectly and then do not "cancel" each other ? (this works with rects). Same effect in Safari and firefox. Thanks bugzilla@wiggum.w3.org
• [Bug 6462] Self-reference and cyclic references in headers='' bugzilla@wiggum.w3.org
• [Bug 8114] Section "months" should be renamed to "year-months". This is clearer, and allows the spec to add a section just handling months (without years) in the future. bugzilla@wiggum.w3.org
• [Bug 8038] Permit closing tag for new, void elements - for legacy compatibility = XHTML alignment bugzilla@wiggum.w3.org
• [Bug 8116] URNs are URIs but not URLs bugzilla@wiggum.w3.org
• [Bug 8116] New: URNs are URIs but not URLs bugzilla@wiggum.w3.org
• [Bug 8115] New: The note on time-zone ranges is too absolute in stating the limits from -12 to +14 and 00/30/45 minutes. Add the word "currently" in to the note. bugzilla@wiggum.w3.org
• [Bug 8114] New: Section "months" should be renamed to "year-months". This is clearer, and allows the spec to add a section just handling months (without years) in the future. bugzilla@wiggum.w3.org
• [Bug 8038] Permit closing tag for new, void elements - for legacy compatibility = XHTML alignment bugzilla@wiggum.w3.org
• [Bug 8113] New: checking should be cancelable bugzilla@wiggum.w3.org
• [Bug 8112] New: the border-style on table and td, th should only be set when <table border> is present bugzilla@wiggum.w3.org
• [Bug 8111] New: when <table border> is present, the border-width of the table's th and td should be set to 1px as a presentational hint bugzilla@wiggum.w3.org
• [Bug 8110] New: <table border=adsf> should also have 1px border bugzilla@wiggum.w3.org
• [Bug 7978] Form foster parenting introduces extra space to layout bugzilla@wiggum.w3.org
• [Bug 8107] I dont think that itemid should be prohibited if there is no itemtype. Several of the use cases would work fine with an id but no type bugzilla@wiggum.w3.org
• [Bug 8107] I dont think that itemid should be prohibited if there is no itemtype. Several of the use cases would work fine with an id but no type bugzilla@wiggum.w3.org
• [Bug 8107] I dont think that itemid should be prohibited if there is no itemtype. Several of the use cases would work fine with an id but no type bugzilla@wiggum.w3.org
• [Bug 8107] I dont think that itemid should be prohibited if there is no itemtype. Several of the use cases would work fine with an id but no type bugzilla@wiggum.w3.org
• [Bug 8107] I dont think that itemid should be prohibited if there is no itemtype. Several of the use cases would work fine with an id but no type bugzilla@wiggum.w3.org
• [Bug 8107] I dont think that itemid should be prohibited if there is no itemtype. Several of the use cases would work fine with an id but no type bugzilla@wiggum.w3.org
• [Bug 8109] New: I'm looking for the API proposal of accessing metadata of media files. For example, I'll want to access metadata of audio files for to get it's title, artists, etc. Or, if I need to get the shooting time of photo, I'll want to get it from JPEG's EXIF bugzilla@wiggum.w3.org
• [Bug 8108] New: There is no reference about the mouseover event judgment when the element(iframe,canvas, etc..) including the transparent shade comes in succession mutually, and it embarrasses it. I hope the judgment to be done as seen. bugzilla@wiggum.w3.org
• [Bug 8107] I dont think that itemid should be prohibited if there is no itemtype. Several of the use cases would work fine with an id but no type bugzilla@wiggum.w3.org
• [Bug 8107] I dont think that itemid should be prohibited if there is no itemtype. Several of the use cases would work fine with an id but no type bugzilla@wiggum.w3.org
• [Bug 8107] New: I dont think that itemid should be prohibited if there is no itemtype. Several of the use cases would work fine with an id but no type bugzilla@wiggum.w3.org
• [Bug 8106] New: typo: doubled "the" bugzilla@wiggum.w3.org
• [Bug 8105] New: typo: doubled "the" bugzilla@wiggum.w3.org
• [Bug 8104] New: typo: doubled "the" bugzilla@wiggum.w3.org
• [Bug 8103] New: typo: doubled "the", and that two times. bugzilla@wiggum.w3.org
• [Bug 8102] New: typo: doubled "the", and that two times. bugzilla@wiggum.w3.org
• [Bug 8101] New: typo: doubled "the" bugzilla@wiggum.w3.org
• [Bug 8100] New: typo : double "the" bugzilla@wiggum.w3.org
• [Bug 8099] New: Update 9.5 (Parsing HTML Fragments) for "script data" tokenizer state bugzilla@wiggum.w3.org

Tuesday, 27 October 2009

• [Bug 8097] New: Link relation types should use the IANA registry per draft-nottingham-http-link-header bugzilla@wiggum.w3.org
• [Bug 8096] New: <link>'s "type" attribute should be allowed to appear multiple times and/or should allow for a space separated list of advertised types, such that clients can request them via the Accept: header. bugzilla@wiggum.w3.org
• [Bug 8095] New: link's "type" attribute could be used to advertise available representations if it were linked to the Accept: header per Mike Kelly's thread(s) bugzilla@wiggum.w3.org
• [Bug 8094] New: It's not very clear whether or not this includes word-style, squiggly-line, as-you-type spell-checking. This feature sounds like more of a manual spell-check done after a body of text is completed. Should a spell-check option be added to the CSS spec for bugzilla@wiggum.w3.org
• [Bug 8092] HTMLCollection subclass interfaces are incompatible with static languages bugzilla@wiggum.w3.org
• [Bug 8093] New: Why is the browsing context name reset on domain navigation? bugzilla@wiggum.w3.org
• [Bug 8092] HTMLCollection subclass interfaces are incompatible with static languages bugzilla@wiggum.w3.org
• [Bug 8092] New: HTMLCollection subclass interfaces are incompatible with static languages bugzilla@wiggum.w3.org
• [Bug 8079] "the document is therefore required to use UTF-8 as its encoding" - this sounds like it's intended as an informative restatement of the conformance requirements in #character-encoding-declaration, in which case it shouldn't use the normative keyword "requ bugzilla@wiggum.w3.org
• [Bug 8088] Change back the meaning of <meta http-equiv="Content-Language" content="FOO, BAR"> bugzilla@wiggum.w3.org
• [Bug 8091] What must the flag initially be, when it wasn't set by the HTML parser? bugzilla@wiggum.w3.org
• [Bug 8091] What must the flag initially be, when it wasn't set by the HTML parser? bugzilla@wiggum.w3.org
• [Bug 8090] "must be the preferred MIME name for that encoding" - should say it's an ASCII case-insensitive match of the preferred MIME name bugzilla@wiggum.w3.org
• [Bug 8090] "must be the preferred MIME name for that encoding" - should say it's an ASCII case-insensitive match of the preferred MIME name bugzilla@wiggum.w3.org
• [Bug 8089] "identifying a script resource of the type given by the type attribute, if the attribute is present, or of the type "text/javascript", if the attribute is absent." - what does "of the type" mean? Sounds like it means the HTTP content-type must be that val bugzilla@wiggum.w3.org
• [Bug 8089] "identifying a script resource of the type given by the type attribute, if the attribute is present, or of the type "text/javascript", if the attribute is absent." - what does "of the type" mean? Sounds like it means the HTTP content-type must be that val bugzilla@wiggum.w3.org
• [Bug 8088] Change back the meaning of <meta http-equiv="Content-Language" content="FOO, BAR"> bugzilla@wiggum.w3.org
• [Bug 8087] '<any string that doesn't contain the substring "-->" >' is not valid ABNF (prose-val can't contain '>') bugzilla@wiggum.w3.org
• [Bug 8087] '<any string that doesn't contain the substring "-->" >' is not valid ABNF (prose-val can't contain '>') bugzilla@wiggum.w3.org
• [Bug 8055] "of the RFC 2046" - s/the// bugzilla@wiggum.w3.org
• [Bug 8055] "of the RFC 2046" - s/the// bugzilla@wiggum.w3.org
• [Bug 8083] "Pragma directions" - s/ons/ves/ bugzilla@wiggum.w3.org
• [Bug 8058] "The hgroup element should be used in these kinds of situations:" - shouldn't use normative keywords in non-normative text bugzilla@wiggum.w3.org
• [Bug 8059] "This includes HTML elements in XML documents, even when those documents are in another context (e.g. inside an XSLT transform)" - that seems to conflict with an earlier example saying "if the element is found within a transformation expressed in XSLT (as bugzilla@wiggum.w3.org
• [Bug 8060] Why must class be a set of unique tokens? It's quite common to have duplicates (~0.5% of dotbot pages), and convenient when you're programmatically generating HTML, and harmless bugzilla@wiggum.w3.org
• [Bug 8060] Why must class be a set of unique tokens? It's quite common to have duplicates (~0.5% of dotbot pages), and convenient when you're programmatically generating HTML, and harmless bugzilla@wiggum.w3.org
• [Bug 8065] "Otherwise, let new children be targets returned." - s/targets/the nodes/ bugzilla@wiggum.w3.org
• [Bug 8061] "Authors may use any value in the class attribute" - no they mayn't, since earlier it was said it "must have a value that is ...". Maybe it should say "Authors may use any token values ...". Also, s/use the values/use values/ bugzilla@wiggum.w3.org
• [Bug 8067] "Otherwise, let new children be targets returned." - s/targets/the nodes/ bugzilla@wiggum.w3.org
• [Bug 8065] "Otherwise, let new children be targets returned." - s/targets/the nodes/ bugzilla@wiggum.w3.org
• [Bug 8073] "For example, redirects must be followed" - examples are non-normative, so this should not use normative keywords bugzilla@wiggum.w3.org
• [Bug 8074] The document load event is delayed until all resources are obtained, but obtaining might be delayed indefinitely if the resource is fetched when needed and not pro-actively, so load may be delayed indefinitely, which doesn't sound sensible. Is that intent bugzilla@wiggum.w3.org
• [Bug 8079] "the document is therefore required to use UTF-8 as its encoding" - this sounds like it's intended as an informative restatement of the conformance requirements in #character-encoding-declaration, in which case it shouldn't use the normative keyword "requ bugzilla@wiggum.w3.org
• [Bug 8079] "the document is therefore required to use UTF-8 as its encoding" - this sounds like it's intended as an informative restatement of the conformance requirements in #character-encoding-declaration, in which case it shouldn't use the normative keyword "requ bugzilla@wiggum.w3.org
• [Bug 8084] "In particular, this applies to encodings in which the bytes corresponding to "<script>" in ASCII can encode a different string." - s/In particular/For example/ (there's nothing particular about <script>, it could be <img onload=...> or <div style=color:e bugzilla@wiggum.w3.org
• [Bug 8084] "In particular, this applies to encodings in which the bytes corresponding to "<script>" in ASCII can encode a different string." - s/In particular/For example/ (there's nothing particular about <script>, it could be <img onload=...> or <div style=color:e bugzilla@wiggum.w3.org
• [Bug 8085] The list of known dangerous encodings should include JOHAB and CP1361, both of which encode characters to sequences with the byte "<", and both of which are supported by iconv (and presumably other implementations) bugzilla@wiggum.w3.org
• [Bug 8056] "Replace any sequence of two or more consecutive space characters in value with a single U+0020 SPACE character." - should be "one or more", so that single newlines etc get turned into spaces too bugzilla@wiggum.w3.org
• [Bug 8089] New: "identifying a script resource of the type given by the type attribute, if the attribute is present, or of the type "text/javascript", if the attribute is absent." - what does "of the type" mean? Sounds like it means the HTTP content-type must be that val bugzilla@wiggum.w3.org
• [Bug 8074] The document load event is delayed until all resources are obtained, but obtaining might be delayed indefinitely if the resource is fetched when needed and not pro-actively, so load may be delayed indefinitely, which doesn't sound sensible. Is that intent bugzilla@wiggum.w3.org
• [Bug 8079] "the document is therefore required to use UTF-8 as its encoding" - this sounds like it's intended as an informative restatement of the conformance requirements in #character-encoding-declaration, in which case it shouldn't use the normative keyword "requ bugzilla@wiggum.w3.org
• [Bug 8080] Event firing section still talks about namespaces bugzilla@wiggum.w3.org
• [Bug 8080] Event firing section still talks about namespaces bugzilla@wiggum.w3.org
• [Bug 8081] There should be an example of the content="0; url=http://example.com/" style syntax, because it's particularly hard to deduce from the definition of valid syntax bugzilla@wiggum.w3.org
• [Bug 8081] There should be an example of the content="0; url=http://example.com/" style syntax, because it's particularly hard to deduce from the definition of valid syntax bugzilla@wiggum.w3.org
• [Bug 8085] The list of known dangerous encodings should include JOHAB and CP1361, both of which encode characters to sequences with the byte "<", and both of which are supported by iconv (and presumably other implementations) bugzilla@wiggum.w3.org
• [Bug 8091] New: What must the flag initially be, when it wasn't set by the HTML parser? bugzilla@wiggum.w3.org
• [Bug 8073] "For example, redirects must be followed" - examples are non-normative, so this should not use normative keywords bugzilla@wiggum.w3.org
• [Bug 8065] "Otherwise, let new children be targets returned." - s/targets/the nodes/ bugzilla@wiggum.w3.org
• [Bug 8061] "Authors may use any value in the class attribute" - no they mayn't, since earlier it was said it "must have a value that is ...". Maybe it should say "Authors may use any token values ...". Also, s/use the values/use values/ bugzilla@wiggum.w3.org
• [Bug 8090] New: "must be the preferred MIME name for that encoding" - should say it's an ASCII case-insensitive match of the preferred MIME name bugzilla@wiggum.w3.org
• [Bug 8058] "The hgroup element should be used in these kinds of situations:" - shouldn't use normative keywords in non-normative text bugzilla@wiggum.w3.org
• [Bug 8064] "... and thus their behavior, varies depending on ..." - remove comma bugzilla@wiggum.w3.org
• [Bug 8059] "This includes HTML elements in XML documents, even when those documents are in another context (e.g. inside an XSLT transform)" - that seems to conflict with an earlier example saying "if the element is found within a transformation expressed in XSLT (as bugzilla@wiggum.w3.org
• [Bug 8088] New: Change back the meaning of <meta http-equiv="Content-Language" content="FOO, BAR"> bugzilla@wiggum.w3.org
• [Bug 8087] '<any string that doesn't contain the substring "-->" >' is not valid ABNF (prose-val can't contain '>') bugzilla@wiggum.w3.org
• [Bug 8087] New: '<any string that doesn't contain the substring "-->" >' is not valid ABNF (prose-val can't contain '>') bugzilla@wiggum.w3.org
• [Bug 8086] New: "Furtermore" bugzilla@wiggum.w3.org
• [Bug 8085] New: The list of known dangerous encodings should include JOHAB and CP1361, both of which encode characters to sequences with the byte "<", and both of which are supported by iconv (and presumably other implementations) bugzilla@wiggum.w3.org
• [Bug 8038] Permit closing tag for new, void elements - for legacy compatibility = XHTML alignment bugzilla@wiggum.w3.org
• [Bug 8084] New: "In particular, this applies to encodings in which the bytes corresponding to "<script>" in ASCII can encode a different string." - s/In particular/For example/ (there's nothing particular about <script>, it could be <img onload=...> or <div style=color:e bugzilla@wiggum.w3.org
• [Bug 7633] The use of @summary should be encouraged when circumstances warrant bugzilla@wiggum.w3.org
• [Bug 8083] New: "Pragma directions" - s/ons/ves/ bugzilla@wiggum.w3.org
• [Bug 8082] New: "a HTTP header" - s/a/an/ bugzilla@wiggum.w3.org
• [Bug 8081] New: There should be an example of the content="0; url=http://example.com/" style syntax, because it's particularly hard to deduce from the definition of valid syntax bugzilla@wiggum.w3.org
• [Bug 8038] Permit closing tag for new, void elements - for legacy compatibility = XHTML alignment bugzilla@wiggum.w3.org
• [Bug 8038] Permit closing tag for new, void elements - for legacy compatibility = XHTML alignment bugzilla@wiggum.w3.org
• [Bug 6181] Process table feedback (including headers='" issue) bugzilla@wiggum.w3.org
• [Bug 8047] Reflecting floats: The rules for parsing floating point number values return an unlimited-precision (finite in base 10) number. How is it converted to limited-precision IDL attribute types? In particular, what rounding mode is used? and do very large valu bugzilla@wiggum.w3.org
• [Bug 5807] User Agent display of title attribute content not defined bugzilla@wiggum.w3.org
• [Bug 8080] New: Event firing section still talks about namespaces bugzilla@wiggum.w3.org
• [Bug 8077] article bugzilla@wiggum.w3.org
• [Bug 8054] lastModified could perhaps return a date like "10/25/0002009". It should say that the year is the "*shortest possible* string of four or more digits ..." bugzilla@wiggum.w3.org
• [Bug 8054] lastModified could perhaps return a date like "10/25/0002009". It should say that the year is the "*shortest possible* string of four or more digits ..." bugzilla@wiggum.w3.org
• [Bug 8047] Reflecting floats: The rules for parsing floating point number values return an unlimited-precision (finite in base 10) number. How is it converted to limited-precision IDL attribute types? In particular, what rounding mode is used? and do very large valu bugzilla@wiggum.w3.org
• [Bug 8047] Reflecting floats: The rules for parsing floating point number values return an unlimited-precision (finite in base 10) number. How is it converted to limited-precision IDL attribute types? In particular, what rounding mode is used? and do very large valu bugzilla@wiggum.w3.org
• [Bug 8079] New: "the document is therefore required to use UTF-8 as its encoding" - this sounds like it's intended as an informative restatement of the conformance requirements in #character-encoding-declaration, in which case it shouldn't use the normative keyword "requ bugzilla@wiggum.w3.org
• [Bug 8038] Permit closing tag for new, void elements - for legacy compatibility = XHTML alignment bugzilla@wiggum.w3.org
• [Bug 7978] Form foster parenting introduces extra space to layout bugzilla@wiggum.w3.org
• [Bug 7978] Form foster parenting introduces extra space to layout bugzilla@wiggum.w3.org
• [Bug 8077] New: article bugzilla@wiggum.w3.org
• [Bug 7978] Form foster parenting introduces extra space to layout bugzilla@wiggum.w3.org
• [Bug 7978] Form foster parenting introduces extra space to layout bugzilla@wiggum.w3.org
• [Bug 7978] Form foster parenting introduces extra space to layout bugzilla@wiggum.w3.org
• [Bug 7978] Form foster parenting introduces extra space to layout bugzilla@wiggum.w3.org
• [Bug 8003] line breaks in attributes (especially title) bugzilla@wiggum.w3.org

Monday, 26 October 2009

• [Bug 8003] line breaks in attributes (especially title) bugzilla@wiggum.w3.org
• [Bug 7978] Form foster parenting introduces extra space to layout bugzilla@wiggum.w3.org
• [Bug 7978] Form foster parenting introduces extra space to layout bugzilla@wiggum.w3.org
• [Bug 7978] Form foster parenting introduces extra space to layout bugzilla@wiggum.w3.org
• [Bug 7260] Create testsuite for table headers association bugzilla@wiggum.w3.org
• [Bug 8038] Permit closing tag for new, void elements - for legacy compatibility = XHTML alignment bugzilla@wiggum.w3.org
• [Bug 7978] Form foster parenting introduces extra space to layout bugzilla@wiggum.w3.org
• [Bug 7978] Form foster parenting introduces extra space to layout bugzilla@wiggum.w3.org
• [Bug 7978] Form foster parenting introduces extra space to layout bugzilla@wiggum.w3.org
• [Bug 7978] Form foster parenting introduces extra space to layout bugzilla@wiggum.w3.org
• [Bug 7978] Form foster parenting introduces extra space to layout bugzilla@wiggum.w3.org
• [Bug 7978] Form foster parenting introduces extra space to layout bugzilla@wiggum.w3.org
• [Bug 7978] Form foster parenting introduces extra space to layout bugzilla@wiggum.w3.org
• [Bug 7978] Form foster parenting introduces extra space to layout bugzilla@wiggum.w3.org
• [Bug 8074] New: The document load event is delayed until all resources are obtained, but obtaining might be delayed indefinitely if the resource is fetched when needed and not pro-actively, so load may be delayed indefinitely, which doesn't sound sensible. Is that intent bugzilla@wiggum.w3.org
• [Bug 8073] New: "For example, redirects must be followed" - examples are non-normative, so this should not use normative keywords bugzilla@wiggum.w3.org
• [Bug 7978] Form foster parenting introduces extra space to layout bugzilla@wiggum.w3.org
• [Bug 8003] line breaks in attributes (especially title) bugzilla@wiggum.w3.org
• [Bug 7978] Form foster parenting introduces extra space to layout bugzilla@wiggum.w3.org
• [Bug 8000] ARIA roles added to the a element should be conforming in HTML5 bugzilla@wiggum.w3.org
• [Bug 7978] Form foster parenting introduces extra space to layout bugzilla@wiggum.w3.org
• [Bug 8067] New: "Otherwise, let new children be targets returned." - s/targets/the nodes/ bugzilla@wiggum.w3.org
• [Bug 8066] New: "Parsed the given string text as HTML or XML and inserts" - should be "Parses" bugzilla@wiggum.w3.org
• [Bug 8065] New: "Otherwise, let new children be targets returned." - s/targets/the nodes/ bugzilla@wiggum.w3.org
• [Bug 8060] Why must class be a set of unique tokens? It's quite common to have duplicates (~0.5% of dotbot pages), and convenient when you're programmatically generating HTML, and harmless bugzilla@wiggum.w3.org
• [Bug 8000] ARIA roles added to the a element should be conforming in HTML5 bugzilla@wiggum.w3.org
• [Bug 8038] Permit closing tag for new, void elements - for legacy compatibility = XHTML alignment bugzilla@wiggum.w3.org
• [Bug 8064] New: "... and thus their behavior, varies depending on ..." - remove comma bugzilla@wiggum.w3.org
• [Bug 8063] New: "correponding" bugzilla@wiggum.w3.org
• [Bug 8062] New: "there must be namespace declaration" - should be "a" or "declarations" or something bugzilla@wiggum.w3.org
• [Bug 8038] Permit closing tag for new, void elements - for legacy compatibility = XHTML alignment bugzilla@wiggum.w3.org

Sunday, 25 October 2009

• [Bug 8038] Permit closing tag for new, void elements - for legacy compatibility = XHTML alignment bugzilla@wiggum.w3.org
• [Bug 8038] Permit closing tag for new, void elements - for legacy compatibility = XHTML alignment bugzilla@wiggum.w3.org
• [Bug 8003] line breaks in attributes (especially title) bugzilla@wiggum.w3.org
• [Bug 8038] Permit closing tag for new, void elements - for legacy compatibility = XHTML alignment bugzilla@wiggum.w3.org
• [Bug 8061] New: "Authors may use any value in the class attribute" - no they mayn't, since earlier it was said it "must have a value that is ...". Maybe it should say "Authors may use any token values ...". Also, s/use the values/use values/ bugzilla@wiggum.w3.org
• [Bug 8060] New: Why must class be a set of unique tokens? It's quite common to have duplicates (~0.5% of dotbot pages), and convenient when you're programmatically generating HTML, and harmless bugzilla@wiggum.w3.org
• [Bug 8059] New: "This includes HTML elements in XML documents, even when those documents are in another context (e.g. inside an XSLT transform)" - that seems to conflict with an earlier example saying "if the element is found within a transformation expressed in XSLT (as bugzilla@wiggum.w3.org
• [Bug 8058] New: "The hgroup element should be used in these kinds of situations:" - shouldn't use normative keywords in non-normative text bugzilla@wiggum.w3.org
• [Bug 8057] New: IDL block needs class="idl" bugzilla@wiggum.w3.org
• [Bug 8056] New: "Replace any sequence of two or more consecutive space characters in value with a single U+0020 SPACE character." - should be "one or more", so that single newlines etc get turned into spaces too bugzilla@wiggum.w3.org
• [Bug 8055] New: "of the RFC 2046" - s/the// bugzilla@wiggum.w3.org
• [Bug 8054] New: lastModified could perhaps return a date like "10/25/0002009". It should say that the year is the "*shortest possible* string of four or more digits ..." bugzilla@wiggum.w3.org
• [Bug 8047] Reflecting floats: The rules for parsing floating point number values return an unlimited-precision (finite in base 10) number. How is it converted to limited-precision IDL attribute types? In particular, what rounding mode is used? and do very large valu bugzilla@wiggum.w3.org
• [Bug 8053] why &race; defined in older revision has been removed? bugzilla@wiggum.w3.org
• [Bug 8052] The spec should not allow <map name=a> when there is <map name=A> bugzilla@wiggum.w3.org
• [Bug 8052] The spec should not allow <map name=a> when there is <map name=A> bugzilla@wiggum.w3.org
• [Bug 8050] "creator void (in DOMString name);" - should have a 'value' argument bugzilla@wiggum.w3.org
• [Bug 8051] "The following DOMException codes are defined in DOM Core." - no they're not (only 1..17 are defined in the referenced document) bugzilla@wiggum.w3.org
• [Bug 8050] "creator void (in DOMString name);" - should have a 'value' argument bugzilla@wiggum.w3.org
• [Bug 8046] Reflecting floats: The IDL attribute types include +/-Infinity, so it doesn't make sense to talk about floats being "out of range" because everything is within the infinite range bugzilla@wiggum.w3.org
• [Bug 8049] For consistency with HTMLFormControlsCollection and HTMLOptionsCollection, this should probably be called HTMLPropertiesCollection bugzilla@wiggum.w3.org
• [Bug 8046] Reflecting floats: The IDL attribute types include +/-Infinity, so it doesn't make sense to talk about floats being "out of range" because everything is within the infinite range bugzilla@wiggum.w3.org
• [Bug 8048] "The same DOMTokenList object must be returned every time for each attribute" - should say "DOMTokenList or DOMSettableTokenList" bugzilla@wiggum.w3.org
• [Bug 8049] For consistency with HTMLFormControlsCollection and HTMLOptionsCollection, this should probably be called HTMLPropertiesCollection bugzilla@wiggum.w3.org
• [Bug 8048] "The same DOMTokenList object must be returned every time for each attribute" - should say "DOMTokenList or DOMSettableTokenList" bugzilla@wiggum.w3.org
• [Bug 8047] Reflecting floats: The rules for parsing floating point number values return an unlimited-precision (finite in base 10) number. How is it converted to limited-precision IDL attribute types? In particular, what rounding mode is used? and do very large valu bugzilla@wiggum.w3.org
• [Bug 8047] Reflecting floats: The rules for parsing floating point number values return an unlimited-precision (finite in base 10) number. How is it converted to limited-precision IDL attribute types? In particular, what rounding mode is used? and do very large valu bugzilla@wiggum.w3.org
• [Bug 8045] Should be called "limited to only non-negative numbers", because it allows 0 (which is not a positive number) bugzilla@wiggum.w3.org
• [Bug 8046] Reflecting floats: The IDL attribute types include +/-Infinity, so it doesn't make sense to talk about floats being "out of range" because everything is within the infinite range bugzilla@wiggum.w3.org
• [Bug 8053] New: why &race; defined in older revision has been removed? bugzilla@wiggum.w3.org
• [Bug 8052] New: The spec should not allow <map name=a> when there is <map name=A> bugzilla@wiggum.w3.org
• [Bug 8045] Should be called "limited to only non-negative numbers", because it allows 0 (which is not a positive number) bugzilla@wiggum.w3.org
• [Bug 8044] The document's current address can contain fragments. HTTP says the Referer must not contain fragments. Presumably HTML5 ought to say to strip the fragment. (document.referrer is affected the same way.) bugzilla@wiggum.w3.org
• [Bug 8044] The document's current address can contain fragments. HTTP says the Referer must not contain fragments. Presumably HTML5 ought to say to strip the fragment. (document.referrer is affected the same way.) bugzilla@wiggum.w3.org
• [Bug 8043] "It is given a string and a starting position" - no it's not. It should probably instead say "Let input and position be the same variables as those of the same name in the algorithm that invoked these steps." bugzilla@wiggum.w3.org
• [Bug 8043] "It is given a string and a starting position" - no it's not. It should probably instead say "Let input and position be the same variables as those of the same name in the algorithm that invoked these steps." bugzilla@wiggum.w3.org
• [Bug 8042] "if denominator has value" - should be "*a* value" bugzilla@wiggum.w3.org
• [Bug 8041] Should say "This algorithm will return either a number, or a number and a denominator character, or two numbers, or nothing", for consistency with other algorithms bugzilla@wiggum.w3.org
• [Bug 8042] "if denominator has value" - should be "*a* value" bugzilla@wiggum.w3.org
• [Bug 8041] Should say "This algorithm will return either a number, or a number and a denominator character, or two numbers, or nothing", for consistency with other algorithms bugzilla@wiggum.w3.org
• [Bug 8040] editorial: this list is not in alphabetical order (itemref should be higher up) bugzilla@wiggum.w3.org
• [Bug 8040] editorial: this list is not in alphabetical order (itemref should be higher up) bugzilla@wiggum.w3.org
• [Bug 8039] "Let queue be a stack of elements" - this is quite a confusing choice of terminology bugzilla@wiggum.w3.org
• [Bug 8039] "Let queue be a stack of elements" - this is quite a confusing choice of terminology bugzilla@wiggum.w3.org
• [Bug 8038] Permit closing tag for new, void elements - for legacy compatibility = XHTML alignment bugzilla@wiggum.w3.org
• [Bug 8037] The form controls collection should just be an HTMLCollection instead of having an HTMLFormControlsCollection interface bugzilla@wiggum.w3.org
• [Bug 8036] HTMLOptionsCollection should inherit from HTMLCollection bugzilla@wiggum.w3.org
• [Bug 8035] HTMLAllCollection should inherit from HTMLCollection bugzilla@wiggum.w3.org
• [Bug 8037] The form controls collection should just be an HTMLCollection instead of having an HTMLFormControlsCollection interface bugzilla@wiggum.w3.org
• [Bug 8036] HTMLOptionsCollection should inherit from HTMLCollection bugzilla@wiggum.w3.org
• [Bug 8035] HTMLAllCollection should inherit from HTMLCollection bugzilla@wiggum.w3.org
• [Bug 8034] It appears that there is no way to draw more than one line of text per call to fillText/strokeText, so what is the point of discarding any line-height value set in the font attribute? bugzilla@wiggum.w3.org
• [Bug 8033] Note in the prose that some exceptions aren't actually defined in [DOMCORE] yet bugzilla@wiggum.w3.org
• [Bug 8033] Note in the prose that some exceptions aren't actually defined in [DOMCORE] yet bugzilla@wiggum.w3.org
• [Bug 8032] Wouldn't it be better to show video/audio controls by default? Otherwise you might end up with media visible on the page that is impossible to play. bugzilla@wiggum.w3.org
• [Bug 8051] New: "The following DOMException codes are defined in DOM Core." - no they're not (only 1..17 are defined in the referenced document) bugzilla@wiggum.w3.org
• [Bug 8050] New: "creator void (in DOMString name);" - should have a 'value' argument bugzilla@wiggum.w3.org
• [Bug 8030] "either 52 weeks or 53 such seven-day periods" - s/weeks// bugzilla@wiggum.w3.org
• [Bug 8030] "either 52 weeks or 53 such seven-day periods" - s/weeks// bugzilla@wiggum.w3.org
• [Bug 8028] If the first character is not Z or + or -, the subalgorithm returns undefined values. It should explicitly fail and return nothing. bugzilla@wiggum.w3.org
• [Bug 8028] If the first character is not Z or + or -, the subalgorithm returns undefined values. It should explicitly fail and return nothing. bugzilla@wiggum.w3.org
• [Bug 8027] Does the time-zone offset also consist of a sign? If so, it should be listed in the introduction. If not, the 'valid ...' definition can't say +/- represents the offset's sign. bugzilla@wiggum.w3.org
• [Bug 8027] Does the time-zone offset also consist of a sign? If so, it should be listed in the introduction. If not, the 'valid ...' definition can't say +/- represents the offset's sign. bugzilla@wiggum.w3.org
• [Bug 8049] New: For consistency with HTMLFormControlsCollection and HTMLOptionsCollection, this should probably be called HTMLPropertiesCollection bugzilla@wiggum.w3.org
• [Bug 8048] New: "The same DOMTokenList object must be returned every time for each attribute" - should say "DOMTokenList or DOMSettableTokenList" bugzilla@wiggum.w3.org
• [Bug 8047] New: Reflecting floats: The rules for parsing floating point number values return an unlimited-precision (finite in base 10) number. How is it converted to limited-precision IDL attribute types? In particular, what rounding mode is used? and do very large valu bugzilla@wiggum.w3.org
• [Bug 8046] New: Reflecting floats: The IDL attribute types include +/-Infinity, so it doesn't make sense to talk about floats being "out of range" because everything is within the infinite range bugzilla@wiggum.w3.org
• [Bug 8045] New: Should be called "limited to only non-negative numbers", because it allows 0 (which is not a positive number) bugzilla@wiggum.w3.org

Saturday, 24 October 2009

• [Bug 8044] New: The document's current address can contain fragments. HTTP says the Referer must not contain fragments. Presumably HTML5 ought to say to strip the fragment. (document.referrer is affected the same way.) bugzilla@wiggum.w3.org
• [Bug 8023] "If day is not a number in the range 1 ≤ month ≤ maxday, then fail." - s/month/day/ bugzilla@wiggum.w3.org
• [Bug 8026] Given a datetime ...T00:00Z, is the best representation ...T00:00-00:00 or ...T00:00+00:00? bugzilla@wiggum.w3.org
• [Bug 8026] Given a datetime ...T00:00Z, is the best representation ...T00:00-00:00 or ...T00:00+00:00? bugzilla@wiggum.w3.org
• [Bug 8025] "Dates before the year zero can't be represented as a datetime in this version of HTML." - s/zero/one/ (though I suppose that's not precisely correct since 0001-01-01T00:00+23:59 is almost a day earlier than the year 1) bugzilla@wiggum.w3.org
• [Bug 8024] "the time zone in use on the east coast of North America during daylight saving time." - should say USA, not North America. (e.g. Nova Scotia looks like it's on the east coast of North America, but it's UTC-3 in DST.) bugzilla@wiggum.w3.org
• [Bug 8025] "Dates before the year zero can't be represented as a datetime in this version of HTML." - s/zero/one/ (though I suppose that's not precisely correct since 0001-01-01T00:00+23:59 is almost a day earlier than the year 1) bugzilla@wiggum.w3.org
• [Bug 8024] "the time zone in use on the east coast of North America during daylight saving time." - should say USA, not North America. (e.g. Nova Scotia looks like it's on the east coast of North America, but it's UTC-3 in DST.) bugzilla@wiggum.w3.org
• [Bug 8023] "If day is not a number in the range 1 ≤ month ≤ maxday, then fail." - s/month/day/ bugzilla@wiggum.w3.org
• [Bug 8022] "ISO8601 libraries might not parse dates and times exactly the same manner" - should be "*in* exactly the same manner" bugzilla@wiggum.w3.org
• [Bug 8021] The step with dividing by 10^{length} is phrased very differently to the fraction loop for parsing floating point numbers, but seems to be achieving the same result. They should be phrased the same, to make it clear they're computing the same thing. bugzilla@wiggum.w3.org
• [Bug 8022] "ISO8601 libraries might not parse dates and times exactly the same manner" - should be "*in* exactly the same manner" bugzilla@wiggum.w3.org
• [Bug 8021] The step with dividing by 10^{length} is phrased very differently to the fraction loop for parsing floating point numbers, but seems to be achieving the same result. They should be phrased the same, to make it clear they're computing the same thing. bugzilla@wiggum.w3.org
• [Bug 8020] "return value as an integer" - that number needs to be categorised as either a percentage or a length, as stated in the introduction bugzilla@wiggum.w3.org
• [Bug 8020] "return value as an integer" - that number needs to be categorised as either a percentage or a length, as stated in the introduction bugzilla@wiggum.w3.org
• [Bug 8019] <!DOCTYPE html PUBLICa> throws two parse errors. bugzilla@wiggum.w3.org
• [Bug 8019] <!DOCTYPE html PUBLICa> throws two parse errors. bugzilla@wiggum.w3.org
• [Bug 8018] The space characters cases within the before DOCTYPE public/system identifier states can never be reached. To fix that, remove those cases. bugzilla@wiggum.w3.org
• [Bug 8043] New: "It is given a string and a starting position" - no it's not. It should probably instead say "Let input and position be the same variables as those of the same name in the algorithm that invoked these steps." bugzilla@wiggum.w3.org
• [Bug 8042] New: "if denominator has value" - should be "*a* value" bugzilla@wiggum.w3.org
• [Bug 8041] New: Should say "This algorithm will return either a number, or a number and a denominator character, or two numbers, or nothing", for consistency with other algorithms bugzilla@wiggum.w3.org
• [Bug 8015] "skip all White_Space characters" - should xref to "skip White_Space characters" bugzilla@wiggum.w3.org
• [Bug 8015] "skip all White_Space characters" - should xref to "skip White_Space characters" bugzilla@wiggum.w3.org
• [Bug 8029] From RCDATA state, & goes to char ref in data, which then goes to data state. Should go back to RCDATA state. bugzilla@wiggum.w3.org
• [Bug 8029] From RCDATA state, & goes to char ref in data, which then goes to data state. Should go back to RCDATA state. bugzilla@wiggum.w3.org
• [Bug 8040] New: editorial: this list is not in alphabetical order (itemref should be higher up) bugzilla@wiggum.w3.org
• [Bug 8039] New: "Let queue be a stack of elements" - this is quite a confusing choice of terminology bugzilla@wiggum.w3.org
• [Bug 8038] New: Permit closing tag for new, void elements - for legacy compatibility = XHTML alignment bugzilla@wiggum.w3.org

Friday, 23 October 2009

• [Bug 8037] The form controls collection should just be an HTMLCollection instead of having an HTMLFormControlsCollection interface bugzilla@wiggum.w3.org
• [Bug 8036] HTMLOptionsCollection should inherit from HTMLCollection bugzilla@wiggum.w3.org
• [Bug 8037] The form controls collection should just be an HTMLCollection instead of having an HTMLFormControlsCollection interface bugzilla@wiggum.w3.org
• [Bug 8037] New: The form controls collection should just be an HTMLCollection instead of having an HTMLFormControlsCollection interface bugzilla@wiggum.w3.org
• [Bug 8036] New: HTMLOptionsCollection should inherit from HTMLCollection bugzilla@wiggum.w3.org
• [Bug 8035] HTMLAllCollection should inherit from HTMLCollection bugzilla@wiggum.w3.org
• [Bug 8035] HTMLAllCollection should inherit from HTMLCollection bugzilla@wiggum.w3.org
• [Bug 8035] New: HTMLAllCollection should inherit from HTMLCollection bugzilla@wiggum.w3.org
• [Bug 7842] No programmatic way to make an HTML document - consider adding createHTMLDocument bugzilla@wiggum.w3.org
• [Bug 8034] New: It appears that there is no way to draw more than one line of text per call to fillText/strokeText, so what is the point of discarding any line-height value set in the font attribute? bugzilla@wiggum.w3.org
• [Bug 8033] New: Note in the prose that some exceptions aren't actually defined in [DOMCORE] yet 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 7245] canvas bugzilla@wiggum.w3.org
• [Bug 5823] Scope allowable on a td bugzilla@wiggum.w3.org
• [Bug 7806] atom ID element generation for feed entries 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 8000] ARIA roles added to the a element should be conforming in HTML5 bugzilla@wiggum.w3.org
• [Bug 5821] meta/@scheme missing bugzilla@wiggum.w3.org
• [Bug 5821] meta/@scheme missing bugzilla@wiggum.w3.org
• [Bug 5822] The headers attribute should be able to reference a td bugzilla@wiggum.w3.org
• [Bug 5758] insufficient accessibility fallback for <audio> or <video> 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 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 7740] Authoring advice for canvas is bad for accessibility bugzilla@wiggum.w3.org
• [Bug 7245] canvas bugzilla@wiggum.w3.org
• [Bug 7011] [in off-bug discussion] canvas accessible fallback provision is under specified 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 8032] New: Wouldn't it be better to show video/audio controls by default? Otherwise you might end up with media visible on the page that is impossible to play. bugzilla@wiggum.w3.org
• [Bug 8003] line breaks in attributes (especially title) bugzilla@wiggum.w3.org
• [Bug 8030] New: "either 52 weeks or 53 such seven-day periods" - s/weeks// bugzilla@wiggum.w3.org
• [Bug 8003] line breaks in attributes (especially title) bugzilla@wiggum.w3.org
• [Bug 8029] New: From RCDATA state, & goes to char ref in data, which then goes to data state. Should go back to RCDATA state. bugzilla@wiggum.w3.org
• [Bug 8028] New: If the first character is not Z or + or -, the subalgorithm returns undefined values. It should explicitly fail and return nothing. bugzilla@wiggum.w3.org
• [Bug 8003] line breaks in attributes (especially title) bugzilla@wiggum.w3.org
• [Bug 8027] New: Does the time-zone offset also consist of a sign? If so, it should be listed in the introduction. If not, the 'valid ...' definition can't say +/- represents the offset's sign. bugzilla@wiggum.w3.org
• [Bug 8026] New: Given a datetime ...T00:00Z, is the best representation ...T00:00-00:00 or ...T00:00+00:00? bugzilla@wiggum.w3.org
• [Bug 8025] New: "Dates before the year zero can't be represented as a datetime in this version of HTML." - s/zero/one/ (though I suppose that's not precisely correct since 0001-01-01T00:00+23:59 is almost a day earlier than the year 1) bugzilla@wiggum.w3.org
• [Bug 8024] New: "the time zone in use on the east coast of North America during daylight saving time." - should say USA, not North America. (e.g. Nova Scotia looks like it's on the east coast of North America, but it's UTC-3 in DST.) bugzilla@wiggum.w3.org
• [Bug 8023] New: "If day is not a number in the range 1 ≤ month ≤ maxday, then fail." - s/month/day/ bugzilla@wiggum.w3.org
• [Bug 8022] New: "ISO8601 libraries might not parse dates and times exactly the same manner" - should be "*in* exactly the same manner" bugzilla@wiggum.w3.org
• [Bug 8021] New: The step with dividing by 10^{length} is phrased very differently to the fraction loop for parsing floating point numbers, but seems to be achieving the same result. They should be phrased the same, to make it clear they're computing the same thing. bugzilla@wiggum.w3.org
• [Bug 8020] New: "return value as an integer" - that number needs to be categorised as either a percentage or a length, as stated in the introduction bugzilla@wiggum.w3.org
• [Bug 8019] New: <!DOCTYPE html PUBLICa> throws two parse errors. bugzilla@wiggum.w3.org
• [Bug 8018] New: The space characters cases within the before DOCTYPE public/system identifier states can never be reached. To fix that, remove those cases. bugzilla@wiggum.w3.org
• [Bug 8003] line breaks in attributes (especially title) bugzilla@wiggum.w3.org
• [Bug 8015] "skip all White_Space characters" - should xref to "skip White_Space characters" bugzilla@wiggum.w3.org
• [Bug 7918] prefetching: allow site to deny bugzilla@wiggum.w3.org
• [Bug 7918] prefetching: allow site to deny bugzilla@wiggum.w3.org
• [Bug 7918] prefetching: allow site to deny bugzilla@wiggum.w3.org
• [Bug 8000] ARIA roles added to the a element should be conforming in HTML5 bugzilla@wiggum.w3.org
• [Bug 8000] ARIA roles added to the a element should be conforming in HTML5 bugzilla@wiggum.w3.org
• [Bug 8016] anything bugzilla@wiggum.w3.org
• [Bug 8015] "skip all White_Space characters" - should xref to "skip White_Space characters" bugzilla@wiggum.w3.org
• [Bug 8014] "the character immediately after the last one examined by the sub-algorithm" - what does 'examined' mean? To find the number in "123XY" it has to examine the X, so is that counted? Probably should say "after the last one matched" instead bugzilla@wiggum.w3.org
• [Bug 8014] "the character immediately after the last one examined by the sub-algorithm" - what does 'examined' mean? To find the number in "123XY" it has to examine the X, so is that counted? Probably should say "after the last one matched" instead bugzilla@wiggum.w3.org
• [Bug 8013] "string is guaranteed to be a valid floating point number" - no it's not - it could be "0." which is not valid bugzilla@wiggum.w3.org
• [Bug 8013] "string is guaranteed to be a valid floating point number" - no it's not - it could be "0." which is not valid bugzilla@wiggum.w3.org
• [Bug 8012] This says "Collect a sequence of characters ... interpret the resulting sequence as a base-ten integer", whereas the signed and unsigned integers had a whole five-step loop to do precisely the same thing. They should all use the simpler phrasing, since it bugzilla@wiggum.w3.org
• [Bug 8012] This says "Collect a sequence of characters ... interpret the resulting sequence as a base-ten integer", whereas the signed and unsigned integers had a whole five-step loop to do precisely the same thing. They should all use the simpler phrasing, since it bugzilla@wiggum.w3.org
• [Bug 8011] ECMAScript says the result of ToString on Number is not uniquely determined (in the last digit of s), but HTML5 makes it sound like there's a single best representation of any number. It should explicitly note that the best representation may be any one o bugzilla@wiggum.w3.org
• [Bug 8011] ECMAScript says the result of ToString on Number is not uniquely determined (in the last digit of s), but HTML5 makes it sound like there's a single best representation of any number. It should explicitly note that the best representation may be any one o bugzilla@wiggum.w3.org
• [Bug 8010] A valid floating point number was defined as a string, and I'd assume valid ones are a subset of all floating point numbers, so this is the best representation of a string. Applying ToString to a string isn't very interesting. It needs to be clear that it bugzilla@wiggum.w3.org
• [Bug 8010] A valid floating point number was defined as a string, and I'd assume valid ones are a subset of all floating point numbers, so this is the best representation of a string. Applying ToString to a string isn't very interesting. It needs to be clear that it bugzilla@wiggum.w3.org
• [Bug 8009] "Add the value of the current character" - is the 'current character' the same as the 'next character'? Why use a different term? Seems better to be consistent. (Same for signed integers) bugzilla@wiggum.w3.org
• [Bug 8009] "Add the value of the current character" - is the 'current character' the same as the 'next character'? Why use a different term? Seems better to be consistent. (Same for signed integers) bugzilla@wiggum.w3.org
• [Bug 8008] The plus-sign case fails to say "If position is past the end of input, return an error" after it advances position, and so the next character used in step 8 may be undefined bugzilla@wiggum.w3.org
• [Bug 8008] The plus-sign case fails to say "If position is past the end of input, return an error" after it advances position, and so the next character used in step 8 may be undefined bugzilla@wiggum.w3.org
• [Bug 8007] The step that skips "+" does not say '(The "+" is ignored, but it is not conforming.)', whereas the rules for signed integers do say that (and it seems a helpful comment) bugzilla@wiggum.w3.org
• [Bug 7998] "any of the DOM and WebAPI specifications" - what's a WebAPI specification? (Presumably this refers to Web IDL, but I can only tell that by looking at the Web IDL spec's URL in the references section, so it's not very clear.) bugzilla@wiggum.w3.org
• [Bug 7997] "if it matches the media-type token" - s/token/rule/ (to use the correct ABNF terminology) bugzilla@wiggum.w3.org
• [Bug 8000] ARIA roles added to the a element should be conforming in HTML5 bugzilla@wiggum.w3.org
• [Bug 8003] line breaks in attributes (especially title) bugzilla@wiggum.w3.org
• [Bug 8005] For control and permanently undefined characters no action is given: Whould they be replaced my fffd? bugzilla@wiggum.w3.org
• [Bug 7998] "any of the DOM and WebAPI specifications" - what's a WebAPI specification? (Presumably this refers to Web IDL, but I can only tell that by looking at the Web IDL spec's URL in the references section, so it's not very clear.) bugzilla@wiggum.w3.org
• [Bug 8007] The step that skips "+" does not say '(The "+" is ignored, but it is not conforming.)', whereas the rules for signed integers do say that (and it seems a helpful comment) bugzilla@wiggum.w3.org
• [Bug 7997] "if it matches the media-type token" - s/token/rule/ (to use the correct ABNF terminology) bugzilla@wiggum.w3.org
• [Bug 7996] "any MIME type ending with the four characters "+xml"" - even the 'valid MIME type' "text/html; charset=utf8+xml", and not "application/xhtml+xml; charset=utf8"? Probably this should require the MIME type's *subtype* to end with +xml bugzilla@wiggum.w3.org
• [Bug 7996] "any MIME type ending with the four characters "+xml"" - even the 'valid MIME type' "text/html; charset=utf8+xml", and not "application/xhtml+xml; charset=utf8"? Probably this should require the MIME type's *subtype* to end with +xml bugzilla@wiggum.w3.org
• [Bug 7995] "The attribute value can be left unquoted if it doesn't contain any of " ' ` = < or >." - should also mention space characters bugzilla@wiggum.w3.org
• [Bug 7995] "The attribute value can be left unquoted if it doesn't contain any of " ' ` = < or >." - should also mention space characters bugzilla@wiggum.w3.org
• [Bug 7994] afdasfasdf bugzilla@wiggum.w3.org
• [Bug 7993] "areas that are out of scope" - dead link to deleted section #no bugzilla@wiggum.w3.org
• [Bug 7993] "areas that are out of scope" - dead link to deleted section #no bugzilla@wiggum.w3.org
• [Bug 7992] Original insertion mode concept doesn't work well when SVG with HTML content embedded in non-body context bugzilla@wiggum.w3.org
• [Bug 7992] Original insertion mode concept doesn't work well when SVG with HTML content embedded in non-body context bugzilla@wiggum.w3.org
• [Bug 7991] "This specification ... include ... a full duplex client-server communication channel" - I assume that refers to Web Sockets, which is no longer included in this spec bugzilla@wiggum.w3.org
• [Bug 7978] Form foster parenting introduces extra space to layout bugzilla@wiggum.w3.org
• [Bug 7978] Form foster parenting introduces extra space to layout bugzilla@wiggum.w3.org

Thursday, 22 October 2009

• [Bug 8003] line breaks in attributes (especially title) bugzilla@wiggum.w3.org
• [Bug 7964] Either change the "properties of an item" algorithm to be tree-order or HTMLPropertyCollection.values to be algorithm-order bugzilla@wiggum.w3.org
• [Bug 8016] New: anything bugzilla@wiggum.w3.org
• [Bug 8015] New: "skip all White_Space characters" - should xref to "skip White_Space characters" bugzilla@wiggum.w3.org
• [Bug 8014] New: "the character immediately after the last one examined by the sub-algorithm" - what does 'examined' mean? To find the number in "123XY" it has to examine the X, so is that counted? Probably should say "after the last one matched" instead bugzilla@wiggum.w3.org
• [Bug 8013] New: "string is guaranteed to be a valid floating point number" - no it's not - it could be "0." which is not valid bugzilla@wiggum.w3.org
• [Bug 8012] New: This says "Collect a sequence of characters ... interpret the resulting sequence as a base-ten integer", whereas the signed and unsigned integers had a whole five-step loop to do precisely the same thing. They should all use the simpler phrasing, since it bugzilla@wiggum.w3.org
• [Bug 8011] New: ECMAScript says the result of ToString on Number is not uniquely determined (in the last digit of s), but HTML5 makes it sound like there's a single best representation of any number. It should explicitly note that the best representation may be any one o bugzilla@wiggum.w3.org
• [Bug 8010] New: A valid floating point number was defined as a string, and I'd assume valid ones are a subset of all floating point numbers, so this is the best representation of a string. Applying ToString to a string isn't very interesting. It needs to be clear that it bugzilla@wiggum.w3.org
• [Bug 8009] New: "Add the value of the current character" - is the 'current character' the same as the 'next character'? Why use a different term? Seems better to be consistent. (Same for signed integers) bugzilla@wiggum.w3.org
• [Bug 8008] New: The plus-sign case fails to say "If position is past the end of input, return an error" after it advances position, and so the next character used in step 8 may be undefined bugzilla@wiggum.w3.org
• [Bug 8007] New: The step that skips "+" does not say '(The "+" is ignored, but it is not conforming.)', whereas the rules for signed integers do say that (and it seems a helpful comment) bugzilla@wiggum.w3.org
• [Bug 7806] atom ID element generation for feed entries bugzilla@wiggum.w3.org
• [Bug 7806] atom ID element generation for feed entries bugzilla@wiggum.w3.org
• [Bug 7806] atom ID element generation for feed entries bugzilla@wiggum.w3.org
• [Bug 8005] New: For control and permanently undefined characters no action is given: Whould they be replaced my fffd? bugzilla@wiggum.w3.org
• [Bug 7868] what about time zones? which one is used? local (may be difficult to find out)? is this communicated to the user? can he change it? bugzilla@wiggum.w3.org
• [Bug 7806] atom ID element generation for feed entries bugzilla@wiggum.w3.org
• [Bug 8003] New: line breaks in attributes (especially title) bugzilla@wiggum.w3.org
• [Bug 7868] what about time zones? which one is used? local (may be difficult to find out)? is this communicated to the user? can he change it? bugzilla@wiggum.w3.org
• [Bug 7806] atom ID element generation for feed entries bugzilla@wiggum.w3.org
• [Bug 7806] atom ID element generation for feed entries bugzilla@wiggum.w3.org
• [Bug 7868] what about time zones? which one is used? local (may be difficult to find out)? is this communicated to the user? can he change it? bugzilla@wiggum.w3.org
• [Bug 7806] atom ID element generation for feed entries bugzilla@wiggum.w3.org
• [Bug 7868] what about time zones? which one is used? local (may be difficult to find out)? is this communicated to the user? can he change it? bugzilla@wiggum.w3.org
• [Bug 7973] atom ID format bugzilla@wiggum.w3.org
• [Bug 7973] atom ID format bugzilla@wiggum.w3.org
• [Bug 7868] what about time zones? which one is used? local (may be difficult to find out)? is this communicated to the user? can he change it? bugzilla@wiggum.w3.org
• [Bug 7973] atom ID format bugzilla@wiggum.w3.org
• [Bug 7992] Original insertion mode concept doesn't work well when SVG with HTML content embedded in non-body context bugzilla@wiggum.w3.org
• [Bug 8000] ARIA roles added to the a element should be conforming in HTML5 bugzilla@wiggum.w3.org
• [Bug 7868] what about time zones? which one is used? local (may be difficult to find out)? is this communicated to the user? can he change it? bugzilla@wiggum.w3.org

Wednesday, 21 October 2009

• [Bug 7868] what about time zones? which one is used? local (may be difficult to find out)? is this communicated to the user? can he change it? bugzilla@wiggum.w3.org
• [Bug 7868] what about time zones? which one is used? local (may be difficult to find out)? is this communicated to the user? can he change it? bugzilla@wiggum.w3.org
• [Bug 7973] atom ID format bugzilla@wiggum.w3.org
• [Bug 7953] s/must be performd/must be performed/ bugzilla@wiggum.w3.org
• [Bug 7868] what about time zones? which one is used? local (may be difficult to find out)? is this communicated to the user? can he change it? bugzilla@wiggum.w3.org
• [Bug 8000] New: ARIA roles added to the a element should be conforming in HTML5 bugzilla@wiggum.w3.org
• [Bug 7998] New: "any of the DOM and WebAPI specifications" - what's a WebAPI specification? (Presumably this refers to Web IDL, but I can only tell that by looking at the Web IDL spec's URL in the references section, so it's not very clear.) bugzilla@wiggum.w3.org
• [Bug 7997] New: "if it matches the media-type token" - s/token/rule/ (to use the correct ABNF terminology) bugzilla@wiggum.w3.org
• [Bug 7996] New: "any MIME type ending with the four characters "+xml"" - even the 'valid MIME type' "text/html; charset=utf8+xml", and not "application/xhtml+xml; charset=utf8"? Probably this should require the MIME type's *subtype* to end with +xml bugzilla@wiggum.w3.org
• [Bug 7973] atom ID format bugzilla@wiggum.w3.org
• [Bug 7995] New: "The attribute value can be left unquoted if it doesn't contain any of " ' ` = < or >." - should also mention space characters bugzilla@wiggum.w3.org
• [Bug 7994] New: afdasfasdf bugzilla@wiggum.w3.org
• [Bug 7868] what about time zones? which one is used? local (may be difficult to find out)? is this communicated to the user? can he change it? bugzilla@wiggum.w3.org
• [Bug 7993] New: "areas that are out of scope" - dead link to deleted section #no bugzilla@wiggum.w3.org
• [Bug 7992] New: Original insertion mode concept doesn't work well when SVG with HTML content embedded in non-body context bugzilla@wiggum.w3.org
• [Bug 7991] New: "This specification ... include ... a full duplex client-server communication channel" - I assume that refers to Web Sockets, which is no longer included in this spec bugzilla@wiggum.w3.org
• [Bug 7978] Form foster parenting introduces extra space to layout bugzilla@wiggum.w3.org
• [Bug 7964] Either change the "properties of an item" algorithm to be tree-order or HTMLPropertyCollection.values to be algorithm-order bugzilla@wiggum.w3.org
• [Bug 7978] Form foster parenting introduces extra space to layout bugzilla@wiggum.w3.org
• [Bug 7990] Add itemref interface bugzilla@wiggum.w3.org
• [Bug 7990] Add itemref interface bugzilla@wiggum.w3.org
• [Bug 7989] nextid, rb and spacer should use HTMLUnknownElement (like isindex) bugzilla@wiggum.w3.org
• [Bug 7989] nextid, rb and spacer should use HTMLUnknownElement (like isindex) bugzilla@wiggum.w3.org
• [Bug 7988] Remove "spacer". IE, WebKit and Opera parse it as a normal unknown element bugzilla@wiggum.w3.org
• [Bug 7988] Remove "spacer". IE, WebKit and Opera parse it as a normal unknown element bugzilla@wiggum.w3.org
• [Bug 7987] Clean up load() bugzilla@wiggum.w3.org
• [Bug 7981] s/restrictiosn/restrictions/ bugzilla@wiggum.w3.org
• [Bug 7978] Form foster parenting introduces extra space to layout bugzilla@wiggum.w3.org
• [Bug 7981] s/restrictiosn/restrictions/ bugzilla@wiggum.w3.org
• [Bug 7980] "presented by" should be "represented here by" bugzilla@wiggum.w3.org
• [Bug 7980] "presented by" should be "represented here by" bugzilla@wiggum.w3.org
• [Bug 7868] what about time zones? which one is used? local (may be difficult to find out)? is this communicated to the user? can he change it? bugzilla@wiggum.w3.org
• [Bug 7979] "special characters" is unnecessarily vague -- refer to delimiters bugzilla@wiggum.w3.org
• [Bug 7979] "special characters" is unnecessarily vague -- refer to delimiters bugzilla@wiggum.w3.org
• [Bug 7978] Form foster parenting introduces extra space to layout bugzilla@wiggum.w3.org
• [Bug 7977] Define whether application/octet-stream with parameters is a type that the user agent knows it cannot render bugzilla@wiggum.w3.org
• [Bug 7977] Define whether application/octet-stream with parameters is a type that the user agent knows it cannot render bugzilla@wiggum.w3.org
• [Bug 7974] Please explain what the use case is for the 'emptied' event or drop the event from the spec bugzilla@wiggum.w3.org
• [Bug 7868] what about time zones? which one is used? local (may be difficult to find out)? is this communicated to the user? can he change it? bugzilla@wiggum.w3.org
• [Bug 7973] atom ID format bugzilla@wiggum.w3.org
• [Bug 7868] what about time zones? which one is used? local (may be difficult to find out)? is this communicated to the user? can he change it? bugzilla@wiggum.w3.org
• [Bug 7972] It appears that the steps listed for what to do when reset() is invoked contain a race condition unless step 1 (checking if already marked) and step 2 (marking the form as locked) are performed atomically together. bugzilla@wiggum.w3.org
• [Bug 7971] <base> UA requirements (determining base URL of a Document object) bugzilla@wiggum.w3.org
• [Bug 7971] <base> UA requirements (determining base URL of a Document object) bugzilla@wiggum.w3.org
• [Bug 7868] what about time zones? which one is used? local (may be difficult to find out)? is this communicated to the user? can he change it? bugzilla@wiggum.w3.org
• [Bug 7965] "ASCII case-sensitive" in "Markup declaration open state" is a broken xref bugzilla@wiggum.w3.org
• [Bug 7965] "ASCII case-sensitive" in "Markup declaration open state" is a broken xref bugzilla@wiggum.w3.org
• [Bug 7868] what about time zones? which one is used? local (may be difficult to find out)? is this communicated to the user? can he change it? bugzilla@wiggum.w3.org
• [Bug 7868] what about time zones? which one is used? local (may be difficult to find out)? is this communicated to the user? can he change it? bugzilla@wiggum.w3.org
• [Bug 7964] Either change the "properties of an item" algorithm to be tree-order or HTMLPropertyCollection.values to be algorithm-order bugzilla@wiggum.w3.org
• [Bug 7963] 11. "Otherwise, if current is not a refid element" should be an itemref element. bugzilla@wiggum.w3.org
• [Bug 7990] New: Add itemref interface bugzilla@wiggum.w3.org
• [Bug 7964] Either change the "properties of an item" algorithm to be tree-order or HTMLPropertyCollection.values to be algorithm-order bugzilla@wiggum.w3.org
• [Bug 7962] s/<span>last event ID string</span>/<span title="concept-event-stream-last-event-id">last event ID string</span>/g bugzilla@wiggum.w3.org
• [Bug 7963] 11. "Otherwise, if current is not a refid element" should be an itemref element. bugzilla@wiggum.w3.org
• [Bug 7962] s/<span>last event ID string</span>/<span title="concept-event-stream-last-event-id">last event ID string</span>/g bugzilla@wiggum.w3.org
• [Bug 7960] s/<span title="absolute URLs">absolute URL</span>/<span title="absolute URL">absolute URLs</span>/ bugzilla@wiggum.w3.org
• [Bug 7959] s/<span>editing hosts</span>/<span title="editing-host">editing hosts</span>/ bugzilla@wiggum.w3.org
• [Bug 7961] "script execution context" isn't defined bugzilla@wiggum.w3.org
• [Bug 7960] s/<span title="absolute URLs">absolute URL</span>/<span title="absolute URL">absolute URLs</span>/ bugzilla@wiggum.w3.org
• [Bug 7958] "(end-1)th position": add title="" bugzilla@wiggum.w3.org
• [Bug 7959] s/<span>editing hosts</span>/<span title="editing-host">editing hosts</span>/ bugzilla@wiggum.w3.org
• [Bug 7958] "(end-1)th position": add title="" bugzilla@wiggum.w3.org
• [Bug 7957] [Webstorage] s/<span>browsing contexts</span>/<span title="browsing-context">browsing contexts</span>/ bugzilla@wiggum.w3.org
• [Bug 7957] [Webstorage] s/<span>browsing contexts</span>/<span title="browsing-context">browsing contexts</span>/ bugzilla@wiggum.w3.org
• [Bug 7956] It is not obvious if or how a caption can be placed below a table instead of above the table. This section might benefit from a sentence or two clarifying that. bugzilla@wiggum.w3.org
• [Bug 7954] s/<span>valid URLs</span>/<span title="valid-url">valid URLs</span>/ bugzilla@wiggum.w3.org
• [Bug 7926] Undefine insertion point if parser on call stack doing anything other than running script element bugzilla@wiggum.w3.org
• [Bug 7953] s/must be performd/must be performed/ bugzilla@wiggum.w3.org
• [Bug 7926] Undefine insertion point if parser on call stack doing anything other than running script element bugzilla@wiggum.w3.org
• [Bug 7952] s/<span>same</span>/same/ bugzilla@wiggum.w3.org
• [Bug 7951] First example: http://example.com/jon/ & http://example.com/~jon/ are used bugzilla@wiggum.w3.org
• [Bug 7952] s/<span>same</span>/same/ bugzilla@wiggum.w3.org
• [Bug 7951] First example: http://example.com/jon/ & http://example.com/~jon/ are used bugzilla@wiggum.w3.org
• [Bug 7949] This should be marked as a willful violation to RFC 2616 where missing of the charset parameter is interpreted as iso-8859-1 bugzilla@wiggum.w3.org
• [Bug 7950] xref "offline application cache" bugzilla@wiggum.w3.org
• [Bug 7949] This should be marked as a willful violation to RFC 2616 where missing of the charset parameter is interpreted as iso-8859-1 bugzilla@wiggum.w3.org
• [Bug 7948] [RFC2781] should be referenced in the third Note? bugzilla@wiggum.w3.org
• [Bug 7941] document.getItems should be restricted to HTMLDocument in DOM intro box, as it does not apply to other types of documents. bugzilla@wiggum.w3.org
• [Bug 7948] [RFC2781] should be referenced in the third Note? bugzilla@wiggum.w3.org
• [Bug 7947] s/script's global scope/script's global object/g, s/script browsing context/script's browsing context/g bugzilla@wiggum.w3.org
• [Bug 7947] s/script's global scope/script's global object/g, s/script browsing context/script's browsing context/g bugzilla@wiggum.w3.org
• [Bug 7947] s/script's global scope/script's global object/g, s/script browsing context/script's browsing context/g bugzilla@wiggum.w3.org
• [Bug 7942] It's not defined what happens when properties is set. Throw INVALID_ACCESS_ERR? bugzilla@wiggum.w3.org
• [Bug 7946] Ping-From, Ping-To: wrong heading level or in the wrong section bugzilla@wiggum.w3.org
• [Bug 7945] Add a reference to [PROGRESS] here, or make |progress| a simple event (twice) bugzilla@wiggum.w3.org
• [Bug 7942] It's not defined what happens when properties is set. Throw INVALID_ACCESS_ERR? bugzilla@wiggum.w3.org
• [Bug 7941] document.getItems should be restricted to HTMLDocument in DOM intro box, as it does not apply to other types of documents. bugzilla@wiggum.w3.org
• [Bug 7940] Under "content model", it isn't clear what the significance of the italic "or" is. If it is intended to signify a higher precidence "or", consider using bullet points to clarify the nesting of conjuctions. bugzilla@wiggum.w3.org
• [Bug 7940] Under "content model", it isn't clear what the significance of the italic "or" is. If it is intended to signify a higher precidence "or", consider using bullet points to clarify the nesting of conjuctions. bugzilla@wiggum.w3.org
• [Bug 7939] stalled is a simple event according to the resource fetch algorithm in 4.8.10.5 Loading the media resource bugzilla@wiggum.w3.org
• [Bug 7937] er might return the document with one paragraph modified as follows: <p>I also have some <mark>kitten</mark>s who are visiting me these days. They're really cute. I think they like my garden! Maybe I should adopt a <mark>kitten</mark>.</p> bugzilla@wiggum.w3.org
• [Bug 7936] Consider https://bugzilla.mozilla.org/show_bug.cgi?id=521670 bugzilla@wiggum.w3.org
• [Bug 7932] element.properties says "If the element has an item attribute". The item attribute is now called itemscope. bugzilla@wiggum.w3.org
• [Bug 7931] The "loop" label in the 'A start tag whose tag name is "li"' is misplaced, or there is something else wrong that is making the loop useless. bugzilla@wiggum.w3.org
• [Bug 7931] The "loop" label in the 'A start tag whose tag name is "li"' is misplaced, or there is something else wrong that is making the loop useless. bugzilla@wiggum.w3.org
• [Bug 7926] Undefine insertion point if parser on call stack doing anything other than running script element bugzilla@wiggum.w3.org
• [Bug 7924] xaXAafs bugzilla@wiggum.w3.org
• [Bug 7923] What about local files access? bugzilla@wiggum.w3.org
• [Bug 7920] media queries ref bugzilla@wiggum.w3.org
• [Bug 7918] prefetching: allow site to deny bugzilla@wiggum.w3.org
• [Bug 7917] document.close() should attempt to tokenize bugzilla@wiggum.w3.org
• [Bug 7917] document.close() should attempt to tokenize bugzilla@wiggum.w3.org
• [Bug 7915] “itemref” element is missing, <http://www.whatwg.org/specs/web-apps/current-work/multipage/semantics.html#itemref> bugzilla@wiggum.w3.org
• [Bug 7910] Since IANA considerations is an appendix, its subsections should be marked as such as well. bugzilla@wiggum.w3.org
• [Bug 7978] Form foster parenting introduces extra space to layout bugzilla@wiggum.w3.org
• [Bug 7914] step. 6 should say "object" not "array", right? i.e. "whose value is the object _properties_" bugzilla@wiggum.w3.org
• [Bug 7914] step. 6 should say "object" not "array", right? i.e. "whose value is the object _properties_" bugzilla@wiggum.w3.org
• [Bug 7806] atom ID element generation for feed entries bugzilla@wiggum.w3.org
• [Bug 7806] atom ID element generation for feed entries bugzilla@wiggum.w3.org
• [Bug 7910] Since IANA considerations is an appendix, its subsections should be marked as such as well. bugzilla@wiggum.w3.org
• [Bug 7909] It seems like this is a subsection of the wrong section. Either it should just be a level up or it should be moved up one section. bugzilla@wiggum.w3.org
• [Bug 7989] New: nextid, rb and spacer should use HTMLUnknownElement (like isindex) bugzilla@wiggum.w3.org
• [Bug 7910] Since IANA considerations is an appendix, its subsections should be marked as such as well. bugzilla@wiggum.w3.org
• [Bug 7909] It seems like this is a subsection of the wrong section. Either it should just be a level up or it should be moved up one section. bugzilla@wiggum.w3.org
• [Bug 7988] New: Remove "spacer". IE, WebKit and Opera parse it as a normal unknown element bugzilla@wiggum.w3.org
• [Bug 7908] the item attribute is gone, DOM intro box for element.properties needs to be updated bugzilla@wiggum.w3.org
• [Bug 7908] the item attribute is gone, DOM intro box for element.properties needs to be updated bugzilla@wiggum.w3.org
• [Bug 7906] The venn diagram is all black in the PDF copy bugzilla@wiggum.w3.org
• [Bug 7862] Support Extended Processing Behavior via @profile/@version bugzilla@wiggum.w3.org
• [Bug 7905] Markup in second example has formatting broken - titlecase on tags and > creating line breaks bugzilla@wiggum.w3.org
• [Bug 7898] Maybe this section should cover all elements and attributes historically allowed by IETF standards and W3C Recommendations but no longer allowed, such as <rb> and <a urn> for consistency bugzilla@wiggum.w3.org
• [Bug 7898] Maybe this section should cover all elements and attributes historically allowed by IETF standards and W3C Recommendations but no longer allowed, such as <rb> and <a urn> for consistency bugzilla@wiggum.w3.org
• [Bug 7862] Support Extended Processing Behavior via @profile/@version bugzilla@wiggum.w3.org
• [Bug 7896] Specify pageshow and pagehide events bugzilla@wiggum.w3.org
• [Bug 7897] One can argue that "Any (namespace-less) attribute may be specified ..." contradicts with obsolete feature section where use of some attributes is disallowed bugzilla@wiggum.w3.org
• [Bug 7897] One can argue that "Any (namespace-less) attribute may be specified ..." contradicts with obsolete feature section where use of some attributes is disallowed bugzilla@wiggum.w3.org
• [Bug 7862] Support Extended Processing Behavior via @profile/@version bugzilla@wiggum.w3.org
• [Bug 7806] atom ID element generation for feed entries 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 7862] Support Extended Processing Behavior via @profile/@version bugzilla@wiggum.w3.org
• [Bug 7895] In step 6, it should be allowed (and clear that it is allowed) for UAs to use additional data such as the site TLD to guess the correct encoding bugzilla@wiggum.w3.org
• [Bug 7895] In step 6, it should be allowed (and clear that it is allowed) for UAs to use additional data such as the site TLD to guess the correct encoding bugzilla@wiggum.w3.org
• [Bug 7893] In the example <div id="b" itemprop="band" itemscope id="jazzband"> the div element has two id attributes. Is this desirable? bugzilla@wiggum.w3.org
• [Bug 7892] typo bugzilla@wiggum.w3.org
• [Bug 7893] In the example <div id="b" itemprop="band" itemscope id="jazzband"> the div element has two id attributes. Is this desirable? bugzilla@wiggum.w3.org
• [Bug 7890] "When no more character are": s/character/characters/ bugzilla@wiggum.w3.org
• [Bug 7892] typo bugzilla@wiggum.w3.org
• [Bug 7889] audio, canvas and video are missing bugzilla@wiggum.w3.org
• [Bug 7890] "When no more character are": s/character/characters/ bugzilla@wiggum.w3.org
• [Bug 7889] audio, canvas and video are missing bugzilla@wiggum.w3.org
• [Bug 7888] s/Computer input/User input/ bugzilla@wiggum.w3.org
• [Bug 7888] s/Computer input/User input/ bugzilla@wiggum.w3.org
• [Bug 7886] Drop applet, marquee bugzilla@wiggum.w3.org
• [Bug 7886] Drop applet, marquee bugzilla@wiggum.w3.org
• [Bug 7885] "…the element does not have an async attribute, or": s/, or// bugzilla@wiggum.w3.org
• [Bug 7883] s/defind/defined/ bugzilla@wiggum.w3.org
• [Bug 7883] s/defind/defined/ bugzilla@wiggum.w3.org
• [Bug 7884] s/defind/defined/ bugzilla@wiggum.w3.org
• [Bug 7883] s/defind/defined/ bugzilla@wiggum.w3.org
• [Bug 7977] Define whether application/octet-stream with parameters is a type that the user agent knows it cannot render bugzilla@wiggum.w3.org
• [Bug 7978] Form foster parenting introduces extra space to layout bugzilla@wiggum.w3.org
• [Bug 7882] 'message' events has a different interface than it says in the index bugzilla@wiggum.w3.org
• [Bug 7881] 'undo', 'redo' events have a different interface than it says in the index bugzilla@wiggum.w3.org
• [Bug 7882] 'message' events has a different interface than it says in the index bugzilla@wiggum.w3.org
• [Bug 7881] 'undo', 'redo' events have a different interface than it says in the index bugzilla@wiggum.w3.org
• [Bug 7880] 'popstate' event has a different interface than it says in the index bugzilla@wiggum.w3.org
• [Bug 7880] 'popstate' event has a different interface than it says in the index bugzilla@wiggum.w3.org
• [Bug 7879] 'unload' event has a different interface than it says in the index bugzilla@wiggum.w3.org
• [Bug 7879] 'unload' event has a different interface than it says in the index bugzilla@wiggum.w3.org
• [Bug 7877] A media.stop() method would be advantageous, having just pause does restrict the bounds of use especially for media players on a website. bugzilla@wiggum.w3.org
• [Bug 7876] "A synchronous section never mutates the DOM, runs any script, or have any other side-effects." should say "has any other". bugzilla@wiggum.w3.org
• [Bug 7876] "A synchronous section never mutates the DOM, runs any script, or have any other side-effects." should say "has any other". bugzilla@wiggum.w3.org
• [Bug 7862] Support Extended Processing Behavior via @profile/@version bugzilla@wiggum.w3.org
• [Bug 7875] term: a "range" is an interval between two numbers, e.g. 2-4 or 1969-2032. the term "range" does not mean "imprecise number". bugzilla@wiggum.w3.org

Tuesday, 20 October 2009

• [Bug 7872] I have no idea how a "search field" would look like, on any platform. describe. bugzilla@wiggum.w3.org
• [Bug 7871] there's more meaning to a password field than just being obstructed. it's really only for passwords / credentials. firefox stores them in the password manager, for example, meaning FF really gives it the meaning "password", not just "obstructed". the defi bugzilla@wiggum.w3.org
• [Bug 7869] complicated calculation given, but not clearly (only implicitly) stating the obvious question: which day does the week start with? I strongly feel it's Monday, but other people/cultures disagree, I think. bugzilla@wiggum.w3.org
• [Bug 7870] how does a user enter a "week"? calendar widget? how would he enter it as text? bugzilla@wiggum.w3.org
• [Bug 7869] complicated calculation given, but not clearly (only implicitly) stating the obvious question: which day does the week start with? I strongly feel it's Monday, but other people/cultures disagree, I think. bugzilla@wiggum.w3.org
• [Bug 7868] what about time zones? which one is used? local (may be difficult to find out)? is this communicated to the user? can he change it? bugzilla@wiggum.w3.org
• [Bug 7806] atom ID element generation for feed entries bugzilla@wiggum.w3.org
• [Bug 7967] ertertert bugzilla@wiggum.w3.org
• [Bug 7867] How should a browser render this? Give examples for "typical" or "good" implementations, maybe even for different device types. Should specify that a desktop browser should give a calendar widget, because airlines etc. want that (implement it in JS, but b bugzilla@wiggum.w3.org
• [Bug 7865] BenB wants an example of use of datetime-local, e.g. "What time should your event start", with no timezone information, so that the site can keep the event starting at that time in the user's time zone regardless of what time zone the user moves to by the bugzilla@wiggum.w3.org
• [Bug 7865] BenB wants an example of use of datetime-local, e.g. "What time should your event start", with no timezone information, so that the site can keep the event starting at that time in the user's time zone regardless of what time zone the user moves to by the bugzilla@wiggum.w3.org
• [Bug 7862] Support Extended Processing Behavior via @profile/@version bugzilla@wiggum.w3.org
• [Bug 7987] New: Clean up load() bugzilla@wiggum.w3.org
• [Bug 7862] Support Extended Processing Behavior via @profile/@version bugzilla@wiggum.w3.org
• [Bug 7862] Support Extended Processing Behavior via @profile/@version bugzilla@wiggum.w3.org
• [Bug 7806] atom ID element generation for feed entries bugzilla@wiggum.w3.org
• [Bug 7861] requirements for meta/http-equiv extensions bugzilla@wiggum.w3.org
• [Bug 7859] Mention under step 1 that it can also be aborted if the user agent has discovered that there is no network available and therefore cannot perform HTTP requests. This prevents dispatching error events when the user is using the application offline. bugzilla@wiggum.w3.org
• [Bug 7859] Mention under step 1 that it can also be aborted if the user agent has discovered that there is no network available and therefore cannot perform HTTP requests. This prevents dispatching error events when the user is using the application offline. bugzilla@wiggum.w3.org
• [Bug 7843] Please make 'abort', ' loadend' and 'emptied' use "queue a task". Firing them sync is annoying to implement and doesn't seem to solve any problem. bugzilla@wiggum.w3.org
• [Bug 7843] Please make 'abort', ' loadend' and 'emptied' use "queue a task". Firing them sync is annoying to implement and doesn't seem to solve any problem. bugzilla@wiggum.w3.org
• [Bug 7806] atom ID element generation for feed entries bugzilla@wiggum.w3.org
• [Bug 7981] New: s/restrictiosn/restrictions/ bugzilla@wiggum.w3.org
• [Bug 7980] New: "presented by" should be "represented here by" bugzilla@wiggum.w3.org
• [Bug 7979] New: "special characters" is unnecessarily vague -- refer to delimiters bugzilla@wiggum.w3.org
• [Bug 7806] atom ID element generation for feed entries bugzilla@wiggum.w3.org
• [Bug 7978] New: Form foster parenting introduces extra space to layout bugzilla@wiggum.w3.org
• [Bug 7977] New: Define whether application/octet-stream with parameters is a type that the user agent knows it cannot render bugzilla@wiggum.w3.org
• [Bug 7848] MathML version used in HTML5 bugzilla@wiggum.w3.org
• [Bug 7806] atom ID element generation for feed entries bugzilla@wiggum.w3.org
• [Bug 7858] All the current entries should merge into one current entry in the joint session history. (imagine a series of nested iframes that haven't been navigated, and call go(-1)... it should go back at the top-level, not do something weird with the iframes) bugzilla@wiggum.w3.org
• [Bug 7858] All the current entries should merge into one current entry in the joint session history. (imagine a series of nested iframes that haven't been navigated, and call go(-1)... it should go back at the top-level, not do something weird with the iframes) bugzilla@wiggum.w3.org
• [Bug 7843] Please make 'abort', ' loadend' and 'emptied' use "queue a task". Firing them sync is annoying to implement and doesn't seem to solve any problem. bugzilla@wiggum.w3.org
• [Bug 7857] "Wait for the browsing context to be closed" should be explicit about spinning a nested event loop bugzilla@wiggum.w3.org
• [Bug 7857] "Wait for the browsing context to be closed" should be explicit about spinning a nested event loop bugzilla@wiggum.w3.org
• [Bug 7855] Define fragment parsing when the context is not an HTML, SVG or MathML node bugzilla@wiggum.w3.org
• [Bug 7843] Please make 'abort', ' loadend' and 'emptied' use "queue a task". Firing them sync is annoying to implement and doesn't seem to solve any problem. bugzilla@wiggum.w3.org
• [Bug 7842] No programmatic way to make an HTML document - consider adding createHTMLDocument bugzilla@wiggum.w3.org
• [Bug 7842] No programmatic way to make an HTML document - consider adding createHTMLDocument bugzilla@wiggum.w3.org
• [Bug 7806] atom ID element generation for feed entries bugzilla@wiggum.w3.org
• [Bug 7848] MathML version used in HTML5 bugzilla@wiggum.w3.org
• [Bug 7856] When JavaScript or <canvas> is disabled <canvas> should be treated as an ordinary element and not a replaced element. bugzilla@wiggum.w3.org
• [Bug 7856] When JavaScript or <canvas> is disabled <canvas> should be treated as an ordinary element and not a replaced element. bugzilla@wiggum.w3.org
• [Bug 7806] atom ID element generation for feed entries bugzilla@wiggum.w3.org
• [Bug 7854] "offline application cache" doesn't xref right bugzilla@wiggum.w3.org
• [Bug 7854] "offline application cache" doesn't xref right bugzilla@wiggum.w3.org
• [Bug 7852] DOM Events has dropped namespaces. Drop all init*EventNS methods. bugzilla@wiggum.w3.org
• [Bug 7852] DOM Events has dropped namespaces. Drop all init*EventNS methods. bugzilla@wiggum.w3.org
• [Bug 7851] Some (perhaps all) scripts with a for="" attribute should be ignored bugzilla@wiggum.w3.org
• [Bug 7851] Some (perhaps all) scripts with a for="" attribute should be ignored bugzilla@wiggum.w3.org
• [Bug 7849] Check whether .search should or shouldn't work with data: URLs bugzilla@wiggum.w3.org
• [Bug 7849] Check whether .search should or shouldn't work with data: URLs bugzilla@wiggum.w3.org
• [Bug 7848] MathML version used in HTML5 bugzilla@wiggum.w3.org
• [Bug 7844] Remove "that is in a Document and" when the src attribute is set and when a source is inserted, because there's no reason resource selection shouldn't be run when it's not in the document. Then we also don't have to run resource selection when inserting a bugzilla@wiggum.w3.org
• [Bug 7847] for - label - "Associatd" bugzilla@wiggum.w3.org
• [Bug 7844] Remove "that is in a Document and" when the src attribute is set and when a source is inserted, because there's no reason resource selection shouldn't be run when it's not in the document. Then we also don't have to run resource selection when inserting a bugzilla@wiggum.w3.org
• [Bug 7842] No programmatic way to make an HTML document - consider adding createHTMLDocument bugzilla@wiggum.w3.org
• [Bug 7974] New: Please explain what the use case is for the 'emptied' event or drop the event from the spec bugzilla@wiggum.w3.org
• [Bug 7806] atom ID element generation for feed entries bugzilla@wiggum.w3.org
• [Bug 7843] Please make 'abort', ' loadend' and 'emptied' use "queue a task". Firing them sync is annoying to implement and doesn't seem to solve any problem. bugzilla@wiggum.w3.org
• [Bug 7841] s/that the user agent/the user agent/ bugzilla@wiggum.w3.org
• [Bug 7842] No programmatic way to make an HTML document - consider adding createHTMLDocument bugzilla@wiggum.w3.org
• [Bug 7841] s/that the user agent/the user agent/ bugzilla@wiggum.w3.org
• [Bug 7806] atom ID element generation for feed entries bugzilla@wiggum.w3.org
• [Bug 7840] Index of attributes lacks global attributes bugzilla@wiggum.w3.org
• [Bug 7840] Index of attributes lacks global attributes bugzilla@wiggum.w3.org
• [Bug 7973] New: atom ID format bugzilla@wiggum.w3.org
• [Bug 7971] <base> UA requirements bugzilla@wiggum.w3.org
• [Bug 7806] atom ID element generation for feed entries bugzilla@wiggum.w3.org
• [Bug 7806] atom ID element generation for feed entries bugzilla@wiggum.w3.org
• [Bug 7806] atom ID element generation for feed entries bugzilla@wiggum.w3.org
• [Bug 7838] The words "boolean attribute" aren't xreffed here. bugzilla@wiggum.w3.org
• [Bug 7839] Missing (unbalanced) quotemark before "checkbox" keyword. bugzilla@wiggum.w3.org
• [Bug 7838] The words "boolean attribute" aren't xreffed here. bugzilla@wiggum.w3.org
• [Bug 7837] "space separated list" in ping="" isn't properly xreffed bugzilla@wiggum.w3.org
• [Bug 7837] "space separated list" in ping="" isn't properly xreffed bugzilla@wiggum.w3.org
• [Bug 7836] Should the name="" of a <map> be unique in the document? bugzilla@wiggum.w3.org
• [Bug 7836] Should the name="" of a <map> be unique in the document? bugzilla@wiggum.w3.org
• [Bug 7835] It's not defined what the ownerDocument should be for the created HTMLAudioElement. Similarly for new Image() and new Option() bugzilla@wiggum.w3.org
• [Bug 7835] It's not defined what the ownerDocument should be for the created HTMLAudioElement. Similarly for new Image() and new Option() bugzilla@wiggum.w3.org
• [Bug 7834] "If a new element is inserted between the two nodes that define pointer" - s/element/node/ bugzilla@wiggum.w3.org
• [Bug 7834] "If a new element is inserted between the two nodes that define pointer" - s/element/node/ bugzilla@wiggum.w3.org
• [Bug 7833] The 'demand' event should fire on the canvas whenever it's apperance may affect display. It may occur before document's 'load' event or much later. It is like image fetching from network, it should be up to the browser, when it actually fire. May be helpf bugzilla@wiggum.w3.org
• [Bug 7832] The 'for' attribute could point to a element (eg. form) to indicate progress without need for scripting. bugzilla@wiggum.w3.org
• [Bug 7831] Does the spec handle setting a drag object type, and having drop targets only respond/highlight to certain drag object types? bugzilla@wiggum.w3.org
• [Bug 7830] Does the spec handle selecting multiple objects to drag (holding shift, or command keys) bugzilla@wiggum.w3.org
• [Bug 7972] It appears that the steps listed for what to do when reset() is invoked contain a race condition unless step 1 (checking if already marked) and step 2 (marking the form as locked) are performed atomically together. bugzilla@wiggum.w3.org
• [Bug 7972] New: It appears that the steps listed for what to do when reset() is invoked contain a race condition unless step 1 (checking if already marked) and step 2 (marking the form as locked) are performed atomically together. bugzilla@wiggum.w3.org
• [Bug 7826] Should mention that <hgroup> is a valid context for <hx>. bugzilla@wiggum.w3.org
• [Bug 7826] Should mention that <hgroup> is a valid context for <hx>. bugzilla@wiggum.w3.org
• [Bug 7825] typo: "if one available" should read "if one is available" bugzilla@wiggum.w3.org
• [Bug 7824] It would be very helpful to have a brief mention here of *why* the WindowProxy object exists. bugzilla@wiggum.w3.org
• [Bug 7824] It would be very helpful to have a brief mention here of *why* the WindowProxy object exists. bugzilla@wiggum.w3.org
• [Bug 7820] s/codec parameter/codecs parameter/ twice bugzilla@wiggum.w3.org
• [Bug 7817] Last example: stray </p> bugzilla@wiggum.w3.org
• [Bug 7820] s/codec parameter/codecs parameter/ twice bugzilla@wiggum.w3.org
• [Bug 7817] Last example: stray </p> bugzilla@wiggum.w3.org
• [Bug 7816] editorial: stray colon here in author view bugzilla@wiggum.w3.org
• [Bug 7816] editorial: stray colon here in author view bugzilla@wiggum.w3.org
• [Bug 7809] The character ranges in this section should follow the conventions of other ranges. I.e. "to" instead of ".." and the name of the character directly after the Unicode code point. bugzilla@wiggum.w3.org
• [Bug 7810] Maybe it's just me, but this paragraph is unclear to me. It is too difficult to understand. What is transparent content? bugzilla@wiggum.w3.org
• [Bug 7809] The character ranges in this section should follow the conventions of other ranges. I.e. "to" instead of ".." and the name of the character directly after the Unicode code point. bugzilla@wiggum.w3.org
• [Bug 7807] term "new master" can be ambiguous bugzilla@wiggum.w3.org
• [Bug 7807] term "new master" can be ambiguous bugzilla@wiggum.w3.org
• [Bug 7806] atom ID element generation for feed entries bugzilla@wiggum.w3.org
• [Bug 7806] atom ID element generation for feed entries bugzilla@wiggum.w3.org
• [Bug 7805] The tag name of foreign elements aren't necessarily all-lowercase. bugzilla@wiggum.w3.org
• [Bug 7804] In Firefox and Safari .text returns the value of the child text nodes -- not textContent bugzilla@wiggum.w3.org
• [Bug 7804] In Firefox and Safari .text returns the value of the child text nodes -- not textContent bugzilla@wiggum.w3.org
• [Bug 7803] The title element's "value" is earlier defined to be the value of its child text nodes -- not textContent bugzilla@wiggum.w3.org
• [Bug 7803] The title element's "value" is earlier defined to be the value of its child text nodes -- not textContent bugzilla@wiggum.w3.org
• [Bug 7802] editorial: broken xref in dom-intro: s/dom-getItems()/dom-document-getItems/ bugzilla@wiggum.w3.org
• [Bug 7802] editorial: broken xref in dom-intro: s/dom-getItems()/dom-document-getItems/ bugzilla@wiggum.w3.org
• [Bug 7801] Shouldn't autofocus be included in this matrix? bugzilla@wiggum.w3.org
• [Bug 7800] title attribute: add new attr for machine-readable strings bugzilla@wiggum.w3.org
• [Bug 7706] This section should reference "matches a fallback namespace" in step 3. bugzilla@wiggum.w3.org
• [Bug 7706] This section should reference "matches a fallback namespace" in step 3. bugzilla@wiggum.w3.org
• [Bug 7689] Cache-defeating semantics are not defined bugzilla@wiggum.w3.org

Monday, 19 October 2009

• [Bug 7768] Manifest download error means obsolete or idle cache group? bugzilla@wiggum.w3.org
• [Bug 7766] Fallback namespace overlap/repetition ignored bugzilla@wiggum.w3.org
• [Bug 7766] Fallback namespace overlap/repetition ignored bugzilla@wiggum.w3.org
• [Bug 7689] Cache-defeating semantics are not defined bugzilla@wiggum.w3.org
• [Bug 7766] Fallback namespace overlap/repetition ignored bugzilla@wiggum.w3.org
• [Bug 7768] Manifest download error means obsolete or idle cache group? bugzilla@wiggum.w3.org
• [Bug 7971] New: <base> UA requirements bugzilla@wiggum.w3.org
• [Bug 7964] Either change the "properties of an item" algorithm to be tree-order or HTMLPropertyCollection.values to be algorithm-order bugzilla@wiggum.w3.org

Sunday, 18 October 2009

• [Bug 7794] IDL attribute should be refId for consistency with e.g. getElementById bugzilla@wiggum.w3.org
• [Bug 7794] IDL attribute should be refId for consistency with e.g. getElementById bugzilla@wiggum.w3.org
• [Bug 7786] change priority for online whitelist namespaces other than * bugzilla@wiggum.w3.org
• [Bug 7785] "Expiring application caches" feedback bugzilla@wiggum.w3.org
• [Bug 7785] "Expiring application caches" feedback bugzilla@wiggum.w3.org
• [Bug 7784] "cache failure steps" feedback bugzilla@wiggum.w3.org
• [Bug 7784] "cache failure steps" feedback bugzilla@wiggum.w3.org
• [Bug 7783] appcache download events bugzilla@wiggum.w3.org
• [Bug 7964] Either change the "properties of an item" algorithm to be tree-order or HTMLPropertyCollection.values to be algorithm-order bugzilla@wiggum.w3.org
• [Bug 7781] forbid duplicate online whitelist namespaces bugzilla@wiggum.w3.org
• [Bug 7782] "select an application cache" is vague bugzilla@wiggum.w3.org
• [Bug 7781] forbid duplicate online whitelist namespaces bugzilla@wiggum.w3.org
• [Bug 7964] Either change the "properties of an item" algorithm to be tree-order or HTMLPropertyCollection.values to be algorithm-order bugzilla@wiggum.w3.org
• [Bug 7780] simplify appcache terminology bugzilla@wiggum.w3.org
• [Bug 7964] New: Either change the "properties of an item" algorithm to be tree-order or HTMLPropertyCollection.values to be algorithm-order bugzilla@wiggum.w3.org
• [Bug 7779] Missing task source for application cache events bugzilla@wiggum.w3.org
• [Bug 7779] Missing task source for application cache events bugzilla@wiggum.w3.org
• [Bug 7778] "interpreted as a character encoding" is not linked to a defined algorithm bugzilla@wiggum.w3.org
• [Bug 7775] are the extra events needed when status is checking or downloading bugzilla@wiggum.w3.org
• [Bug 7645] associate printable pages and less-convenient-to-print pages with link rel value "print" bugzilla@wiggum.w3.org
• [Bug 7736] add tooltip attribute & keep title for other uses bugzilla@wiggum.w3.org
• [Bug 7963] New: 11. "Otherwise, if current is not a refid element" should be an itemref element. bugzilla@wiggum.w3.org
• [Bug 7962] New: s/<span>last event ID string</span>/<span title="concept-event-stream-last-event-id">last event ID string</span>/g bugzilla@wiggum.w3.org
• [Bug 7961] New: "script execution context" isn't defined bugzilla@wiggum.w3.org
• [Bug 7960] New: s/<span title="absolute URLs">absolute URL</span>/<span title="absolute URL">absolute URLs</span>/ bugzilla@wiggum.w3.org
• [Bug 7959] New: s/<span>editing hosts</span>/<span title="editing-host">editing hosts</span>/ bugzilla@wiggum.w3.org
• [Bug 7958] New: "(end-1)th position": add title="" bugzilla@wiggum.w3.org
• [Bug 7957] New: [Webstorage] s/<span>browsing contexts</span>/<span title="browsing-context">browsing contexts</span>/ bugzilla@wiggum.w3.org
• [Bug 7956] New: It is not obvious if or how a caption can be placed below a table instead of above the table. This section might benefit from a sentence or two clarifying that. bugzilla@wiggum.w3.org
• [Bug 7954] New: s/<span>valid URLs</span>/<span title="valid-url">valid URLs</span>/ bugzilla@wiggum.w3.org
• [Bug 7953] New: s/must be performd/must be performed/ bugzilla@wiggum.w3.org
• [Bug 7952] New: s/<span>same</span>/same/ bugzilla@wiggum.w3.org
• [Bug 7951] New: First example: http://example.com/jon/ & http://example.com/~jon/ are used bugzilla@wiggum.w3.org
• [Bug 7950] New: xref "offline application cache" bugzilla@wiggum.w3.org
• [Bug 7510] Allow elements beyond just HTML, MathML, and SVG into SVG element bugzilla@wiggum.w3.org
• [Bug 7949] New: This should be marked as a willful violation to RFC 2616 where missing of the charset parameter is interpreted as iso-8859-1 bugzilla@wiggum.w3.org
• [Bug 7948] New: [RFC2781] should be referenced in the third Note? bugzilla@wiggum.w3.org
• [Bug 7947] New: s/script's global scope/script's global object/g, s/script browsing context/script's browsing context/g bugzilla@wiggum.w3.org
• [Bug 7773] Suggestion for "Updating an application cache" bugzilla@wiggum.w3.org
• [Bug 7776] rename appcache events? bugzilla@wiggum.w3.org
• [Bug 7773] Suggestion for "Updating an application cache" bugzilla@wiggum.w3.org
• [Bug 7772] add interfaces to event summary bugzilla@wiggum.w3.org
• [Bug 7772] add interfaces to event summary bugzilla@wiggum.w3.org
• [Bug 7771] matching fallback namespaces bugzilla@wiggum.w3.org
• [Bug 7771] matching fallback namespaces bugzilla@wiggum.w3.org
• [Bug 7768] Manifest download error means obsolete or idle cache group? bugzilla@wiggum.w3.org
• [Bug 7767] Atomic update of application cache is not well-defined bugzilla@wiggum.w3.org
• [Bug 7765] Maybe progress should be named fetchcachefile or some such bugzilla@wiggum.w3.org
• [Bug 7752] Please use "URL character encoding" instead of just "character encoding" for clarity bugzilla@wiggum.w3.org
• [Bug 7752] Please use "URL character encoding" instead of just "character encoding" for clarity bugzilla@wiggum.w3.org
• [Bug 7736] add tooltip attribute & keep title for other uses bugzilla@wiggum.w3.org
• [Bug 7721] Drag and Drop is not keyboard accessible bugzilla@wiggum.w3.org
• [Bug 7711] The "strong native semantics" are worded very similarly -- but not quite the same -- for input type=Number, input type=range, and progressbar. bugzilla@wiggum.w3.org
• [Bug 7689] Cache-defeating semantics are not defined bugzilla@wiggum.w3.org
• [Bug 7645] associate printable pages and less-convenient-to-print pages with link rel value "print" bugzilla@wiggum.w3.org
• [Bug 7510] Allow elements beyond just HTML, MathML, and SVG into SVG element bugzilla@wiggum.w3.org
• [Bug 7461] List of space characters should include U+000B LINE TABULATION (VT) or should note why it is not included. bugzilla@wiggum.w3.org
• [Bug 7946] New: Ping-From, Ping-To: wrong heading level or in the wrong section bugzilla@wiggum.w3.org
• [Bug 7945] New: Add a reference to [PROGRESS] here, or make |progress| a simple event (twice) bugzilla@wiggum.w3.org
• [Bug 7944] vCard: agent: avoid power-of-attorney implication bugzilla@wiggum.w3.org
• [Bug 7943] vCard: personal name: more properties bugzilla@wiggum.w3.org
• [Bug 7944] New: vCard: agent: avoid power-of-attorney implication bugzilla@wiggum.w3.org
• [Bug 7943] New: vCard: personal name: more properties bugzilla@wiggum.w3.org
• [Bug 7942] New: It's not defined what happens when properties is set. Throw INVALID_ACCESS_ERR? bugzilla@wiggum.w3.org

Saturday, 17 October 2009

• [Bug 7941] document.getItems should be restricted to HTMLDocument in DOM intro box, as it does not apply to other types of documents. bugzilla@wiggum.w3.org
• [Bug 7941] document.getItems should be restricted to HTMLDocument in DOM intro box, as it does not apply to other types of documents. bugzilla@wiggum.w3.org
• [Bug 7941] New: document.getItems should be restricted to HTMLDocument in DOM intro box, as it does not apply to other types of documents. bugzilla@wiggum.w3.org
• [Bug 7940] New: Under "content model", it isn't clear what the significance of the italic "or" is. If it is intended to signify a higher precidence "or", consider using bullet points to clarify the nesting of conjuctions. bugzilla@wiggum.w3.org
• [Bug 7939] New: stalled is a simple event according to the resource fetch algorithm in 4.8.10.5 Loading the media resource bugzilla@wiggum.w3.org
• [Bug 7461] List of space characters should include U+000B LINE TABULATION (VT) or should note why it is not included. bugzilla@wiggum.w3.org
• [Bug 7461] List of space characters should include U+000B LINE TABULATION (VT) or should note why it is not included. bugzilla@wiggum.w3.org

Friday, 16 October 2009

• [Bug 7937] New: er might return the document with one paragraph modified as follows: <p>I also have some <mark>kitten</mark>s who are visiting me these days. They're really cute. I think they like my garden! Maybe I should adopt a <mark>kitten</mark>.</p> bugzilla@wiggum.w3.org
• [Bug 7936] New: Consider https://bugzilla.mozilla.org/show_bug.cgi?id=521670 bugzilla@wiggum.w3.org
• [Bug 7926] Undefine insertion point if parser on call stack doing anything other than running script element bugzilla@wiggum.w3.org
• [Bug 7918] prefetching: allow site to deny bugzilla@wiggum.w3.org

Thursday, 15 October 2009

• [Bug 7927] widht/height says "map to the dimension properties" but the link goes to "maps to the pixel length property" bugzilla@wiggum.w3.org
• [Bug 7932] New: element.properties says "If the element has an item attribute". The item attribute is now called itemscope. bugzilla@wiggum.w3.org
• [Bug 7931] New: The "loop" label in the 'A start tag whose tag name is "li"' is misplaced, or there is something else wrong that is making the loop useless. bugzilla@wiggum.w3.org
• [Bug 7927] New: widht/height says "map to the dimension properties" but the link goes to "maps to the pixel length property" bugzilla@wiggum.w3.org
• [Bug 7926] New: Undefine insertion point if parser on call stack doing anything other than running script element bugzilla@wiggum.w3.org
• [Bug 7918] prefetching: allow site to deny bugzilla@wiggum.w3.org
• [Bug 7924] New: xaXAafs bugzilla@wiggum.w3.org

Wednesday, 14 October 2009

• [Bug 7923] New: What about local files access? bugzilla@wiggum.w3.org
• [Bug 7917] document.close() should attempt to tokenize bugzilla@wiggum.w3.org
• [Bug 6606] generic 3rd-party <mark>, Smart Tags, and Accelerators prevention bugzilla@wiggum.w3.org
• [Bug 7920] New: media queries ref bugzilla@wiggum.w3.org
• [Bug 7918] New: prefetching: allow site to deny bugzilla@wiggum.w3.org
• [Bug 7902] ijhugytfdsdfgdsd bugzilla@wiggum.w3.org
• [Bug 7894] what is bugzilla@wiggum.w3.org
• [Bug 7917] New: document.close() should attempt to tokenize bugzilla@wiggum.w3.org
• [Bug 7915] New: “itemref” element is missing, <http://www.whatwg.org/specs/web-apps/current-work/multipage/semantics.html#itemref> bugzilla@wiggum.w3.org
• [Bug 7834] "If a new element is inserted between the two nodes that define pointer" - s/element/node/ bugzilla@wiggum.w3.org
• [Bug 7843] Please make 'abort', ' loadend' and 'emptied' use "queue a task". Firing them sync is annoying to implement and doesn't seem to solve any problem. bugzilla@wiggum.w3.org
• [Bug 7900] timedate bugzilla@wiggum.w3.org
• [Bug 7901] ijhugytfd bugzilla@wiggum.w3.org
• [Bug 7903] yhjrth bugzilla@wiggum.w3.org
• [Bug 7914] New: step. 6 should say "object" not "array", right? i.e. "whose value is the object _properties_" bugzilla@wiggum.w3.org

Tuesday, 13 October 2009

• [Bug 7910] New: Since IANA considerations is an appendix, its subsections should be marked as such as well. bugzilla@wiggum.w3.org
• [Bug 7909] New: It seems like this is a subsection of the wrong section. Either it should just be a level up or it should be moved up one section. bugzilla@wiggum.w3.org
• [Bug 7721] Drag and Drop is not keyboard accessible bugzilla@wiggum.w3.org
• [Bug 7721] Drag and Drop is not keyboard accessible bugzilla@wiggum.w3.org
• [Bug 7908] New: the item attribute is gone, DOM intro box for element.properties needs to be updated bugzilla@wiggum.w3.org
• [Bug 7906] New: The venn diagram is all black in the PDF copy bugzilla@wiggum.w3.org

Monday, 12 October 2009

• [Bug 7905] New: Markup in second example has formatting broken - titlecase on tags and > creating line breaks bugzilla@wiggum.w3.org
• [Bug 7904] sex and moooooore seeeex bugzilla@wiggum.w3.org
• [Bug 7904] New: sex and moooooore seeeex bugzilla@wiggum.w3.org
• [Bug 7903] New: yhjrth bugzilla@wiggum.w3.org
• [Bug 7902] New: ijhugytfdsdfgdsd bugzilla@wiggum.w3.org
• [Bug 7901] New: ijhugytfd bugzilla@wiggum.w3.org
• [Bug 7900] New: timedate bugzilla@wiggum.w3.org
• [Bug 7898] New: Maybe this section should cover all elements and attributes historically allowed by IETF standards and W3C Recommendations but no longer allowed, such as <rb> and <a urn> for consistency bugzilla@wiggum.w3.org
• [Bug 7897] New: One can argue that "Any (namespace-less) attribute may be specified ..." contradicts with obsolete feature section where use of some attributes is disallowed 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 7896] New: Specify pageshow and pagehide events bugzilla@wiggum.w3.org
• [Bug 7895] In step 6, it should be allowed (and clear that it is allowed) for UAs to use additional data such as the site TLD to guess the correct encoding bugzilla@wiggum.w3.org
• [Bug 7895] New: In step 6, it should be allowed (and clear that it is allowed) for UAs to use additional data such as the site TLD to guess the correct encoding bugzilla@wiggum.w3.org
• [Bug 7894] New: what is bugzilla@wiggum.w3.org
• [Bug 7891] Current stable Opera releases have at least partial support for canvas. bugzilla@wiggum.w3.org
• [Bug 7893] New: In the example <div id="b" itemprop="band" itemscope id="jazzband"> the div element has two id attributes. Is this desirable? bugzilla@wiggum.w3.org
• [Bug 7892] New: typo bugzilla@wiggum.w3.org

Sunday, 11 October 2009

• [Bug 6606] generic 3rd-party <mark>, Smart Tags, and Accelerators prevention bugzilla@wiggum.w3.org
• [Bug 7891] New: Current stable Opera releases have at least partial support for canvas. bugzilla@wiggum.w3.org
• [Bug 7890] New: "When no more character are": s/character/characters/ bugzilla@wiggum.w3.org
• [Bug 7889] New: audio, canvas and video are missing bugzilla@wiggum.w3.org
• [Bug 7888] New: s/Computer input/User input/ bugzilla@wiggum.w3.org
• [Bug 7887] Drop HTMLTableDataCellElement and HTMLTableHeaderCellElement bugzilla@wiggum.w3.org
• [Bug 7887] New: Drop HTMLTableDataCellElement and HTMLTableHeaderCellElement bugzilla@wiggum.w3.org
• [Bug 7886] New: Drop applet, marquee bugzilla@wiggum.w3.org
• [Bug 7381] Clarify default encoding wording and add some examples for non-latin locales. bugzilla@wiggum.w3.org
• [Bug 7878] An attribute to actually find out if something is playing would be nice (.isplaying). Unless I'm wrong currently you can't actually tell if something is playing without setting var with JS when you start to play and you can't go by the playback position s bugzilla@wiggum.w3.org
• [Bug 7885] New: "…the element does not have an async attribute, or": s/, or// bugzilla@wiggum.w3.org
• [Bug 7381] Clarify default encoding wording and add some examples for non-latin locales. bugzilla@wiggum.w3.org
• [Bug 7884] New: s/defind/defined/ bugzilla@wiggum.w3.org
• [Bug 7883] New: s/defind/defined/ bugzilla@wiggum.w3.org
• [Bug 7882] New: 'message' events has a different interface than it says in the index bugzilla@wiggum.w3.org
• [Bug 7881] New: 'undo', 'redo' events have a different interface than it says in the index bugzilla@wiggum.w3.org
• [Bug 7880] New: 'popstate' event has a different interface than it says in the index bugzilla@wiggum.w3.org
• [Bug 7879] New: 'unload' event has a different interface than it says in the index bugzilla@wiggum.w3.org

Saturday, 10 October 2009

• [Bug 7878] New: An attribute to actually find out if something is playing would be nice (.isplaying). Unless I'm wrong currently you can't actually tell if something is playing without setting var with JS when you start to play and you can't go by the playback position s bugzilla@wiggum.w3.org
• [Bug 7877] New: A media.stop() method would be advantageous, having just pause does restrict the bounds of use especially for media players on a website. bugzilla@wiggum.w3.org
• [Bug 7873] what about backwards compat? can you imagine google or my personal blog website using <input type="search"> for the search field? what about older browsers? bugzilla@wiggum.w3.org
• [Bug 7866] so much more simple to work with! bugzilla@wiggum.w3.org
• [Bug 7862] Support Extended Processing Behavior via @profile/@version bugzilla@wiggum.w3.org
• [Bug 7862] Support Extended Processing Behavior via @profile/@version bugzilla@wiggum.w3.org
• [Bug 7876] New: "A synchronous section never mutates the DOM, runs any script, or have any other side-effects." should say "has any other". bugzilla@wiggum.w3.org
• [Bug 7862] Support Extended Processing Behavior via @profile/@version bugzilla@wiggum.w3.org
• [Bug 7873] what about backwards compat? can you imagine google or my personal blog website using <input type="search"> for the search field? what about older browsers? bugzilla@wiggum.w3.org
• [Bug 7875] New: term: a "range" is an interval between two numbers, e.g. 2-4 or 1969-2032. the term "range" does not mean "imprecise number". bugzilla@wiggum.w3.org
• [Bug 7873] New: what about backwards compat? can you imagine google or my personal blog website using <input type="search"> for the search field? what about older browsers? bugzilla@wiggum.w3.org
• [Bug 7872] New: I have no idea how a "search field" would look like, on any platform. describe. bugzilla@wiggum.w3.org
• [Bug 7871] New: there's more meaning to a password field than just being obstructed. it's really only for passwords / credentials. firefox stores them in the password manager, for example, meaning FF really gives it the meaning "password", not just "obstructed". the defi bugzilla@wiggum.w3.org
• [Bug 7870] New: how does a user enter a "week"? calendar widget? how would he enter it as text? bugzilla@wiggum.w3.org
• [Bug 7869] New: complicated calculation given, but not clearly (only implicitly) stating the obvious question: which day does the week start with? I strongly feel it's Monday, but other people/cultures disagree, I think. bugzilla@wiggum.w3.org
• [Bug 7868] New: what about time zones? which one is used? local (may be difficult to find out)? is this communicated to the user? can he change it? bugzilla@wiggum.w3.org
• [Bug 7867] New: How should a browser render this? Give examples for "typical" or "good" implementations, maybe even for different device types. Should specify that a desktop browser should give a calendar widget, because airlines etc. want that (implement it in JS, but b bugzilla@wiggum.w3.org
• [Bug 7866] New: so much more simple to work with! bugzilla@wiggum.w3.org
• [Bug 7865] New: BenB wants an example of use of datetime-local, e.g. "What time should your event start", with no timezone information, so that the site can keep the event starting at that time in the user's time zone regardless of what time zone the user moves to by the bugzilla@wiggum.w3.org

Friday, 9 October 2009

• [Bug 7862] New: Support Extended Processing Behavior via @profile/@version bugzilla@wiggum.w3.org
• [Bug 7861] New: requirements for meta/http-equiv extensions bugzilla@wiggum.w3.org
• [Bug 7859] Mention under step 1 that it can also be aborted if the user agent has discovered that there is no network available and therefore cannot perform HTTP requests. This prevents dispatching error events when the user is using the application offline. bugzilla@wiggum.w3.org
• [Bug 7859] New: Mention under step 1 that it can also be aborted if the user agent has discovered that there is no network available and therefore cannot perform HTTP requests. This prevents dispatching error events when the user is using the application offline. bugzilla@wiggum.w3.org
• [Bug 7858] All the current entries should merge into one current entry in the joint session history. (imagine a series of nested iframes that haven't been navigated, and call go(-1)... it should go back at the top-level, not do something weird with the iframes) bugzilla@wiggum.w3.org
• [Bug 7858] All the current entries should merge into one current entry in the joint session history. (imagine a series of nested iframes that haven't been navigated, and call go(-1)... it should go back at the top-level, not do something weird with the iframes) bugzilla@wiggum.w3.org
• [Bug 7858] New: All the current entries should merge into one current entry in the joint session history. (imagine a series of nested iframes that haven't been navigated, and call go(-1)... it should go back at the top-level, not do something weird with the iframes) bugzilla@wiggum.w3.org
• [Bug 7836] Should the name="" of a <map> be unique in the document? bugzilla@wiggum.w3.org
• [Bug 7848] MathML version used in HTML5 bugzilla@wiggum.w3.org
• [Bug 7857] New: "Wait for the browsing context to be closed" should be explicit about spinning a nested event loop bugzilla@wiggum.w3.org
• [Bug 7851] Some (perhaps all) scripts with a for="" attribute should be ignored bugzilla@wiggum.w3.org
• [Bug 7855] Define fragment parsing when the context is not an HTML, SVG or MathML node bugzilla@wiggum.w3.org
• [Bug 7856] New: When JavaScript or <canvas> is disabled <canvas> should be treated as an ordinary element and not a replaced element. bugzilla@wiggum.w3.org
• [Bug 7856] When JavaScript or <canvas> is disabled <canvas> should be treated as an ordinary element and not a replaced element. bugzilla@wiggum.w3.org
• [Bug 7855] Define fragment parsing when the context is not an HTML, SVG or MathML node bugzilla@wiggum.w3.org
• [Bug 7855] New: Define fragment parsing when the context is not an HTML, SVG or MathML node bugzilla@wiggum.w3.org
• [Bug 7854] New: "offline application cache" doesn't xref right bugzilla@wiggum.w3.org
• [Bug 7853] metadata bugzilla@wiggum.w3.org
• [Bug 7853] New: metadata bugzilla@wiggum.w3.org
• [Bug 7850] Trying out loud bugzilla@wiggum.w3.org
• [Bug 7845] javascript bugzilla@wiggum.w3.org
• [Bug 7846] javascript bugzilla@wiggum.w3.org
• [Bug 7845] javascript bugzilla@wiggum.w3.org
• [Bug 7852] New: DOM Events has dropped namespaces. Drop all init*EventNS methods. bugzilla@wiggum.w3.org
• [Bug 7851] Some (perhaps all) scripts with a for="" attribute should be ignored bugzilla@wiggum.w3.org
• [Bug 7851] New: Some (perhaps all) scripts with a for="" attribute should be ignored bugzilla@wiggum.w3.org
• [Bug 7836] Should the name="" of a <map> be unique in the document? bugzilla@wiggum.w3.org
• [Bug 7844] Remove "that is in a Document and" when the src attribute is set and when a source is inserted, because there's no reason resource selection shouldn't be run when it's not in the document. Then we also don't have to run resource selection when inserting a bugzilla@wiggum.w3.org
• [Bug 7848] MathML version used in HTML5 bugzilla@wiggum.w3.org
• [Bug 7792] async on inline script is gratuitously backwards-incompatible, should be ignored bugzilla@wiggum.w3.org
• [Bug 7792] async on inline script is gratuitously backwards-incompatible, should be ignored bugzilla@wiggum.w3.org
• [Bug 7850] New: Trying out loud bugzilla@wiggum.w3.org

Thursday, 8 October 2009

• [Bug 7849] New: Check whether .search should or shouldn't work with data: URLs bugzilla@wiggum.w3.org
• [Bug 7848] New: MathML version used in HTML5 bugzilla@wiggum.w3.org
• [Bug 7847] New: for - label - "Associatd" bugzilla@wiggum.w3.org
• [Bug 7842] No programmatic way to make an HTML document - consider adding createHTMLDocument bugzilla@wiggum.w3.org
• [Bug 7846] New: javascript bugzilla@wiggum.w3.org
• [Bug 7845] New: javascript bugzilla@wiggum.w3.org
• [Bug 7844] New: Remove "that is in a Document and" when the src attribute is set and when a source is inserted, because there's no reason resource selection shouldn't be run when it's not in the document. Then we also don't have to run resource selection when inserting a bugzilla@wiggum.w3.org
• [Bug 7843] Please make 'abort', ' loadend' and 'emptied' use "queue a task". Firing them sync is annoying to implement and doesn't seem to solve any problem. bugzilla@wiggum.w3.org
• [Bug 7843] New: Please make 'abort', ' loadend' and 'emptied' use "queue a task". Firing them sync is annoying to implement and doesn't seem to solve any problem. bugzilla@wiggum.w3.org
• [Bug 7842] No programmatic way to make an HTML document - consider adding createHTMLDocument bugzilla@wiggum.w3.org
• [Bug 7842] New: No programmatic way to make an HTML document - consider adding createHTMLDocument bugzilla@wiggum.w3.org
• [Bug 7841] New: s/that the user agent/the user agent/ bugzilla@wiggum.w3.org
• [Bug 7840] New: Index of attributes lacks global attributes bugzilla@wiggum.w3.org
• [Bug 7839] New: Missing (unbalanced) quotemark before "checkbox" keyword. bugzilla@wiggum.w3.org
• [Bug 7838] New: The words "boolean attribute" aren't xreffed here. bugzilla@wiggum.w3.org
• [Bug 7837] New: "space separated list" in ping="" isn't properly xreffed bugzilla@wiggum.w3.org
• [Bug 7836] New: Should the name="" of a <map> be unique in the document? bugzilla@wiggum.w3.org
• [Bug 7835] New: It's not defined what the ownerDocument should be for the created HTMLAudioElement. Similarly for new Image() and new Option() bugzilla@wiggum.w3.org
• [Bug 7834] "If a new element is inserted between the two nodes that define pointer" - s/element/node/ bugzilla@wiggum.w3.org
• [Bug 7834] New: "If a new element is inserted between the two nodes that define pointer" - s/element/node/ bugzilla@wiggum.w3.org
• [Bug 7833] New: The 'demand' event should fire on the canvas whenever it's apperance may affect display. It may occur before document's 'load' event or much later. It is like image fetching from network, it should be up to the browser, when it actually fire. May be helpf bugzilla@wiggum.w3.org
• [Bug 7832] New: The 'for' attribute could point to a element (eg. form) to indicate progress without need for scripting. bugzilla@wiggum.w3.org
• [Bug 7831] New: Does the spec handle setting a drag object type, and having drop targets only respond/highlight to certain drag object types? bugzilla@wiggum.w3.org
• [Bug 7830] New: Does the spec handle selecting multiple objects to drag (holding shift, or command keys) bugzilla@wiggum.w3.org

Wednesday, 7 October 2009

• [Bug 7826] New: Should mention that <hgroup> is a valid context for <hx>. bugzilla@wiggum.w3.org

Tuesday, 6 October 2009

• [Bug 7825] New: typo: "if one available" should read "if one is available" bugzilla@wiggum.w3.org
• [Bug 7824] New: It would be very helpful to have a brief mention here of *why* the WindowProxy object exists. bugzilla@wiggum.w3.org
• [Bug 7800] title attribute: add new attr for machine-readable strings bugzilla@wiggum.w3.org
• [Bug 7800] title attribute: add new attr for machine-readable strings bugzilla@wiggum.w3.org
• [Bug 7820] New: s/codec parameter/codecs parameter/ twice bugzilla@wiggum.w3.org
• [Bug 7817] New: Last example: stray </p> bugzilla@wiggum.w3.org
• [Bug 7816] New: editorial: stray colon here in author view bugzilla@wiggum.w3.org

Monday, 5 October 2009

• [Bug 7810] New: Maybe it's just me, but this paragraph is unclear to me. It is too difficult to understand. What is transparent content? bugzilla@wiggum.w3.org
• [Bug 7809] New: The character ranges in this section should follow the conventions of other ranges. I.e. "to" instead of ".." and the name of the character directly after the Unicode code point. bugzilla@wiggum.w3.org
• [Bug 7807] New: term "new master" can be ambiguous bugzilla@wiggum.w3.org
• [Bug 7804] In Firefox and Safari .text returns the value of the child text nodes -- not textContent bugzilla@wiggum.w3.org
• [Bug 7800] title attribute: add new attr for machine-readable strings bugzilla@wiggum.w3.org
• [Bug 7799] If the fragid doesn't match an ID or a name in the document, then surely the browser should revert to doing a text search for the fragid text in the document bugzilla@wiggum.w3.org
• [Bug 7806] atom ID element generation for feed entries bugzilla@wiggum.w3.org
• [Bug 7806] New: atom ID element generation for feed entries bugzilla@wiggum.w3.org
• [Bug 7805] New: The tag name of foreign elements aren't necessarily all-lowercase. bugzilla@wiggum.w3.org
• [Bug 7803] The title element's "value" is earlier defined to be the value of its child text nodes -- not textContent bugzilla@wiggum.w3.org
• [Bug 7804] New: In Firefox and Safari .text returns the value of the child text nodes -- not textContent bugzilla@wiggum.w3.org
• [Bug 7803] New: The title element's "value" is earlier defined to be the value of its child text nodes -- not textContent bugzilla@wiggum.w3.org
• [Bug 7802] New: editorial: broken xref in dom-intro: s/dom-getItems()/dom-document-getItems/ bugzilla@wiggum.w3.org
• [Bug 7657] Redefining dt and dd bugzilla@wiggum.w3.org
• [Bug 7799] If the fragid doesn't match an ID or a name in the document, then surely the browser should revert to doing a text search for the fragid text in the document bugzilla@wiggum.w3.org
• [Bug 7800] title attribute: add new attr for machine-readable strings bugzilla@wiggum.w3.org
• [Bug 7059] Forking XPath bugzilla@wiggum.w3.org
• [Bug 7669] Redefining dt and dd, recommend new element as caption for Figure bugzilla@wiggum.w3.org
• [Bug 7801] New: Shouldn't autofocus be included in this matrix? 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 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 7800] New: title attribute: add new attr for machine-readable strings bugzilla@wiggum.w3.org

Sunday, 4 October 2009

• [Bug 7645] associate printable pages and less-convenient-to-print pages with link rel value "print" bugzilla@wiggum.w3.org
• [Bug 7736] add tooltip attribute & keep title for other uses bugzilla@wiggum.w3.org
• [Bug 7645] associate printable pages and less-convenient-to-print pages with link rel value "print" bugzilla@wiggum.w3.org
• [Bug 7799] New: If the fragid doesn't match an ID or a name in the document, then surely the browser should revert to doing a text search for the fragid text in the document bugzilla@wiggum.w3.org

Saturday, 3 October 2009

• [Bug 7798] New: I'm missing the height property in TextMetrics bugzilla@wiggum.w3.org

Friday, 2 October 2009

• [Bug 7794] New: IDL attribute should be refId for consistency with e.g. getElementById bugzilla@wiggum.w3.org
• [Bug 7792] async on inline script is gratuitously backwards-incompatible, should be ignored bugzilla@wiggum.w3.org
• [Bug 7792] New: async on inline script is gratuitously backwards-incompatible, should be ignored bugzilla@wiggum.w3.org
• [Bug 7776] rename appcache events? bugzilla@wiggum.w3.org

Thursday, 1 October 2009

• [Bug 7752] Please use "URL character encoding" instead of just "character encoding" for clarity bugzilla@wiggum.w3.org
• [Bug 7510] Allow elements beyond just HTML, MathML, and SVG into SVG element bugzilla@wiggum.w3.org
• [Bug 7510] Allow elements beyond just HTML, MathML, and SVG into SVG element bugzilla@wiggum.w3.org
• [Bug 7752] Please use "URL character encoding" instead of just "character encoding" for clarity bugzilla@wiggum.w3.org
• [Bug 7786] change priority for online whitelist namespaces other than * bugzilla@wiggum.w3.org
• [Bug 7786] New: change priority for online whitelist namespaces other than * bugzilla@wiggum.w3.org
• [Bug 7761] It would be nice to have some kind of comment as to how the checking and downloading events from step 2 interact with the events of the same name in step 3 and beyond. bugzilla@wiggum.w3.org
• [Bug 7775] are the extra events needed when status is checking or downloading bugzilla@wiggum.w3.org
• [Bug 7775] are the extra events needed when status is checking or downloading bugzilla@wiggum.w3.org
• [Bug 7785] "Expiring application caches" feedback bugzilla@wiggum.w3.org
• [Bug 7785] New: "Expiring application caches" feedback bugzilla@wiggum.w3.org
• [Bug 7784] "cache failure steps" feedback bugzilla@wiggum.w3.org
• [Bug 7784] New: "cache failure steps" feedback bugzilla@wiggum.w3.org
• [Bug 7783] appcache download events bugzilla@wiggum.w3.org
• [Bug 7783] New: appcache download events bugzilla@wiggum.w3.org
• [Bug 7782] New: "select an application cache" is vague bugzilla@wiggum.w3.org
• [Bug 7781] forbid duplicate online whitelist namespaces bugzilla@wiggum.w3.org
• [Bug 7781] New: forbid duplicate online whitelist namespaces bugzilla@wiggum.w3.org
• [Bug 7780] New: simplify appcache terminology bugzilla@wiggum.w3.org
• [Bug 7765] Maybe progress should be named fetchcachefile or some such bugzilla@wiggum.w3.org
• [Bug 7765] Maybe progress should be named fetchcachefile or some such bugzilla@wiggum.w3.org
• [Bug 7764] Since the online whitelist entries are namespaces it should not use a prefix match but instead something more complicated as is defined for fallback entries in 6.9.5. bugzilla@wiggum.w3.org
• [Bug 7767] Atomic update of application cache is not well-defined bugzilla@wiggum.w3.org
• [Bug 7766] Fallback namespace overlap/repetition ignored bugzilla@wiggum.w3.org
• [Bug 7779] Missing task source for application cache events bugzilla@wiggum.w3.org

Last message date: Saturday, 31 October 2009 18:31:54 UTC