public-html-bugzilla@w3.org from February 2011 by date

Monday, 28 February 2011

• [Bug 11393] End tag fails to break out of foreign content bugzilla@jessica.w3.org
• [Bug 11393] End tag fails to break out of foreign content bugzilla@jessica.w3.org
• [Bug 12017] Keeping IMG aspect ratio bugzilla@jessica.w3.org
• [Bug 11393] End tag fails to break out of foreign content bugzilla@jessica.w3.org
• [Bug 12017] Keeping IMG aspect ratio bugzilla@jessica.w3.org
• [Bug 11962] Add HTML tag support for generation of PDF documents or Post Scripts bugzilla@jessica.w3.org
• [Bug 11458] mechanism needed to control refresh url for ajax applications bugzilla@jessica.w3.org
• [Bug 11457] textarea/text need ability to remove focus bugzilla@jessica.w3.org
• [Bug 7475] Semantics of rel=first and rel=index breaks specs and implementations bugzilla@jessica.w3.org
• [Bug 7475] Semantics of rel=first and rel=index breaks specs and implementations bugzilla@jessica.w3.org
• [Bug 12207] Should html/@lang and html/@xml:lang result in a dc:language predicate? bugzilla@jessica.w3.org
• [Bug 11887] Remove useless input.valueAsNumber. Pretty much the same functionality can be achieved using parseFloat or parseInt bugzilla@jessica.w3.org
• [Bug 12207] New: Should html/@lang and html/@xml:lang result in a dc:language predicate? bugzilla@jessica.w3.org
• [Bug 11887] Remove useless input.valueAsNumber. Pretty much the same functionality can be achieved using parseFloat or parseInt bugzilla@jessica.w3.org
• [Bug 11984] Simplify <video> for implementors and authors by ignoring the Content-Type HTTP header bugzilla@jessica.w3.org
• [Bug 12203] Inconsistent capitalization of "Windows". IANA 1252 uses lowercase, IANA 1254 uses uppercase, so ignore offical versions and go with what makes sense, which is "Windows" bugzilla@jessica.w3.org
• [Bug 12204] Inconsistent capitalization of "Windows". IANA 1252 uses lowercase, IANA 1254 uses uppercase, so ignore offical versions and go with what makes sense, which is "Windows" bugzilla@jessica.w3.org
• [Bug 12204] New: Inconsistent capitalization of "Windows". IANA 1252 uses lowercase, IANA 1254 uses uppercase, so ignore offical versions and go with what makes sense, which is "Windows" bugzilla@jessica.w3.org
• [Bug 12203] New: Inconsistent capitalization of "Windows". IANA 1252 uses lowercase, IANA 1254 uses uppercase, so ignore offical versions and go with what makes sense, which is "Windows" bugzilla@jessica.w3.org
• [Bug 12076] Wishlist: line-based parser bugzilla@jessica.w3.org

Sunday, 27 February 2011

• [Bug 12201] Tim Berners-Lee seems to be TimBL's canonical name bugzilla@jessica.w3.org
• [Bug 12201] New: Tim Berners-Lee seems to be TimBL's canonical name bugzilla@jessica.w3.org
• [Bug 12193] It would be nice to hide the html5(html+css+js) code.The visibility of the code makes it vulnerable to certain types of hacks and ofcourse proprietary code which the developer might wish not to share.please consider this request bugzilla@jessica.w3.org
• [Bug 12200] New: "If a reflecting IDL attribute is a DOMString whose": s/DOMString/DOMString attribute/ bugzilla@jessica.w3.org
• [Bug 12196] pattern = context . createPattern(image, repetition), could be any valid source or only image, by example other canvas... bugzilla@jessica.w3.org
• [Bug 12198] pattern = context . createPattern(image, repetition), could be any valid source or only image, by example other canvas... bugzilla@jessica.w3.org
• [Bug 12197] pattern = context . createPattern(image, repetition), could be any valid source or only image, by example other canvas... bugzilla@jessica.w3.org
• [Bug 12198] pattern = context . createPattern(image, repetition), could be any valid source or only image, by example other canvas... bugzilla@jessica.w3.org
• [Bug 12168] Shouldn't you have a rule somewhere like body { background: white } or html { background: white }? bugzilla@jessica.w3.org
• [Bug 12154] b and strong should be font-weight: bolder, not font-weight: bold. IE9 RC, Firefox 4b11, and WebKit all agree, with only Opera differing. Test case: data:text/html,<!doctype html><p style=font-weight:100><b>Should be bold per current spec</b> bugzilla@jessica.w3.org
• [Bug 12199] New: Step 4.4 "For each character ..." -> It must operate on a sequence of characters, not on a character. Otherwise it would generate overlong form when the encoding is stateful (e.g. consider ISO-2022-JP's escape sequences). bugzilla@jessica.w3.org
• [Bug 12193] It would be nice to hide the html5(html+css+js) code.The visibility of the code makes it vulnerable to certain types of hacks and ofcourse proprietary code which the developer might wish not to share.please consider this request bugzilla@jessica.w3.org
• [Bug 12198] New: pattern = context . createPattern(image, repetition), could be any valid source or only image, by example other canvas... bugzilla@jessica.w3.org
• [Bug 12197] New: pattern = context . createPattern(image, repetition), could be any valid source or only image, by example other canvas... bugzilla@jessica.w3.org
• [Bug 12196] New: pattern = context . createPattern(image, repetition), could be any valid source or only image, by example other canvas... bugzilla@jessica.w3.org

Saturday, 26 February 2011

• [Bug 12193] It would be nice to hide the html5(html+css+js) code.The visibility of the code makes it vulnerable to certain types of hacks and ofcourse proprietary code which the developer might wish not to share.please consider this request bugzilla@jessica.w3.org
• [Bug 12195] canplay event is fired long before one can play in any meaningful way bugzilla@jessica.w3.org
• [Bug 12195] New: canplay event is fired long before one can play in any meaningful way bugzilla@jessica.w3.org
• [Bug 12194] New: The example calls a function "recover" but there is no such function. Should it be calling the function "set"? bugzilla@jessica.w3.org
• [Bug 12191] The spec doesn't currently seem to handle the situation of seeking to a point beyond the end of a presumed-infinite stream, whether by advancing monotonically to that point or arbitrarily seeking to that point. bugzilla@jessica.w3.org
• [Bug 12193] It would be nice to hide the html5(html+css+js) code.The visibility of the code makes it vulnerable to certain types of hacks and ofcourse proprietary code which the developer might wish not to share.please consider this request bugzilla@jessica.w3.org
• [Bug 12193] New: It would be nice to hide the html5(html+css+js) code.The visibility of the code makes it vulnerable to certain types of hacks and ofcourse proprietary code which the developer might wish not to share.please consider this request bugzilla@jessica.w3.org
• [Bug 12192] New: Would be great to see a sample .vtt file! bugzilla@jessica.w3.org

Friday, 25 February 2011

• [Bug 12191] New: The spec doesn't currently seem to handle the situation of seeking to a point beyond the end of a presumed-infinite stream, whether by advancing monotonically to that point or arbitrarily seeking to that point. bugzilla@jessica.w3.org
• [Bug 11943] Typo: "exeption" (wasn't in the original text :) ) bugzilla@jessica.w3.org
• [Bug 11945] The table displays weirdly in WebKit -- some entries ("Z" and "m") spill over between columns, and "y" isn't aligned to the bottom. In Gecko and Opera, it doesn't display in columns at all. How about sticking with <dl> and CSS columns like in my version bugzilla@jessica.w3.org
• [Bug 10828] i18n comment 4 : at least by default, <br> should constitute a bidi paragraph break bugzilla@jessica.w3.org
• [Bug 10693] Need a means for navigating between related timed tracks of media elements bugzilla@jessica.w3.org
• [Bug 12188] aaa adf afadf adfdf bugzilla@jessica.w3.org
• [Bug 12188] New: aaa adf afadf adfdf bugzilla@jessica.w3.org
• [Bug 12186] Should explicitly state that TimeRanges.end() is inclusive, so that if the browser reverts to HAVE_METADATA while playing, the .buffered.end(0) value is the last rendered frame, and .currentTime is the next frame, and so that when .ended is true, .buffere bugzilla@jessica.w3.org
• [Bug 12187] New: should drawImage throw for dw/dh==0? bugzilla@jessica.w3.org
• [Bug 10828] i18n comment 4 : at least by default, <br> should constitute a bidi paragraph break bugzilla@jessica.w3.org
• [Bug 12186] New: Should explicitly state that TimeRanges.end() is inclusive, so that if the browser reverts to HAVE_METADATA while playing, the .buffered.end(0) value is the last rendered frame, and .currentTime is the next frame, and so that when .ended is true, .buffere bugzilla@jessica.w3.org
• [Bug 10828] i18n comment 4 : at least by default, <br> should constitute a bidi paragraph break bugzilla@jessica.w3.org
• [Bug 11939] Progress element max IDL attribute should reflect the maximum value instead of the content attribute bugzilla@jessica.w3.org
• [Bug 10828] i18n comment 4 : at least by default, <br> should constitute a bidi paragraph break bugzilla@jessica.w3.org
• [Bug 11937] Progress element should be indeterminate if the value attribute isn't a valid float bugzilla@jessica.w3.org
• [Bug 12183] "Last call for comments" in the infoboxes bugzilla@jessica.w3.org
• [Bug 12183] New: "Last call for comments" in the infoboxes bugzilla@jessica.w3.org
• [Bug 12182] "The ready states" vs "Network states" bugzilla@jessica.w3.org
• [Bug 12182] New: "The ready states" vs "Network states" bugzilla@jessica.w3.org
• [Bug 10828] i18n comment 4 : at least by default, <br> should constitute a bidi paragraph break bugzilla@jessica.w3.org
• [Bug 11893] define lexical processing rules for ARIA attributes bugzilla@jessica.w3.org
• [Bug 11951] One part of this section says "Binary data with a file name" and another part says "optionally with a file name". So is it optional or not? bugzilla@jessica.w3.org
• [Bug 11951] One part of this section says "Binary data with a file name" and another part says "optionally with a file name". So is it optional or not? bugzilla@jessica.w3.org
• [Bug 10693] Need a means for navigating between related timed tracks of media elements bugzilla@jessica.w3.org
• [Bug 12181] New: The text in 4.12.4.17.1 conflicts with existing practice, older (e.g. HTML 4) descriptions, and the brief summary in the table at the start of 4.12.4, where "index" is described thusly: "Gives a link to the document that provides a table of contents or in bugzilla@jessica.w3.org
• [Bug 11943] Typo: "exeption" (wasn't in the original text :) ) bugzilla@jessica.w3.org
• [Bug 11945] The table displays weirdly in WebKit -- some entries ("Z" and "m") spill over between columns, and "y" isn't aligned to the bottom. In Gecko and Opera, it doesn't display in columns at all. How about sticking with <dl> and CSS columns like in my version bugzilla@jessica.w3.org
• [Bug 11943] Typo: "exeption" (wasn't in the original text :) ) bugzilla@jessica.w3.org
• [Bug 11942] new feature suggestion: add inputmode attribute to <input> and <textarea> This already exists in XHTML Basic: http://www.w3.org/TR/2010/REC-xhtml-basic-20101123/#s_inputmode Rationale is explained in XHTML basic... Nir Dagan nir@nirdagan.com bugzilla@jessica.w3.org
• [Bug 11936] Progress element max and value IDL attributes should be float, not double bugzilla@jessica.w3.org
• [Bug 11936] Progress element max and value IDL attributes should be float, not double bugzilla@jessica.w3.org
• [Bug 11937] Progress element should be indeterminate if the value attribute isn't a valid float bugzilla@jessica.w3.org
• [Bug 11939] Progress element max IDL attribute sholud reflect the maximum value instead of the content attribute bugzilla@jessica.w3.org
• [Bug 11938] Progress element value IDL attribute default value should be 0 instead of -1 bugzilla@jessica.w3.org
• [Bug 11938] Progress element value IDL attribute default value should be 0 instead of -1 bugzilla@jessica.w3.org
• [Bug 11616] UTC began at 1961-01-01T00:00Z, and there is no such thing as proleptic UTC. Therefore the Nero example is ill-defined. bugzilla@jessica.w3.org
• [Bug 11940] Please specify reality and deal with raster images and SVG in embed being handled by the UA rather than a plugin or ignored bugzilla@jessica.w3.org
• [Bug 11616] UTC began at 1961-01-01T00:00Z, and there is no such thing as proleptic UTC. Therefore the Nero example is ill-defined. bugzilla@jessica.w3.org
• [Bug 11925] "HTML documents" in the first paragraph should be xref'ed bugzilla@jessica.w3.org
• [Bug 11925] "HTML documents" in the first paragraph should be xref'ed bugzilla@jessica.w3.org
• [Bug 11737] Change content model of <hgroup> to single <hx> + zero or more <sh> (sub/suphead) elements bugzilla@jessica.w3.org
• [Bug 11731] Replace <hgroup> element with a <subhead> element used as the child of the <hx> element bugzilla@jessica.w3.org
• [Bug 11229] Try making an author-specific edition that has one page per section, a tree on the side, and ben's styles, as per http://www.reddit.com/r/programming/comments/dzww6/who_edits_the_w3c_specs_they_look_like_a_ransom/c14ilc2 bugzilla@jessica.w3.org
• [Bug 10963] Table prohibited from being used as a layout aid bugzilla@jessica.w3.org
• [Bug 12178] Simplify/Remove the semantics of <b> and <i> or the description of it bugzilla@jessica.w3.org
• [Bug 12171] Define "resolve an address" here until there's a useful spec to reference. The lack of specification seriously hurts any attempt to improve interoperability for anything related to URLs bugzilla@jessica.w3.org
• [Bug 12151] :in-range and :out-of-range should only apply to input elements with a type for which min or max apply bugzilla@jessica.w3.org

Thursday, 24 February 2011

• [Bug 12178] New: Simplify/Remove the semantics of <b> and <i> or the description of it bugzilla@jessica.w3.org
• [Bug 12172] What should startOffsetTime return when the current timeline offset is not known? bugzilla@jessica.w3.org
• [Bug 12175] the order of the loadedmetadata, loadeddata and suspend event is not defined bugzilla@jessica.w3.org
• [Bug 12176] New: will try to update the cache bugzilla@jessica.w3.org
• [Bug 12175] the order of the loadedmetadata, loadeddata and suspend event is not defined bugzilla@jessica.w3.org
• [Bug 12175] New: the order of the loadedmetadata, loadeddata and suspend event is not defined bugzilla@jessica.w3.org
• [Bug 12174] New: Structured Clone 'Object' links to HTMLObjectElement? bugzilla@jessica.w3.org
• [Bug 12172] What should startOffsetTime return when the current timeline offset is not known? bugzilla@jessica.w3.org
• [Bug 12172] New: What should startOffsetTime return when the current timeline offset is not known? bugzilla@jessica.w3.org
• [Bug 12171] Define "resolve an address" here until there's a useful spec to reference. The lack of specification seriously hurts any attempt to improve interoperability for anything related to URLs bugzilla@jessica.w3.org
• [Bug 12171] Define "resolve an address" here until there's a useful spec to reference. The lack of specification seriously hurts any attempt to improve interoperability for anything related to URLs bugzilla@jessica.w3.org
• [Bug 12171] Define "resolve an address" here until there's a useful spec to reference. The lack of specification seriously hurts any attempt to improve interoperability for anything related to URLs bugzilla@jessica.w3.org
• [Bug 12171] New: Define "resolve an address" here until there's a useful spec to reference. The lack of specification seriously hurts any attempt to improve interoperability for anything related to URLs bugzilla@jessica.w3.org
• [Bug 11393] End tag fails to break out of foreign content bugzilla@jessica.w3.org
• [Bug 11393] End tag fails to break out of foreign content bugzilla@jessica.w3.org
• [Bug 12141] Specifically state that all <track> options be exposed to the end user bugzilla@jessica.w3.org
• [Bug 12141] Specifically state that all <track> options be exposed to the end user bugzilla@jessica.w3.org
• [Bug 12169] I like cheese bugzilla@jessica.w3.org
• [Bug 12169] I like cheese bugzilla@jessica.w3.org
• [Bug 12168] Shouldn't you have a rule somewhere like body { background: white } or html { background: white }? bugzilla@jessica.w3.org

Wednesday, 23 February 2011

• [Bug 12167] The requirement on the listing element conflicts with its old definition (which requires a special parsing mode where no markup except the element's end tag is recognized) and usage. It is better to avoid requiring any support than to require support that bugzilla@jessica.w3.org
• [Bug 12166] The requirement on the xmp element conflicts with its old definition (which requires a special parsing mode where no markup except the element's end tag is recognized) and usage. It is better to avoid requiring any support than to require support that bre bugzilla@jessica.w3.org
• [Bug 12165] The requirement on the plaintext element conflicts with its old definition and usage. It is better to avoid requiring any support than to require support that breaks legacy usage. The plaintext element should be regarded as undefined in HTML5. bugzilla@jessica.w3.org
• [Bug 12049] Script defer/async attributed have no realistic usage scenario bugzilla@jessica.w3.org
• [Bug 12169] New: I like cheese bugzilla@jessica.w3.org
• [Bug 12168] Shouldn't you have a rule somewhere like body { background: white } or html { background: white }? bugzilla@jessica.w3.org
• [Bug 12031] Please provide example of fragment parsing w/o a contextElement bugzilla@jessica.w3.org
• [Bug 12168] Shouldn't you have a rule somewhere like body { background: white } or html { background: white }? bugzilla@jessica.w3.org
• [Bug 12168] New: Shouldn't you have a rule somewhere like body { background: white } or html { background: white }? bugzilla@jessica.w3.org
• [Bug 12166] The requirement on the xmp element conflicts with its old definition (which requires a special parsing mode where no markup except the element's end tag is recognized) and usage. It is better to avoid requiring any support than to require support that bre bugzilla@jessica.w3.org
• [Bug 12165] The requirement on the plaintext element conflicts with its old definition and usage. It is better to avoid requiring any support than to require support that breaks legacy usage. The plaintext element should be regarded as undefined in HTML5. bugzilla@jessica.w3.org
• [Bug 12167] New: The requirement on the listing element conflicts with its old definition (which requires a special parsing mode where no markup except the element's end tag is recognized) and usage. It is better to avoid requiring any support than to require support that bugzilla@jessica.w3.org
• [Bug 12166] New: The requirement on the xmp element conflicts with its old definition (which requires a special parsing mode where no markup except the element's end tag is recognized) and usage. It is better to avoid requiring any support than to require support that bre bugzilla@jessica.w3.org
• [Bug 12165] New: The requirement on the plaintext element conflicts with its old definition and usage. It is better to avoid requiring any support than to require support that breaks legacy usage. The plaintext element should be regarded as undefined in HTML5. bugzilla@jessica.w3.org
• [Bug 12049] Script defer/async attributed have no realistic usage scenario bugzilla@jessica.w3.org
• [Bug 12164] People, are you crazy?! Why are you putting the entire spec into a single file?? It takes forever to load, and locks up the browser in the process. Split it up and use hyperlinks, like the rest of the world! bugzilla@jessica.w3.org
• [Bug 12164] New: People, are you crazy?! Why are you putting the entire spec into a single file?? It takes forever to load, and locks up the browser in the process. Split it up and use hyperlinks, like the rest of the world! bugzilla@jessica.w3.org
• [Bug 11921] Fix references to test2.w3.org bugzilla@jessica.w3.org
• [Bug 11916] 2d.drawImage.incomplete partially invalid bugzilla@jessica.w3.org
• [Bug 12163] New: The illustration of header associations for the ID/Measurement/Average/Maximum table is incorrect. Since the header cells "Legs" and "Tails" (in both rowgroups) do not have scope attributes set to "row" and they have data cells to their left, they are not bugzilla@jessica.w3.org
• [Bug 12162] New: Overall comment. A downloadable PDF of the altest editor's draft would be a useful way for readers to access the spec. Personally I would like to add my own comments and notations as I read the sepc, but this is only possible with a PDF. I tried creating bugzilla@jessica.w3.org
• [Bug 12161] The link "WebSocket protocol" refers to an Internet Draft that has expired (on Feb. 17, 2011). bugzilla@jessica.w3.org
• [Bug 12161] New: The link "WebSocket protocol" refers to an Internet Draft that has expired (on Feb. 17, 2011). bugzilla@jessica.w3.org
• [Bug 12160] New: The test page linked to does not exist (404 Not Found). bugzilla@jessica.w3.org
• [Bug 11984] Simplify <video> for implementors and authors by ignoring the Content-Type HTTP header bugzilla@jessica.w3.org
• [Bug 12159] New: how to prevent registering a protocol twice w/o bothering the user? bugzilla@jessica.w3.org
• [Bug 11984] Simplify <video> for implementors and authors by ignoring the Content-Type HTTP header bugzilla@jessica.w3.org
• [Bug 12158] [device] It might be useful to have access to USB joysticks (maybe even with force-feedback) and other kinds of HID. bugzilla@jessica.w3.org
• [Bug 12151] :in-range and :out-of-range should only apply to input elements with a type for which min or max apply bugzilla@jessica.w3.org
• [Bug 12154] b and strong should be font-weight: bolder, not font-weight: bold. IE9 RC, Firefox 4b11, and WebKit all agree, with only Opera differing. Test case: data:text/html,<!doctype html><p style=font-weight:100><b>Should be bold per current spec</b> bugzilla@jessica.w3.org
• [Bug 12148] I strongly believe disallowing 'true' and 'false' in boolean attributes will cause significant confusion in the future. Already, you can find respected web developers incorrectly referring to attributes as true and false. For instance: http://blog.getif bugzilla@jessica.w3.org
• [Bug 12148] I strongly believe disallowing 'true' and 'false' in boolean attributes will cause significant confusion in the future. Already, you can find respected web developers incorrectly referring to attributes as true and false. For instance: http://blog.getif bugzilla@jessica.w3.org
• [Bug 12158] New: It might be useful to have access to USB joysticks (maybe even with force-feedback) and other kinds of HID. bugzilla@jessica.w3.org
• [Bug 12151] :in-range and :out-of-range should only apply to input elements with a type for which min or max apply bugzilla@jessica.w3.org
• [Bug 12157] New: s/Other specification/Other specifications/ bugzilla@jessica.w3.org
• [Bug 11637] Disallow abusing the Decision Policy by escalating editorial bugs bugzilla@jessica.w3.org
• [Bug 12141] Specifically state that all <track> options be exposed to the end user bugzilla@jessica.w3.org
• [Bug 12151] :in-range and :out-of-range should only apply to input elements with a type for which min or max apply bugzilla@jessica.w3.org
• [Bug 12151] :in-range and :out-of-range should only apply to input elements with a type for which min or max apply bugzilla@jessica.w3.org

Tuesday, 22 February 2011

• [Bug 12151] :in-range and :out-of-range should only apply to input elements with a type for which min or max apply bugzilla@jessica.w3.org
• [Bug 12154] b and strong should be font-weight: bolder, not font-weight: bold. IE9 RC, Firefox 4b11, and WebKit all agree, with only Opera differing. Test case: data:text/html,<!doctype html><p style=font-weight:100><b>Should be bold per current spec</b> bugzilla@jessica.w3.org
• [Bug 12154] New: b and strong should be font-weight: bolder, not font-weight: bold. IE9 RC, Firefox 4b11, and WebKit all agree, with only Opera differing. Test case: data:text/html,<!doctype html><p style=font-weight:100><b>Should be bold per current spec</b> bugzilla@jessica.w3.org
• [Bug 8401] Remove section 4.12 regarding idioms bugzilla@jessica.w3.org
• [Bug 12141] Specifically state that all <track> options be exposed to the end user bugzilla@jessica.w3.org
• [Bug 12141] Specifically state that all <track> options be exposed to the end user bugzilla@jessica.w3.org
• [Bug 12153] New: The input tag references a 'filelist', which appears to be undefined in the specification. bugzilla@jessica.w3.org
• [Bug 12141] Specifically state that all <track> options be exposed to the end user bugzilla@jessica.w3.org
• [Bug 10525] Please try to improve Bugzilla's accessibility/usability problems before Last Call bugzilla@jessica.w3.org
• [Bug 10525] Please try to improve Bugzilla's accessibility/usability problems before Last Call bugzilla@jessica.w3.org
• [Bug 12141] Specifically state that all <track> options be exposed to the end user bugzilla@jessica.w3.org
• [Bug 11891] add role attribute to list of global attributes and add definition for it bugzilla@jessica.w3.org
• [Bug 12152] New: Charset attribute is (in HTML 4) supposed to inform the browser beforehand about the encoding (before making an HTTP request), and it may also be useful if the resource is not transferred via HTTP or it is sent without suitable Content-Type header. The cu bugzilla@jessica.w3.org
• [Bug 11815] should add something about /favicon.ico too bugzilla@jessica.w3.org
• [Bug 12151] :in-range and :out-of-range should only apply to input elements with a type for which min or max apply bugzilla@jessica.w3.org
• [Bug 12151] :in-range and :out-of-range should only apply to input elements with a type for which min or max apply bugzilla@jessica.w3.org
• [Bug 12148] I strongly believe disallowing 'true' and 'false' in boolean attributes will cause significant confusion in the future. Already, you can find respected web developers incorrectly referring to attributes as true and false. For instance: http://blog.getif bugzilla@jessica.w3.org
• [Bug 12148] I strongly believe disallowing 'true' and 'false' in boolean attributes will cause significant confusion in the future. Already, you can find respected web developers incorrectly referring to attributes as true and false. For instance: http://blog.getif bugzilla@jessica.w3.org
• [Bug 12146] <!DOCTYPE HTML> <html lang="ja"> <head> <meta charset="utf-8"> <link rel="stylesheet" type="text/css" href="style.css"> </head> <body> <div id="wrapper"> <header> <h1><a href="#"><img src="logo.gif"></a></h1> </header> <nav> <ul> <li><a href="#">MENU_01</ bugzilla@jessica.w3.org
• [Bug 12146] <!DOCTYPE HTML> <html lang="ja"> <head> <meta charset="utf-8"> <link rel="stylesheet" type="text/css" href="style.css"> </head> <body> <div id="wrapper"> <header> <h1><a href="#"><img src="logo.gif"></a></h1> </header> <nav> <ul> <li><a href="#">MENU_01</ bugzilla@jessica.w3.org
• [Bug 12151] :in-range and :out-of-range should only apply to input elements with a type for which min or max apply bugzilla@jessica.w3.org
• [Bug 12151] :in-range and :out-of-range should only apply to input elements with a type for which min or max apply bugzilla@jessica.w3.org
• [Bug 12151] :in-range and :out-of-range should only apply to input elements with a type for which min or max apply bugzilla@jessica.w3.org
• [Bug 12151] New: :in-range and :out-of-range should only apply to input elements with a type for which min or max apply bugzilla@jessica.w3.org

Monday, 21 February 2011

• [Bug 12117] Coordination bugzilla@jessica.w3.org
• [Bug 12150] New: t taking p bugzilla@jessica.w3.org
• [Bug 12141] Specifically state that all <track> options be exposed to the end user bugzilla@jessica.w3.org
• [Bug 12148] I strongly believe disallowing 'true' and 'false' in boolean attributes will cause significant confusion in the future. Already, you can find respected web developers incorrectly referring to attributes as true and false. For instance: http://blog.getif bugzilla@jessica.w3.org
• [Bug 12148] I strongly believe disallowing 'true' and 'false' in boolean attributes will cause significant confusion in the future. Already, you can find respected web developers incorrectly referring to attributes as true and false. For instance: http://blog.getif bugzilla@jessica.w3.org
• [Bug 12148] I strongly believe disallowing 'true' and 'false' in boolean attributes will cause significant confusion in the future. Already, you can find respected web developers incorrectly referring to attributes as true and false. For instance: http://blog.getif bugzilla@jessica.w3.org
• [Bug 12148] I strongly believe disallowing 'true' and 'false' in boolean attributes will cause significant confusion in the future. Already, you can find respected web developers incorrectly referring to attributes as true and false. For instance: http://blog.getif bugzilla@jessica.w3.org
• [Bug 12148] I strongly believe disallowing 'true' and 'false' in boolean attributes will cause significant confusion in the future. Already, you can find respected web developers incorrectly referring to attributes as true and false. For instance: http://blog.getif bugzilla@jessica.w3.org
• [Bug 12148] I strongly believe disallowing 'true' and 'false' in boolean attributes will cause significant confusion in the future. Already, you can find respected web developers incorrectly referring to attributes as true and false. For instance: http://blog.getif bugzilla@jessica.w3.org
• [Bug 12149] The argument name is "scheme", but you call it "protocol" in this text: The arguments to the methods have the following meanings and corresponding implementation requirements: protocol (registerProtocolHandler() only) bugzilla@jessica.w3.org
• [Bug 12149] New: The argument name is "scheme", but you call it "protocol" in this text: The arguments to the methods have the following meanings and corresponding implementation requirements: protocol (registerProtocolHandler() only) bugzilla@jessica.w3.org
• [Bug 12148] I strongly believe disallowing 'true' and 'false' in boolean attributes will cause significant confusion in the future. Already, you can find respected web developers incorrectly referring to attributes as true and false. For instance: http://blog.getif bugzilla@jessica.w3.org
• [Bug 12148] New: I strongly believe disallowing 'true' and 'false' in boolean attributes will cause significant confusion in the future. Already, you can find respected web developers incorrectly referring to attributes as true and false. For instance: http://blog.getif bugzilla@jessica.w3.org
• [Bug 12147] It's not "little green guys with guns", it's "diminutively-sized colorfully challenged persons expressing their second amendment rights". bugzilla@jessica.w3.org
• [Bug 12147] New: It's not "little green guys with guns", it's "diminutively-sized colorfully challenged persons expressing their second amendment rights". bugzilla@jessica.w3.org
• [Bug 12146] New: <!DOCTYPE HTML> <html lang="ja"> <head> <meta charset="utf-8"> <link rel="stylesheet" type="text/css" href="style.css"> </head> <body> <div id="wrapper"> <header> <h1><a href="#"><img src="logo.gif"></a></h1> </header> <nav> <ul> <li><a href="#">MENU_01</ bugzilla@jessica.w3.org
• [Bug 12145] define how to resolve conflicting link types bugzilla@jessica.w3.org
• [Bug 12145] define how to resolve conflicting link types bugzilla@jessica.w3.org
• [Bug 12145] New: define how to resolve conflicting link types bugzilla@jessica.w3.org
• [Bug 11447] Please document in the decision policy the procedure for reopening an issue bugzilla@jessica.w3.org

Sunday, 20 February 2011

• [Bug 12138] how about cammand "top up deposit" in file document PHP ? bugzilla@jessica.w3.org
• [Bug 12137] how about cammand "top up deposit" in file document PHP ? bugzilla@jessica.w3.org
• [Bug 12141] Specifically state that all <track> options be exposed to the end user bugzilla@jessica.w3.org
• [Bug 12142] 2d.drawImage.wrongtype partially incorrect bugzilla@jessica.w3.org
• [Bug 12142] New: 2d.drawImage.wrongtype partially incorrect bugzilla@jessica.w3.org
• [Bug 11856] what happens when nothing happens in the getData() algorithm? bugzilla@jessica.w3.org
• [Bug 12141] Specifically state that all <track> options be exposed to the end user bugzilla@jessica.w3.org
• [Bug 12141] Specifically state that all <track> options be exposed to the end user bugzilla@jessica.w3.org

Saturday, 19 February 2011

• [Bug 12141] Specifically state that all <track> options be exposed to the end user bugzilla@jessica.w3.org
• [Bug 12141] New: Specifically state that all <track> options be exposed to the end user bugzilla@jessica.w3.org
• [Bug 12140] Why is there no getTransform() method? bugzilla@jessica.w3.org
• [Bug 12140] Why is there no getTransform() method? bugzilla@jessica.w3.org
• [Bug 12140] New: Why is there no getTransform() method? bugzilla@jessica.w3.org
• [Bug 12072] Comments before <!DOCTYPE html> should be forbidden bugzilla@jessica.w3.org
• [Bug 12138] New: how about cammand "top up deposit" in file document PHP ? bugzilla@jessica.w3.org
• [Bug 12137] New: how about cammand "top up deposit" in file document PHP ? bugzilla@jessica.w3.org
• [Bug 12136] New: how about command for "top up deposit" in file document? I need help, please.?? bugzilla@jessica.w3.org
• [Bug 12135] New: Step 4 should abort the substeps if there is no base element. bugzilla@jessica.w3.org
• [Bug 12134] New: Supporting dotted/dashed lines is definitely necessary bugzilla@jessica.w3.org
• [Bug 11699] When calling input.focus(), should (a) the cursor be at the start, (b) the cursor be at the end or (c) the contents be selected? Please define bugzilla@jessica.w3.org
• [Bug 11881] In step 9.3.1 missing "its" in "and (its) value is not the empty string" bugzilla@jessica.w3.org
• [Bug 11305] Remove stuff present in DOM Core bugzilla@jessica.w3.org
• [Bug 12094] Switch from relying on DOM Level 3 Core to Web DOM Core bugzilla@jessica.w3.org
• [Bug 12123] File Streaming bugzilla@jessica.w3.org
• [Bug 12122] AJAX File Uploads bugzilla@jessica.w3.org
• [Bug 12121] Cam Input bugzilla@jessica.w3.org
• [Bug 12120] Microphone input bugzilla@jessica.w3.org
• [Bug 12128] Add link type: dofollow bugzilla@jessica.w3.org
• [Bug 12122] AJAX File Uploads bugzilla@jessica.w3.org
• [Bug 11838] In Gecko, Opera, and IE, the "name" property on Window is replaceable bugzilla@jessica.w3.org
• [Bug 11838] In Gecko, Opera, and IE, the "name" property on Window is replaceable bugzilla@jessica.w3.org
• [Bug 11838] In Gecko, Opera, and IE, the "name" property on Window is replaceable bugzilla@jessica.w3.org
• [Bug 11838] In Gecko, Opera, and IE, the "name" property on Window is replaceable bugzilla@jessica.w3.org
• [Bug 11699] When calling input.focus(), should (a) the cursor be at the start, (b) the cursor be at the end or (c) the contents be selected? Please define bugzilla@jessica.w3.org
• [Bug 11915] Suggestion: Instead of forbidding <u> and inventing <mark> you could as well redefine <u> to be what <mark> is intended for -- roughly the same idea as for <i> and <b>. Clearly not all old HTML4 <i> / <b> / <u> match what the new HTML5 <i> / <b> / <mark> bugzilla@jessica.w3.org
• [Bug 11699] When calling input.focus(), should (a) the cursor be at the start, (b) the cursor be at the end or (c) the contents be selected? Please define bugzilla@jessica.w3.org

Friday, 18 February 2011

• [Bug 11907] the event handler attributes in textTrack and TextTrackCue are marked as read only, and no other API such as addEventListener is indicated to set handlers. bugzilla@jessica.w3.org
• [Bug 11907] the event handler attributes in textTrack and TextTrackCue are marked as read only, and no other API such as addEventListener is indicated to set handlers. bugzilla@jessica.w3.org
• [Bug 11903] i think it'd be more convenient if explicit sections could be children of implicit sections, so you can use implicit sections in general and throw in an <aside> somewhere without breaking the outline. now if you want to throw in an <aside>, you need to ch bugzilla@jessica.w3.org
• [Bug 11889] HTMLInputElement section seems to say that mutable is similar to immutable bugzilla@jessica.w3.org
• [Bug 12031] Please provide example of fragment parsing w/o a contextElement bugzilla@jessica.w3.org
• [Bug 11856] what happens when nothing happens in the getData() algorithm? bugzilla@jessica.w3.org
• [Bug 11884] HAVE_ALL_DATA would be good for when the UA has finished downloading the entire media file. Also, a "loaded" or "progressend" event should be fired so users can know when a file has finished buffering. bugzilla@jessica.w3.org
• [Bug 11856] what happens when nothing happens in the getData() algorithm? bugzilla@jessica.w3.org
• [Bug 11881] In step 9.3.1 missing "its" in "and (its) value is not the empty string" bugzilla@jessica.w3.org
• [Bug 11881] In step 9.3.1 missing "its" in "and (its) value is not the empty string" bugzilla@jessica.w3.org
• [Bug 12133] New: references scroll event, but never fires bugzilla@jessica.w3.org
• [Bug 12132] New: references select event, but never fires bugzilla@jessica.w3.org
• [Bug 11879] Is the setting and getting of the "original insertion mode" here needed? bugzilla@jessica.w3.org
• [Bug 11838] In Gecko, Opera, and IE, the "name" property on Window is replaceable bugzilla@jessica.w3.org
• [Bug 11873] typo: "Metadata" link (in para after the table) points to "auto" definition" bugzilla@jessica.w3.org
• [Bug 11839] window.opener needs to be writable, not readonly (as it is in Gecko, Chrome, IE) bugzilla@jessica.w3.org
• [Bug 11839] window.opener needs to be writable, not readonly (as it is in Gecko, Chrome, IE) bugzilla@jessica.w3.org
• [Bug 11861] Need to say to spin the event loop until all sync sections have run before running a new script to make resourse selection algorithm predictable. See http://lists.whatwg.org/pipermail/whatwg-whatwg.org/2010-August/027878.html bugzilla@jessica.w3.org
• [Bug 11861] Need to say to spin the event loop until all sync sections have run before running a new script to make resourse selection algorithm predictable. See http://lists.whatwg.org/pipermail/whatwg-whatwg.org/2010-August/027878.html bugzilla@jessica.w3.org
• [Bug 12128] New: Add link type: dofollow bugzilla@jessica.w3.org
• [Bug 12072] Comments before <!DOCTYPE html> should be forbidden bugzilla@jessica.w3.org
• [Bug 12029] Define a process for "particularly exceptional circumstances" bugzilla@jessica.w3.org
• [Bug 12106] 1. <quote> <!DOCTYPE HTML> </quote> Is this declaration part of an html document? Or is this part of a Document Type Definition (DTD)? Where are DTDs for html documents defined? 2. <title> Resource metadata management </title> <quote> A Document is always bugzilla@jessica.w3.org
• [Bug 12126] "User agents with no scripting support" is italic, which none of the other subheadings here are. bugzilla@jessica.w3.org
• [Bug 12126] New: "User agents with no scripting support" is italic, which none of the other subheadings here are. bugzilla@jessica.w3.org
• [Bug 12100] UAs do not actually convert DOMStrings to sequences of Unicode characters. Test case: data:text/html,<!doctype html><script>document.documentElement.title = "\ud800"; alert(document.documentElement.title.charCodeAt(0));</script> Expected 65533, got 5529 bugzilla@jessica.w3.org
• [Bug 12125] New: [CSSUI] should link to dev.w3.org, not TR/ bugzilla@jessica.w3.org
• [Bug 12123] File Streaming bugzilla@jessica.w3.org
• [Bug 12122] AJAX File Uploads bugzilla@jessica.w3.org
• [Bug 12121] Cam Input bugzilla@jessica.w3.org
• [Bug 12120] Microphone input bugzilla@jessica.w3.org
• [Bug 11796] HTML5 SUGGESTIONS ------------------------------ This file contains suggestions of tags / features that can be added to HTML5. I sincerely hope that these features are added especially the file tag (<file></file>) which is the last I would write on. I hav bugzilla@jessica.w3.org
• [Bug 12123] New: File Streaming bugzilla@jessica.w3.org
• [Bug 12122] New: AJAX File Uploads bugzilla@jessica.w3.org
• [Bug 12121] New: Cam Input bugzilla@jessica.w3.org
• [Bug 12120] New: Microphone input bugzilla@jessica.w3.org
• [Bug 12119] This section is not clear about how to make a progress element transition from determinate to indeterminate. As written, it sounds as if I'd have to call removeAttribute('value') to make it go into indeterminate mode. But I suspect that the intent is th bugzilla@jessica.w3.org
• [Bug 12119] New: This section is not clear about how to make a progress element transition from determinate to indeterminate. As written, it sounds as if I'd have to call removeAttribute('value') to make it go into indeterminate mode. But I suspect that the intent is th bugzilla@jessica.w3.org
• [Bug 12117] Coordination bugzilla@jessica.w3.org
• [Bug 12072] Comments before <!DOCTYPE html> should be forbidden bugzilla@jessica.w3.org
• [Bug 12117] New: Coordination bugzilla@jessica.w3.org
• [Bug 12116] New: The non-normative box says that the elements property is an HTMLCollection, but it is actually an HTMLFormControlsCollection bugzilla@jessica.w3.org
• [Bug 12097] Very beautiful article bugzilla@jessica.w3.org
• [Bug 12097] Very beautiful article bugzilla@jessica.w3.org
• [Bug 12098] Very beautiful article bugzilla@jessica.w3.org
• [Bug 11887] Remove useless input.valueAsNumber. Pretty much the same functionality can be achieved using parseFloat or parseInt bugzilla@jessica.w3.org
• [Bug 11887] Remove useless input.valueAsNumber. Pretty much the same functionality can be achieved using parseFloat or parseInt bugzilla@jessica.w3.org
• [Bug 12072] Comments before <!DOCTYPE html> should be forbidden bugzilla@jessica.w3.org

Thursday, 17 February 2011

• [Bug 12072] Comments before <!DOCTYPE html> should be forbidden bugzilla@jessica.w3.org
• [Bug 12072] Comments before <!DOCTYPE html> should be forbidden bugzilla@jessica.w3.org
• [Bug 11984] Simplify <video> for implementors and authors by ignoring the Content-Type HTTP header bugzilla@jessica.w3.org
• [Bug 11984] Simplify <video> for implementors and authors by ignoring the Content-Type HTTP header bugzilla@jessica.w3.org
• [Bug 12110] New: The margin note shows no support but at least IE 8 and Firefox 3.6 support dropzone=link for an image. So does Chrome 9, which also supports dropzone=move (when the origin has editable content). bugzilla@jessica.w3.org
• [Bug 11984] Simplify <video> for implementors and authors by ignoring the Content-Type HTTP header bugzilla@jessica.w3.org
• [Bug 12029] Define a process for "particularly exceptional circumstances" bugzilla@jessica.w3.org
• [Bug 12107] mp3 not supported bugzilla@jessica.w3.org
• [Bug 12107] mp3 not supported bugzilla@jessica.w3.org
• [Bug 11984] Simplify <video> for implementors and authors by ignoring the Content-Type HTTP header bugzilla@jessica.w3.org
• [Bug 11984] Simplify <video> for implementors and authors by ignoring the Content-Type HTTP header bugzilla@jessica.w3.org
• [Bug 12107] New: mp3 not supported bugzilla@jessica.w3.org
• [Bug 12072] Comments before <!DOCTYPE html> should be forbidden bugzilla@jessica.w3.org
• [Bug 12029] Define a process for "particularly exceptional circumstances" bugzilla@jessica.w3.org
• [Bug 11984] Simplify <video> for implementors and authors by ignoring the Content-Type HTTP header bugzilla@jessica.w3.org
• [Bug 12106] New: 1. <quote> <!DOCTYPE HTML> </quote> Is this declaration part of an html document? Or is this part of a Document Type Definition (DTD)? Where are DTDs for html documents defined? 2. <title> Resource metadata management </title> <quote> A Document is always bugzilla@jessica.w3.org
• [Bug 11706] Why -00:00 instead of +00:00 when time zone is UTC? bugzilla@jessica.w3.org
• [Bug 12104] Typo: will will bugzilla@jessica.w3.org
• [Bug 12104] New: Type: will will bugzilla@jessica.w3.org
• [Bug 11483] What should selectionStart/End return when there is no selection and no cursor? e.g. display:none bugzilla@jessica.w3.org
• [Bug 9429] Unobsolete the <strike> element - instead suggest how to use it bugzilla@jessica.w3.org
• [Bug 12100] UAs do not actually convert DOMStrings to sequences of Unicode characters. Test case: data:text/html,<!doctype html><script>document.documentElement.title = "\ud800"; alert(document.documentElement.title.charCodeAt(0));</script> Expected 65533, got 5529 bugzilla@jessica.w3.org
• [Bug 12072] Comments before <!DOCTYPE html> should be forbidden bugzilla@jessica.w3.org
• [Bug 10830] i18n comment : Please add support for rb bugzilla@jessica.w3.org
• [Bug 12103] New: currently no browser supports seamless attribute on iframes, frameborder and scrolling should not cause validation errors in HTML5. They should be allowed but not recommended possibly. bugzilla@jessica.w3.org
• [Bug 11815] should add something about /favicon.ico too bugzilla@jessica.w3.org
• [Bug 11815] should add something about /favicon.ico too bugzilla@jessica.w3.org
• [Bug 11706] Why -00:00 instead of +00:00 when time zone is UTC? bugzilla@jessica.w3.org
• [Bug 11706] Why -00:00 instead of +00:00 when time zone is UTC? bugzilla@jessica.w3.org
• [Bug 11499] make clear whether value attribute on input[type='button'] element can be empty bugzilla@jessica.w3.org
• [Bug 11499] make clear whether value attribute on input[type='button'] element can be empty bugzilla@jessica.w3.org
• [Bug 11483] What should selectionStart/End return when there is no selection and no cursor? e.g. display:none bugzilla@jessica.w3.org
• [Bug 11483] What should selectionStart/End return when there is no selection and no cursor? e.g. display:none bugzilla@jessica.w3.org
• [Bug 11666] The value sanitisation algorithm should be clear that it sets the value property to the sanitized form. This is explicit in several cases but implicit in several cases. bugzilla@jessica.w3.org
• [Bug 12091] HTMLdocument named-item getter and object fallback bugzilla@jessica.w3.org
• [Bug 12094] Switch from relying on DOM Level 3 Core to Web DOM Core bugzilla@jessica.w3.org
• [Bug 12101] New: "Structured clone" can be passed an object with a hostile getter that returns an object identical to itself; "structured clone" does not prevent such an infinite regression. bugzilla@jessica.w3.org
• [Bug 12099] Input type=url: value range bugzilla@jessica.w3.org
• [Bug 12099] Input type=url: value range bugzilla@jessica.w3.org
• [Bug 12096] Firefox uses the last meta refresh rather than the first. Test case: http://jsfiddle.net/J58rd/ bugzilla@jessica.w3.org
• [Bug 12094] Switch from relying on DOM Level 3 Core to Web DOM Core bugzilla@jessica.w3.org
• [Bug 12091] HTMLdocument named-item getter and object fallback bugzilla@jessica.w3.org
• [Bug 11068] We should not pause() if the element is removed from a document and then reinserted in the same task, since otherwise that could cause stuttering when moving a video from one frame to another, and would break autoplay when used with innerHTML. bugzilla@jessica.w3.org
• [Bug 11068] We should not pause() if the element is removed from a document and then reinserted in the same task, since otherwise that could cause stuttering when moving a video from one frame to another, and would break autoplay when used with innerHTML. bugzilla@jessica.w3.org
• [Bug 12095] <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <!-- saved from url=(0023)http://officena.com/ib/ --> </STYLE><!-- // please keep these lines on when you copy the source // made by: Nicolas - http://www.javascript-page.com var mymessage = " bugzilla@jessica.w3.org
• [Bug 12095] <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <!-- saved from url=(0023)http://officena.com/ib/ --> </STYLE><!-- // please keep these lines on when you copy the source // made by: Nicolas - http://www.javascript-page.com var mymessage = " bugzilla@jessica.w3.org
• [Bug 12072] Comments before <!DOCTYPE html> should be forbidden bugzilla@jessica.w3.org

Wednesday, 16 February 2011

• [Bug 12072] Comments before <!DOCTYPE html> should be forbidden bugzilla@jessica.w3.org
• [Bug 12073] Permit restricted use of <?xml version="1.0" encoding="UTF-8" ?> bugzilla@jessica.w3.org
• [Bug 12073] Permit restricted use of <?xml version="1.0" encoding="UTF-8" ?> bugzilla@jessica.w3.org
• [Bug 12072] Comments before <!DOCTYPE html> should be forbidden bugzilla@jessica.w3.org
• [Bug 12100] UAs do not actually convert DOMStrings to sequences of Unicode characters. Test case: data:text/html,<!doctype html><script>document.documentElement.title = "\ud800"; alert(document.documentElement.title.charCodeAt(0));</script> Expected 65533, got 5529 bugzilla@jessica.w3.org
• [Bug 12100] New: UAs do not actually convert DOMStrings to sequences of Unicode characters. Test case: data:text/html,<!doctype html><script>document.documentElement.title = "\ud800"; alert(document.documentElement.title.charCodeAt(0));</script> Expected 65533, got 5529 bugzilla@jessica.w3.org
• [Bug 12099] Input type=url: value range bugzilla@jessica.w3.org
• [Bug 12096] Firefox uses the last meta refresh rather than the first. Test case: http://jsfiddle.net/J58rd/ bugzilla@jessica.w3.org
• [Bug 11829] parts of default stylesheet setting unicode-bidi and direction should be normative bugzilla@jessica.w3.org
• [Bug 11829] parts of default stylesheet setting unicode-bidi and direction should be normative bugzilla@jessica.w3.org
• [Bug 12072] Comments before <!DOCTYPE html> should be forbidden bugzilla@jessica.w3.org
• [Bug 12072] Comments before <!DOCTYPE html> should be forbidden bugzilla@jessica.w3.org
• [Bug 12072] Comments before <!DOCTYPE html> should be forbidden bugzilla@jessica.w3.org
• [Bug 11829] parts of default stylesheet setting unicode-bidi and direction should be normative bugzilla@jessica.w3.org
• [Bug 12072] Comments before <!DOCTYPE html> should be forbidden bugzilla@jessica.w3.org
• [Bug 11734] Document the special effect of dir=auto on <pre> and <textarea> bugzilla@jessica.w3.org
• [Bug 11473] Clarify proper tabindex usage bugzilla@jessica.w3.org
• [Bug 11829] parts of default stylesheet setting unicode-bidi and direction should be normative bugzilla@jessica.w3.org
• [Bug 11891] add role attribute to list of global attributes and add definition for it bugzilla@jessica.w3.org
• [Bug 11734] Document the special effect of dir=auto on <pre> and <textarea> bugzilla@jessica.w3.org
• [Bug 11891] add role attribute to list of global attributes and add definition for it bugzilla@jessica.w3.org
• [Bug 11970] onsubmit on element form: invalid return bugzilla@jessica.w3.org
• [Bug 10823] i18n comment 19 : when an input value is remembered, its direction should be remembered too bugzilla@jessica.w3.org
• [Bug 12099] Input type=url: value range bugzilla@jessica.w3.org
• [Bug 11892] explicitly state that ARIA states and properties are formal/normative HTML attributes bugzilla@jessica.w3.org
• [Bug 12072] Comments before <!DOCTYPE html> should be forbidden bugzilla@jessica.w3.org
• [Bug 10823] i18n comment 19 : when an input value is remembered, its direction should be remembered too bugzilla@jessica.w3.org
• [Bug 11891] add role attribute to list of global attributes and add definition for it bugzilla@jessica.w3.org
• [Bug 11182] "tag" link relation underspecified bugzilla@jessica.w3.org
• [Bug 12099] New: Input type=url: value range bugzilla@jessica.w3.org
• [Bug 11891] add role attribute to list of global attributes and add definition for it bugzilla@jessica.w3.org
• [Bug 12098] New: Very beautiful article bugzilla@jessica.w3.org
• [Bug 12097] New: Very beautiful article bugzilla@jessica.w3.org
• [Bug 12096] New: Firefox uses the last meta refresh rather than the first. Test case: http://jsfiddle.net/J58rd/ bugzilla@jessica.w3.org
• [Bug 11857] getData() with no or too many arguments should throw bugzilla@jessica.w3.org
• [Bug 12073] Permit restricted use of <?xml version="1.0" encoding="UTF-8" ?> bugzilla@jessica.w3.org
• [Bug 12095] New: <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <!-- saved from url=(0023)http://officena.com/ib/ --> </STYLE><!-- // please keep these lines on when you copy the source // made by: Nicolas - http://www.javascript-page.com var mymessage = " bugzilla@jessica.w3.org
• [Bug 12073] Permit restricted use of <?xml version="1.0" encoding="UTF-8" ?> bugzilla@jessica.w3.org
• [Bug 12072] Comments before <!DOCTYPE html> should be forbidden bugzilla@jessica.w3.org
• [Bug 11452] 4.10.22.5.5. should describe how to send the filename when the field is a file field. It should send the filename as "filename" parameter and its character encoding must be _charset_. bugzilla@jessica.w3.org
• [Bug 11895] Make Downloads more reliable by specifying checksums bugzilla@jessica.w3.org
• [Bug 11891] add role attribute to list of global attributes and add definition for it bugzilla@jessica.w3.org
• [Bug 11864] section "12 IANA considerations 12.1 text/html" suggests: "This registration is for community review and will be submitted to ...registration with IANA." I understand from this that it it intended to replace RFC 2854. If so I have a problem with the stat bugzilla@jessica.w3.org
• [Bug 11876] text position bugzilla@jessica.w3.org
• [Bug 11863] Should the text say something explicitly about successive br elements, commonly used for vertical spacing? bugzilla@jessica.w3.org
• [Bug 11832] More exhaustive definition of itemValue needed bugzilla@jessica.w3.org
• [Bug 11860] It might be interesting to allow an application to register itself as a (HTTP) proxy for an unknown scheme. bugzilla@jessica.w3.org
• [Bug 11626] The specification says "Time-zone offsets differ based on daylight savings time." In that case, how would you represent a time w/o date in a specific time zone? For example, how would you code "Online tech support chat hours are <time datetime="09:00:00-0 bugzilla@jessica.w3.org
• [Bug 11229] Try making an author-specific edition that has one page per section, a tree on the side, and ben's styles, as per http://www.reddit.com/r/programming/comments/dzww6/who_edits_the_w3c_specs_they_look_like_a_ransom/c14ilc2 bugzilla@jessica.w3.org
• [Bug 11473] Clarify proper tabindex usage bugzilla@jessica.w3.org
• [Bug 11773] Re: applet obsoleted It seems that the committee is being deliberately hostile to Java applets. This is based on the fact that, with the proposed change, it will no longer be possible to include an applet in such a way as to be compatible with all browse bugzilla@jessica.w3.org
• [Bug 11837] remove Matroska example bugzilla@jessica.w3.org
• [Bug 11828] Drop hgroup completely until more research has been conducted bugzilla@jessica.w3.org
• [Bug 11748] The "size" attribute is disallowed, but may be useful on input="file". IE, Firefox and Opera all implement it, allowing you to reliably change the size of the file path textbox (Webkit browsers don't use a textbox). Styling the file upload file using CSS, bugzilla@jessica.w3.org
• [Bug 12073] Permit restricted use of <?xml version="1.0" encoding="UTF-8" ?> bugzilla@jessica.w3.org
• [Bug 11720] At the moment, chrome and opera thinks that iframe with source equal to data url has *not* the same origin as parent window's document. I think that this behavior is much more useful, because it can be used as a simpliest way of sandboxing of content. bugzilla@jessica.w3.org
• [Bug 11535] tabIndex IDL default is −1 for elements that are not focusable, but if the tabindex value is negative integer, the element can still be focused. bugzilla@jessica.w3.org
• [Bug 11837] remove Matroska example bugzilla@jessica.w3.org
• [Bug 11482] Requiring MIME types like application/vnd.openxmlformats-officedocument.wordprocessingml.document in order to allow a .docx file to be uploaded is far too technical for the layman. On the other hand it is equally impractical for web developers to keep an bugzilla@jessica.w3.org
• [Bug 11592] Browsers use customizable dictionaries to correct spelling and tend to mark some names as wrong, that it shouldn't. Maybe each website can inform the browser of words/names it expects to be used and add it (in the scope of that page) to the exceptions. If bugzilla@jessica.w3.org
• [Bug 11614] AAC and MP4 are ABSOLUTELY not acceptable for the open web. I don't care how many strings Apple are pulling - keep your patented encumbered trash - we don't want it. bugzilla@jessica.w3.org
• [Bug 11671] Input Elements with state color and range and their attributes. bugzilla@jessica.w3.org
• [Bug 11837] remove Matroska example bugzilla@jessica.w3.org
• [Bug 11719] [pending stable DOM Core] hasAttribute() also needs lowercasing. (This is already correct in Web DOM Core) bugzilla@jessica.w3.org
• [Bug 11717] [pending stable DOM Core] Element.removeAttribute() needs to lowercase its argument when used on an HTML element. (Don't add anything for removeAttributeNode.) bugzilla@jessica.w3.org
• [Bug 11812] The align attribute on the td and th elements should be conforming bugzilla@jessica.w3.org
• [Bug 12043] For better compatibility with .SRT, could the FULL STOP be replaced with a COMMA? So instead of 00:00:00.000 it would be 00:00:00,000 bugzilla@jessica.w3.org
• [Bug 11837] remove Matroska example bugzilla@jessica.w3.org
• [Bug 12094] Switch from relying on DOM Level 3 Core to Web DOM Core bugzilla@jessica.w3.org
• [Bug 11829] parts of default stylesheet setting unicode-bidi and direction should be normative bugzilla@jessica.w3.org
• [Bug 12043] For better compatibility with .SRT, could the FULL STOP be replaced with a COMMA? So instead of 00:00:00.000 it would be 00:00:00,000 bugzilla@jessica.w3.org
• [Bug 11719] [pending stable DOM Core] hasAttribute() also needs lowercasing. (This is already correct in Web DOM Core) bugzilla@jessica.w3.org
• [Bug 12094] Switch from relying on DOM Level 3 Core to Web DOM Core bugzilla@jessica.w3.org
• [Bug 11235] Support a rel attribute that restricts cookie transmission bugzilla@jessica.w3.org
• [Bug 11235] Support a rel attribute that restricts cookie transmission bugzilla@jessica.w3.org
• [Bug 12094] New: Switch from relying on DOM Level 3 Core to Web DOM Core bugzilla@jessica.w3.org
• [Bug 11842] Default track enabling for video elements seems to miss a qualifier bugzilla@jessica.w3.org
• [Bug 11842] Default track enabling for video elements seems to miss a qualifier bugzilla@jessica.w3.org
• [Bug 11833] Is the logic in 'valueAsNumber' overridable? For example, if the web page wants to accept a number formatted with commas "145,000" will that be allowed? bugzilla@jessica.w3.org
• [Bug 11719] [pending stable DOM Core] hasAttribute() also needs lowercasing. (This is already correct in Web DOM Core) bugzilla@jessica.w3.org
• [Bug 11204] [pending stable DOM Parsing] innerHTML on MathML elements bugzilla@jessica.w3.org
• [Bug 11857] getData() with no or too many arguments should throw bugzilla@jessica.w3.org
• [Bug 12043] For better compatibility with .SRT, could the FULL STOP be replaced with a COMMA? So instead of 00:00:00.000 it would be 00:00:00,000 bugzilla@jessica.w3.org
• [Bug 11858] fix title in ORIGIN reference bugzilla@jessica.w3.org
• [Bug 11858] fix title in ORIGIN reference bugzilla@jessica.w3.org
• [Bug 12044] Feature request: Give developers an option to disable a context's image smoothing bugzilla@jessica.w3.org
• [Bug 11892] explicitly state that ARIA states and properties are formal/normative HTML attributes bugzilla@jessica.w3.org
• [Bug 11204] innerHTML on MathML elements bugzilla@jessica.w3.org
• [Bug 11797] <richtext> </richtext> This will provide a default rich text widget which is scriptable and should also support the Rich Text Format (RTF) Default widget implementation should be a text area with richtext controls above it. This will enable browsers to pr bugzilla@jessica.w3.org
• [Bug 11796] HTML5 SUGGESTIONS ------------------------------ This file contains suggestions of tags / features that can be added to HTML5. I sincerely hope that these features are added especially the file tag (<file></file>) which is the last I would write on. I hav bugzilla@jessica.w3.org
• [Bug 11826] Your leading nav element has no title, thus is in contradiction to the proposal. bugzilla@jessica.w3.org
• [Bug 11794] We should handle the case of a bunch of required controls all being hidden at once — the author shouldn't have to also go in an remove the 'required' attribute on each one. Maybe make hidden="" bar things from constraint validation? bugzilla@jessica.w3.org
• [Bug 11822] applet[align=bottom], embed[align=bottom], iframe[align=bottom], img[align=bottom], input[type=image][align=bottom], object[align=bottom] should not have vertical-align:baseline, but bottom bugzilla@jessica.w3.org
• [Bug 11822] applet[align=bottom], embed[align=bottom], iframe[align=bottom], img[align=bottom], input[type=image][align=bottom], object[align=bottom] should not have vertical-align:baseline, but bottom bugzilla@jessica.w3.org
• [Bug 11817] Copyright should go from 2004 to 2011 now. bugzilla@jessica.w3.org
• [Bug 11817] Copyright should go from 2004 to 2011 now. bugzilla@jessica.w3.org
• [Bug 11814] Pause on exit is not much use if the goal is to read the caption or display it using TTS since the caption has ceased to be relevant. Pause on entry might be more helpful bugzilla@jessica.w3.org
• [Bug 11970] onsubmit on element form: invalid return bugzilla@jessica.w3.org
• [Bug 12091] HTMLdocument named-item getter and object fallback bugzilla@jessica.w3.org
• [Bug 12091] New: HTMLdocument named-item getter and object fallback bugzilla@jessica.w3.org
• [Bug 11775] Hello, I'm just writing a quick note to question the non-inclusion of the "feed" link type (rel="feed") which I remember coming across a few months ago. When I originally saw the new rel type, I was very glad to see that there was finally a way to specify bugzilla@jessica.w3.org
• [Bug 12089] Under 4.8.11.1.2, Transformations, the specification reads: The transformations must be performed in reverse order. For instance, if a scale transformation that doubles the width is applied, followed by a rotation transformation that rotates drawing opera bugzilla@jessica.w3.org
• [Bug 12085] Please drop "The following features are defined in the DOM Range specification: [DOMRANGE]" and the following list; only Selection used those terms bugzilla@jessica.w3.org
• [Bug 12076] Wishlist: line-based parser bugzilla@jessica.w3.org
• [Bug 12073] Permit restricted use of <?xml version="1.0" encoding="UTF-8" ?> bugzilla@jessica.w3.org
• [Bug 12072] Comments before <!DOCTYPE html> should be forbidden bugzilla@jessica.w3.org
• [Bug 12072] Comments before <!DOCTYPE html> should be forbidden bugzilla@jessica.w3.org
• [Bug 12069] A div element with display: inline, inline-block or inline-table should be considered as phrasing content. bugzilla@jessica.w3.org
• [Bug 12061] step 3 says to "set the node to the context element", but I do not see "context element" defined anywhere. Should that be the "current node" or perhaps "current table"? bugzilla@jessica.w3.org
• [Bug 12059] new normative ref to DOMRANGE bugzilla@jessica.w3.org
• [Bug 12059] new normative ref to DOMRANGE bugzilla@jessica.w3.org
• [Bug 12050] <img src="#my file"... doesnt display image bugzilla@jessica.w3.org

Tuesday, 15 February 2011

• [Bug 12072] Comments before <!DOCTYPE html> should be forbidden bugzilla@jessica.w3.org
• [Bug 12073] Permit restricted use of <?xml version="1.0" encoding="UTF-8" ?> bugzilla@jessica.w3.org
• [Bug 10828] i18n comment 4 : at least by default, <br> should constitute a bidi paragraph break bugzilla@jessica.w3.org
• [Bug 10828] i18n comment 4 : at least by default, <br> should constitute a bidi paragraph break bugzilla@jessica.w3.org
• [Bug 12072] Comments before <!DOCTYPE html> should be forbidden bugzilla@jessica.w3.org
• [Bug 12073] Permit restricted use of <?xml version="1.0" encoding="UTF-8" ?> bugzilla@jessica.w3.org
• [Bug 12089] Under 4.8.11.1.2, Transformations, the specification reads: The transformations must be performed in reverse order. For instance, if a scale transformation that doubles the width is applied, followed by a rotation transformation that rotates drawing opera bugzilla@jessica.w3.org
• [Bug 12088] Under 4.8.11.1.2, Transformations, the specification reads: The transformations must be performed in reverse order. For instance, if a scale transformation that doubles the width is applied, followed by a rotation transformation that rotates drawing opera bugzilla@jessica.w3.org
• [Bug 11162] select.size should either be web-compatible or make sense, take your pick bugzilla@jessica.w3.org
• [Bug 11746] Add video, object, img, input[type=image], embed, canvas { overflow: hidden; } since people don't expect these elements to overflow in combination with object-fit:cover (see https://bugs.webkit.org/show_bug.cgi?id=52103 ) bugzilla@jessica.w3.org
• [Bug 11745] Feature request: element.replaceSelection(str) for text fields bugzilla@jessica.w3.org
• [Bug 12089] New: Under 4.8.11.1.2, Transformations, the specification reads: The transformations must be performed in reverse order. For instance, if a scale transformation that doubles the width is applied, followed by a rotation transformation that rotates drawing opera bugzilla@jessica.w3.org
• [Bug 12088] New: Under 4.8.11.1.2, Transformations, the specification reads: The transformations must be performed in reverse order. For instance, if a scale transformation that doubles the width is applied, followed by a rotation transformation that rotates drawing opera bugzilla@jessica.w3.org
• [Bug 10808] text with unknown direction gets corrupted when inserted in content with opposite direction bugzilla@jessica.w3.org
• [Bug 12053] The current default ARIA role for the summary element in HTML5 is nonsensical bugzilla@jessica.w3.org
• [Bug 12086] adsfa sdfasdfasdfadsfasdf adsf asdf bugzilla@jessica.w3.org
• [Bug 12086] New: adsfa sdfasdfasdfadsfasdf adsf asdf bugzilla@jessica.w3.org
• [Bug 12085] New: Please drop "The following features are defined in the DOM Range specification: [DOMRANGE]" and the following list; only Selection used those terms bugzilla@jessica.w3.org
• [Bug 12084] New: application/microdata+json fragment identifiers not really defined bugzilla@jessica.w3.org
• [Bug 11896] html-letter.pdf appears truncated bugzilla@jessica.w3.org
• [Bug 12074] dgdfgdterte te rte rt er tertwe te r bugzilla@jessica.w3.org
• [Bug 12075] Step 12/17: header xref'd to #the-header-element bugzilla@jessica.w3.org
• [Bug 11871] type.delete.html to become invalid bugzilla@jessica.w3.org
• [Bug 12069] A div element with display: inline, inline-block or inline-table should be considered as phrasing content. bugzilla@jessica.w3.org
• [Bug 12072] Comments before <!DOCTYPE html> should be forbidden bugzilla@jessica.w3.org
• [Bug 12076] Wishlist: line-based parser bugzilla@jessica.w3.org
• [Bug 12076] Wishlist: line-based parser bugzilla@jessica.w3.org
• [Bug 12076] New: Wishlist: line-based parser bugzilla@jessica.w3.org
• [Bug 12075] Step 12/17: header xref'd to #the-header-element bugzilla@jessica.w3.org
• [Bug 12068] Make window.onerror more useful bugzilla@jessica.w3.org
• [Bug 12068] Make window.onerror more useful bugzilla@jessica.w3.org
• [Bug 12072] Comments before <!DOCTYPE html> should be forbidden bugzilla@jessica.w3.org
• [Bug 12075] New: Step 12/17: header xref'd to #the-header-element bugzilla@jessica.w3.org
• [Bug 11984] Simplify <video> for implementors and authors by ignoring the Content-Type HTTP header bugzilla@jessica.w3.org
• [Bug 12072] Comments before <!DOCTYPE html> should be forbidden bugzilla@jessica.w3.org
• [Bug 12074] New: dgdfgdterte te rte rt er tertwe te r bugzilla@jessica.w3.org
• [Bug 12073] Permit restricted use of <?xml version="1.0" encoding="UTF-8" ?> bugzilla@jessica.w3.org
• [Bug 11737] Change content model of <hgroup> to single <hx> + zero or more <sh> (sub/suphead) elements bugzilla@jessica.w3.org
• [Bug 11737] Change content model of <hgroup> to single <hx> + zero or more <sh> (sub/suphead) elements bugzilla@jessica.w3.org
• [Bug 12073] Permit restricted use of <?xml version="1.0" encoding="UTF-8" ?> bugzilla@jessica.w3.org
• [Bug 12072] Comments before <!DOCTYPE html> should be forbidden bugzilla@jessica.w3.org
• [Bug 12073] New: Permit restricted use of <?xml version="1.0" encoding="UTF-8" ?> bugzilla@jessica.w3.org
• [Bug 12072] Comments before <!DOCTYPE html> should be forbidden bugzilla@jessica.w3.org
• [Bug 11984] Simplify <video> for implementors and authors by ignoring the Content-Type HTTP header bugzilla@jessica.w3.org
• [Bug 12072] New: Comments before <!DOCTYPE html> should be forbidden bugzilla@jessica.w3.org
• [Bug 11568] dragenter should be fired after dragleave bugzilla@jessica.w3.org
• [Bug 11568] dragenter should be fired after dragleave bugzilla@jessica.w3.org
• [Bug 12068] Make window.onerror more useful bugzilla@jessica.w3.org
• [Bug 12069] New: A div element with display: inline, inline-block or inline-table should be considered as phrasing content. bugzilla@jessica.w3.org
• [Bug 10830] i18n comment : Please add support for rb bugzilla@jessica.w3.org
• [Bug 10828] i18n comment 4 : at least by default, <br> should constitute a bidi paragraph break bugzilla@jessica.w3.org
• [Bug 11211] Need a way to force a line wrap with the bidi semantics of LINE SEPARATOR when necessary. bugzilla@jessica.w3.org
• [Bug 10828] i18n comment 4 : at least by default, <br> should constitute a bidi paragraph break bugzilla@jessica.w3.org
• [Bug 10823] i18n comment 19 : when an input value is remembered, its direction should be remembered too bugzilla@jessica.w3.org
• [Bug 10823] i18n comment 19 : when an input value is remembered, its direction should be remembered too bugzilla@jessica.w3.org
• [Bug 11923] I'm not sure this is a good example; even if nested properly, having a <p> inside of <b> isn't valid. bugzilla@jessica.w3.org
• [Bug 11791] "margin-bottom;" should read "margin-bottom:" bugzilla@jessica.w3.org
• [Bug 11926] I used new blogger template but that template very much error, i just reduce a little error html. I can't do validate at document template. Can you help me to validate new blogger template from Blogspot. Thanks. bugzilla@jessica.w3.org
• [Bug 11953] I think you should cut the word "anyway" twice in step 1.Otherwise.1 and 1.Otherwise.2 bugzilla@jessica.w3.org
• [Bug 11791] "margin-bottom;" should read "margin-bottom:" bugzilla@jessica.w3.org
• [Bug 11801] [device] I think that for usb, some more desired use cases like smart card login and joystick support, would help adapt the proposal. bugzilla@jessica.w3.org
• [Bug 11782] The spec requires event handler content attributes to match ES5 FunctionBody, but has no similar requirement for <script> content. It probably should. bugzilla@jessica.w3.org
• [Bug 11782] The spec requires event handler content attributes to match ES5 FunctionBody, but has no similar requirement for <script> content. It probably should. bugzilla@jessica.w3.org
• [Bug 11781] "Event handler content attributes #event-handler-content-attributes Referenced in: 7.1.1 Introduction 7.1.6.1 Event handlers (2) (3) (4), when specified, must contain valid JavaScript code matching the FunctionBody production." might be wrong since it d bugzilla@jessica.w3.org
• [Bug 11781] "Event handler content attributes #event-handler-content-attributes Referenced in: 7.1.1 Introduction 7.1.6.1 Event handlers (2) (3) (4), when specified, must contain valid JavaScript code matching the FunctionBody production." might be wrong since it d bugzilla@jessica.w3.org
• [Bug 11778] downloadable font support missing bugzilla@jessica.w3.org
• [Bug 11775] Hello, I'm just writing a quick note to question the non-inclusion of the "feed" link type (rel="feed") which I remember coming across a few months ago. When I originally saw the new rel type, I was very glad to see that there was finally a way to specify bugzilla@jessica.w3.org
• [Bug 11774] what is a class ? bugzilla@jessica.w3.org
• [Bug 11271] misleading CVS ref in "status of this document" bugzilla@jessica.w3.org
• [Bug 11771] What is "also" in "a working group decision also from June 2010" in reference too? bugzilla@jessica.w3.org
• [Bug 11771] What is "also" in "a working group decision also from June 2010" in reference too? bugzilla@jessica.w3.org
• [Bug 11752] With the itemscope - it seems unnecessary since it becomes redundant whenever there's an itemtype - so why not have itemtype="item" bugzilla@jessica.w3.org
• [Bug 11746] Add video, object, img, input[type=image], embed, canvas { overflow: hidden; } since people don't expect these elements to overflow in combination with object-fit:cover (see https://bugs.webkit.org/show_bug.cgi?id=52103 ) bugzilla@jessica.w3.org
• [Bug 11753] Don't like "stating what he wishes to drag and what he wishes to drop". Surely you drop what you've dragged, and the question is "where to drop it"? bugzilla@jessica.w3.org
• [Bug 11753] Don't like "stating what he wishes to drag and what he wishes to drop". Surely you drop what you've dragged, and the question is "where to drop it"? bugzilla@jessica.w3.org
• [Bug 11745] Feature request: element.replaceSelection(str) for text fields bugzilla@jessica.w3.org
• [Bug 12065] Please point out that for <input type=file multiple> http://tools.ietf.org/html/rfc2388#section-4.2 should not be used. Instead each file should have its own field. Otherwise you break PHP. bugzilla@jessica.w3.org
• [Bug 11984] Simplify <video> for implementors and authors by ignoring the Content-Type HTTP header bugzilla@jessica.w3.org
• [Bug 11568] dragenter should be fired after dragleave bugzilla@jessica.w3.org

Monday, 14 February 2011

• [Bug 11734] Document the special effect of dir=auto on <pre> and <textarea> bugzilla@jessica.w3.org
• [Bug 11734] Document the special effect of dir=auto on <pre> and <textarea> bugzilla@jessica.w3.org
• [Bug 11734] Document the special effect of dir=auto on <pre> and <textarea> bugzilla@jessica.w3.org
• [Bug 11734] Document the special effect of dir=auto on <pre> and <textarea> bugzilla@jessica.w3.org
• [Bug 11734] Document the special effect of dir=auto on <pre> and <textarea> bugzilla@jessica.w3.org
• [Bug 11984] Simplify <video> for implementors and authors by ignoring the Content-Type HTTP header bugzilla@jessica.w3.org
• [Bug 11737] Change content model of <hgroup> to single <hx> + zero or more <sh> (sub/suphead) elements bugzilla@jessica.w3.org
• [Bug 12068] Make window.onerror more useful bugzilla@jessica.w3.org
• [Bug 12068] New: Make window.onerror more useful bugzilla@jessica.w3.org
• [Bug 11984] Simplify <video> for implementors and authors by ignoring the Content-Type HTTP header bugzilla@jessica.w3.org
• [Bug 11242] Canvas must define what HTML elements may be used in the DOM Subtree bugzilla@jessica.w3.org
• [Bug 11239] Canvas support accessible caret tracking independent of Focus Ring tracking bugzilla@jessica.w3.org
• [Bug 11238] Enable canvas to support accessible rich text editing bugzilla@jessica.w3.org
• [Bug 11323] Don't run scripts when the owner doc isn't the inserter parser's doc or when the owner doc is not the same at "run" and "execute" time bugzilla@jessica.w3.org
• [Bug 11323] Don't run scripts when the owner doc isn't the inserter parser's doc or when the owner doc is not the same at "run" and "execute" time bugzilla@jessica.w3.org
• [Bug 11323] Don't run scripts when the owner doc isn't the inserter parser's doc or when the owner doc is not the same at "run" and "execute" time bugzilla@jessica.w3.org
• [Bug 11984] Simplify <video> for implementors and authors by ignoring the Content-Type HTTP header bugzilla@jessica.w3.org
• [Bug 12065] Please point out that for <input type=file multiple> http://tools.ietf.org/html/rfc2388#section-4.2 should not be used. Instead each file should have its own field. Otherwise you break PHP. bugzilla@jessica.w3.org
• [Bug 11342] TextMetrics should include distance from textBaseline to each of the baselines in the text bugzilla@jessica.w3.org
• [Bug 12065] Please point out that for <input type=file multiple> http://tools.ietf.org/html/rfc2388#section-4.2 should not be used. Instead each file should have its own field. Otherwise you break PHP. bugzilla@jessica.w3.org
• [Bug 12065] Please point out that for <input type=file multiple> http://tools.ietf.org/html/rfc2388#section-4.2 should not be used. Instead each file should have its own field. Otherwise you break PHP. bugzilla@jessica.w3.org
• [Bug 12065] Please point out that for <input type=file multiple> http://tools.ietf.org/html/rfc2388#section-4.2 should not be used. Instead each file should have its own field. Otherwise you break PHP. bugzilla@jessica.w3.org
• [Bug 12065] New: Please point out that for <input type=file multiple> http://tools.ietf.org/html/rfc2388#section-4.2 should not be used. Instead each file should have its own field. Otherwise you break PHP. bugzilla@jessica.w3.org
• [Bug 11393] End tag fails to break out of foreign content bugzilla@jessica.w3.org
• [Bug 11298] Surrogate catching doesn't belong in input stream preprocessing bugzilla@jessica.w3.org
• [Bug 11426] Meta prescan should run on the first 1024 bytes bugzilla@jessica.w3.org
• [Bug 9593] Anchors in spec are not consistent bugzilla@jessica.w3.org
• [Bug 11090] Add a note about XSLT-created scripts bugzilla@jessica.w3.org
• [Bug 12062] New: UTF-8 BOM should not be forbidden in Polyglot Markup bugzilla@jessica.w3.org
• [Bug 11909] The principles of Polyglot Markup - validity? well-formed? DOM-equality? bugzilla@jessica.w3.org
• [Bug 11909] The principles of Polyglot Markup - validity? well-formed? DOM-equality? bugzilla@jessica.w3.org
• [Bug 12061] step 3 says to "set the node to the context element", but I do not see "context element" defined anywhere. Should that be the "current node" or perhaps "current table"? bugzilla@jessica.w3.org
• [Bug 12061] New: step 3 says to "set the node to the context element", but I do not see "context element" defined anywhere. Should that be the "current node" or perhaps "current table"? bugzilla@jessica.w3.org
• [Bug 11909] The principles of Polyglot Markup - validity? well-formed? DOM-equality? bugzilla@jessica.w3.org
• [Bug 12058] boilerplate doesn't list latest WD bugzilla@jessica.w3.org
• [Bug 12059] New: new normative ref to DOMRANGE bugzilla@jessica.w3.org
• [Bug 12058] New: boilerplate doesn't list latest WD bugzilla@jessica.w3.org
• [Bug 12055] Accidental change in http://html5.org/r/5845 ? bugzilla@jessica.w3.org
• [Bug 12055] New: Accidental change in http://html5.org/r/5845 ? bugzilla@jessica.w3.org
• [Bug 12050] <img src="#my file"... doesnt display image bugzilla@jessica.w3.org
• [Bug 12050] <img src="#my file"... doesnt display image bugzilla@jessica.w3.org
• [Bug 12050] <img src="#my file"... doesnt display image bugzilla@jessica.w3.org
• [Bug 12053] The current default ARIA role for the summary element in HTML5 is nonsensical bugzilla@jessica.w3.org
• [Bug 12049] Script defer/async attributed have no realistic usage scenario bugzilla@jessica.w3.org

Sunday, 13 February 2011

• [Bug 12050] <img src="#my file"... doesnt display image bugzilla@jessica.w3.org
• [Bug 12050] <img src="#my file"... doesnt display image bugzilla@jessica.w3.org
• [Bug 11910] @id values in polyglot markup should be XML-valid (or not?) bugzilla@jessica.w3.org
• [Bug 11910] @id values in polyglot markup should be XML-valid (or not?) bugzilla@jessica.w3.org
• [Bug 11909] The principles of Polyglot Markup - validity? well-formed? DOM-equality? bugzilla@jessica.w3.org
• [Bug 11905] Escaping of "<" and "&" in Polyglot Markup bugzilla@jessica.w3.org
• [Bug 10788] @srcdoc in polyglot documents bugzilla@jessica.w3.org
• [Bug 12054] New: clearly state that there must be only one character encoding declaration in a document bugzilla@jessica.w3.org
• [Bug 10152] [polyglot] i18n comment 5 : Mention lang and xml:lang bugzilla@jessica.w3.org
• [Bug 12053] New: The current default ARIA role for the summary element in HTML5 is nonsensical bugzilla@jessica.w3.org
• [Bug 11904] <plaintext> and <xmp> in Polyglot Markup bugzilla@jessica.w3.org
• [Bug 12049] Script defer/async attributed have no realistic usage scenario bugzilla@jessica.w3.org
• [Bug 12052] New: w3c error for header and nav element bugzilla@jessica.w3.org
• [Bug 12050] <img src="#my file"... doesnt display image bugzilla@jessica.w3.org
• [Bug 12050] <img src="#my file"... doesnt display image bugzilla@jessica.w3.org
• [Bug 12049] Script defer/async attributed have no realistic usage scenario bugzilla@jessica.w3.org
• [Bug 12049] Script defer/async attributed have no realistic usage scenario bugzilla@jessica.w3.org

Saturday, 12 February 2011

• [Bug 12049] Script defer/async attributed have no realistic usage scenario bugzilla@jessica.w3.org
• [Bug 12049] Script defer/async attributed have no realistic usage scenario bugzilla@jessica.w3.org
• [Bug 12050] New: <img src="#my file"... doesnt display image bugzilla@jessica.w3.org
• [Bug 12049] New: Script defer/async attributed have no realistic usage scenario bugzilla@jessica.w3.org
• [Bug 11999] poster frame algo doesn't handle absent poster attribute bugzilla@jessica.w3.org
• [Bug 11984] Simplify <video> for implementors and authors by ignoring the Content-Type HTTP header bugzilla@jessica.w3.org
• [Bug 11981] There's a race condition with autoplay if the autoplay attribute is removed in e.g. 'loadstart' event listener bugzilla@jessica.w3.org
• [Bug 11930] It's very common for many application to require access to the number of video frames, as well as to have the ability to seek to a given frame. Think of a video editor. There is no notion of a video frame here. We should add fields, like "currentFrame", a bugzilla@jessica.w3.org
• [Bug 12029] Define a process for "particularly exceptional circumstances" bugzilla@jessica.w3.org
• [Bug 12045] New: Update rgba serialization tests bugzilla@jessica.w3.org
• [Bug 12044] Feature request: Give developers an option to disable a context's image smoothing bugzilla@jessica.w3.org
• [Bug 11391] Provide examples of actual <track> usage, user agent implications bugzilla@jessica.w3.org
• [Bug 11593] the <track> @kind attribute should include the all of the identified accessibility content types bugzilla@jessica.w3.org
• [Bug 11755] The introduction should be clearer about use cases best addressed by polyglot markup bugzilla@jessica.w3.org
• [Bug 12043] For better compatibility with .SRT, could the FULL STOP be replaced with a COMMA? So instead of 00:00:00.000 it would be 00:00:00,000 bugzilla@jessica.w3.org
• [Bug 11910] @id values in polyglot markup should be XML-valid (or not?) bugzilla@jessica.w3.org
• [Bug 11910] @id values in polyglot markup should be XML-valid (or not?) bugzilla@jessica.w3.org
• [Bug 11909] The principles of Polyglot Markup - validity? well-formed? DOM-equality? bugzilla@jessica.w3.org
• [Bug 11905] Escaping of "<" and "&" in Polyglot Markup bugzilla@jessica.w3.org
• [Bug 11904] <plaintext> and <xmp> in Polyglot Markup bugzilla@jessica.w3.org
• [Bug 11754] Should clearly indicate that Web authors don't need to bother to make their content polyglot if they don't know they have a use case bugzilla@jessica.w3.org
• [Bug 10788] @srcdoc in polyglot documents bugzilla@jessica.w3.org
• [Bug 10152] [polyglot] i18n comment 5 : Mention lang and xml:lang bugzilla@jessica.w3.org
• [Bug 11343] Browsers allow *any* element to match :active between a mousedown on it and the subsequent mouseup. The definition of :active should change to match this behavior. bugzilla@jessica.w3.org
• [Bug 11343] Browsers allow *any* element to match :active between a mousedown on it and the subsequent mouseup. The definition of :active should change to match this behavior. bugzilla@jessica.w3.org
• [Bug 12044] Feature request: Give developers an option to disable a context's image smoothing bugzilla@jessica.w3.org
• [Bug 11338] Add note saying something like "In the HTML serialization, namespace prefixes and namespace declarations are non-conforming and are do not have the same effect as in XML..." bugzilla@jessica.w3.org
• [Bug 11338] Add note saying something like "In the HTML serialization, namespace prefixes and namespace declarations are non-conforming and are do not have the same effect as in XML..." bugzilla@jessica.w3.org
• [Bug 12044] Feature request: Give developers an option to disable a context's image smoothing bugzilla@jessica.w3.org
• [Bug 12044] Feature request: Give developers an option to disable a context's image smoothing (ie, anti-assailing) bugzilla@jessica.w3.org
• [Bug 11486] [pending ISSUE-118] Remove rel=archives in favor of rel=index. They are extremely similar and not that useful to have separately. bugzilla@jessica.w3.org
• [Bug 11488] drawImage(img), where img is SVG image with % height/width bugzilla@jessica.w3.org
• [Bug 12025] [bug?] how to handle this snippet? bugzilla@jessica.w3.org
• [Bug 12044] New: This is a new feature request. Request overview: Give developers an option to disable a context's image smoothing (ie, anti-assailing). Problem: When scaling up images, most user agents smooth the output. This is fine for most use cases, but is undesirabl bugzilla@jessica.w3.org

Friday, 11 February 2011

• [Bug 11587] [pending URL spec] window.location.hostname should remove brackets of IPv6 host bugzilla@jessica.w3.org
• [Bug 11587] [URL] window.location.hostname should remove brackets of IPv6 host bugzilla@jessica.w3.org
• [Bug 11085] Define what "this" value to use for setTimeout(function) bugzilla@jessica.w3.org
• [Bug 11085] Define what "this" value to use for setTimeout(function) bugzilla@jessica.w3.org
• [Bug 12043] For better compatibility with .SRT, could the FULL STOP be replaced with a COMMA? So instead of 00:00:00.000 it would be 00:00:00,000 bugzilla@jessica.w3.org
• [Bug 12043] New: For better compatibility with .SRT, could the FULL STOP be replaced with a COMMA? So instead of 00:00:00.000 it would be 00:00:00,000 bugzilla@jessica.w3.org
• [Bug 11253] Description of input event doesn't seem to match what browsers do bugzilla@jessica.w3.org
• [Bug 11391] Provide examples of actual <track> usage, user agent implications bugzilla@jessica.w3.org
• [Bug 11593] the <track> @kind attribute should include the all of the identified accessibility content types bugzilla@jessica.w3.org
• [Bug 11386] Defer <video> rendering (letterboxing) to CSS bugzilla@jessica.w3.org
• [Bug 11386] Defer <video> rendering (letterboxing) to CSS bugzilla@jessica.w3.org
• [Bug 11487] Include example of using <nav> paragraph-like. I.e. with inline links as seen on annevankesteren.nl. bugzilla@jessica.w3.org
• [Bug 11487] Include example of using <nav> paragraph-like. I.e. with inline links as seen on annevankesteren.nl. bugzilla@jessica.w3.org
• [Bug 11423] Character sets not registered with IANA bugzilla@jessica.w3.org
• [Bug 11486] Remove rel=archives in favor of rel=index. They are extremely similar and not that useful to have separately. bugzilla@jessica.w3.org
• [Bug 11709] People evaluating this spec should be allowed to download parts of it and go through them offline, in their favorite reading device. I'm currently interested in chapters 5 and 6, but I had to go to all sorts of trouble to get those in my iPad. Please prov bugzilla@jessica.w3.org
• [Bug 11610] The abbr element I suggest to add the for attribute, for abbreviations and acronyms defined inline. Some solution proposals: 1. <abbr>W3C</abbr> (<title for="W3C">World Wide Web Consortium</title>) 2. <abbr>CC</abbr> (<dfn for="CC">Creative Commons</dfn>) bugzilla@jessica.w3.org
• [Bug 11505] the problem i try to solve is spam pop ups and aggressive spam page authoring (which ban you from going backward and is obviously made up for banks and exploited by spammers). my idea is to depreciate (not allow) pop ups and also the annoying backward bro bugzilla@jessica.w3.org
• [Bug 12041] New: Probably this should be: "Labeling a resource with the application/microdata+json type asserts that the resource is a JSON text that consists of an object with a single entry called "items" consisting of an array of entries, each of which consists of an o bugzilla@jessica.w3.org
• [Bug 12029] Define a process for "particularly exceptional circumstances" bugzilla@jessica.w3.org
• [Bug 12031] Please provide example of fragment parsing w/o a contextElement bugzilla@jessica.w3.org
• [Bug 12029] Define a process for "particularly exceptional circumstances" bugzilla@jessica.w3.org
• [Bug 12029] Define a process for "particularly exceptional circumstances" bugzilla@jessica.w3.org
• [Bug 12029] Define a process for "particularly exceptional circumstances" bugzilla@jessica.w3.org
• [Bug 12037] math-parse01.html calls undefined function bugzilla@jessica.w3.org
• [Bug 12037] New: math-parse01.html calls undefined function bugzilla@jessica.w3.org
• [Bug 12029] Define a process for "particularly exceptional circumstances" bugzilla@jessica.w3.org
• [Bug 12029] Define a process for "particularly exceptional circumstances" bugzilla@jessica.w3.org
• [Bug 12035] Google Chrome 9.0 seems to support the meter element the intended way, so maybe you can update the implementation status info. bugzilla@jessica.w3.org
• [Bug 12035] New: Google Chrome 9.0 seems to support the meter element the intended way, so maybe you can update the implementation status info. bugzilla@jessica.w3.org
• [Bug 11924] "The ImageData object return must be filled with transparent black.": s/return/returned/ bugzilla@jessica.w3.org
• [Bug 11393] End tag fails to break out of foreign content bugzilla@jessica.w3.org
• [Bug 11955] The canvas should be tainted when drawing text with a cross-origin font (unless CORS was used to allow it) bugzilla@jessica.w3.org
• [Bug 11955] The canvas should be tainted when drawing text with a cross-origin font (unless CORS was used to allow it) bugzilla@jessica.w3.org
• [Bug 11955] The canvas should be tainted when drawing text with a cross-origin font (unless CORS was used to allow it) bugzilla@jessica.w3.org
• [Bug 11342] TextMetrics should include distance from textBaseline to each of the baselines in the text bugzilla@jessica.w3.org
• [Bug 11924] "The ImageData object return must be filled with transparent black.": s/return/returned/ bugzilla@jessica.w3.org
• [Bug 11924] "The ImageData object return must be filled with transparent black.": s/return/returned/ bugzilla@jessica.w3.org
• [Bug 11739] I would like to see a clearPath or clearStroke functions similar to clearRect but to clear lines, not just full rectangles bugzilla@jessica.w3.org
• [Bug 11900] it would be nice to specify a range for the lineWidth, eg, [1, 5], which means that the line starts at width 1, and gradually moves to width 5 at the end point bugzilla@jessica.w3.org
• [Bug 11890] Sometimes we need a pixel(x,y) method. createImageData(1,1) anj put it is slow. javascript is not as fast as c/c++ bugzilla@jessica.w3.org
• [Bug 11263] Most browsers seem to clear to transparent -white- by default, since this results in much nicer blended edges in antialiased-graphics. bugzilla@jessica.w3.org
• [Bug 11819] var c = document.getElementById('canvas'); var ctx = c.getContext('2d'); ctx.drawSvg(SVG_XML_OR_PATH_TO_SVG, dx, dy, dw, dh); bugzilla@jessica.w3.org
• [Bug 11488] drawImage(img), where img is SVG image with % height/width bugzilla@jessica.w3.org
• [Bug 11793] Canvas layers: have multiple drawing layers inside the canvas 2d context, right now to achieve this you must have multiple stacked canvases which isn't optimal bugzilla@jessica.w3.org
• [Bug 11744] setPixel (x,y, color)and getPixel(x,y) should be implemented. getPixel should return color value bugzilla@jessica.w3.org
• [Bug 11739] I would like to see a clearPath or clearStroke functions similar to clearRect but to clear lines, not just full rectangles bugzilla@jessica.w3.org
• [Bug 11488] drawImage(img), where img is SVG image with % height/width bugzilla@jessica.w3.org
• [Bug 11328] Canvas authors needs to be able to assess pixel resolution to rescale canvas elements bugzilla@jessica.w3.org
• [Bug 12031] Please provide example of fragment parsing w/o a contextElement bugzilla@jessica.w3.org
• [Bug 12030] "the user agent must follow the following steps" -- missing "run" or similar bugzilla@jessica.w3.org

Thursday, 10 February 2011

• [Bug 12031] Please provide example of fragment parsing w/o a contextElement bugzilla@jessica.w3.org
• [Bug 12031] Please provide example of fragment parsing w/o a contextElement bugzilla@jessica.w3.org
• [Bug 12031] New: Please provide example of fragment parsing w/o a contextElement bugzilla@jessica.w3.org
• [Bug 9593] Anchors in spec are not consistent bugzilla@jessica.w3.org
• [Bug 12029] Define a process for "particularly exceptional circumstances" bugzilla@jessica.w3.org
• [Bug 12030] "the user agent must follow the following steps" -- missing "run" or similar bugzilla@jessica.w3.org
• [Bug 12030] "the user agent must follow the following steps" -- missing "run" or similar bugzilla@jessica.w3.org
• [Bug 11984] Simplify <video> for implementors and authors by ignoring the Content-Type HTTP header bugzilla@jessica.w3.org
• [Bug 12030] "the user agent must follow the following steps" -- missing "run" or similar bugzilla@jessica.w3.org
• [Bug 12030] New: "the user agent must follow the following steps" -- missing "run" or similar bugzilla@jessica.w3.org
• [Bug 12029] Define a process for "particularly exceptional circumstances" bugzilla@jessica.w3.org
• [Bug 12029] Define a process for "particularly exceptional circumstances" bugzilla@jessica.w3.org
• [Bug 12029] Define a process for "particularly exceptional circumstances" bugzilla@jessica.w3.org
• [Bug 12029] Define a process for "particularly exceptional circumstances" bugzilla@jessica.w3.org
• [Bug 12029] Define a process for "particularly exceptional circumstances" bugzilla@jessica.w3.org
• [Bug 11191] Run scripts based on a parser flag rather than on being a fragment parser bugzilla@jessica.w3.org
• [Bug 12029] New: Define a process for "particularly exceptional circumstances" bugzilla@jessica.w3.org
• [Bug 11393] End tag fails to break out of foreign content bugzilla@jessica.w3.org
• [Bug 12028] New: The table of link types is apparently meant to be in alphabetic order, so "stylesheet" and "sidebar" should be swapped. bugzilla@jessica.w3.org
• [Bug 11393] End tag fails to break out of foreign content bugzilla@jessica.w3.org
• [Bug 11212] Make all the radio button group suffering from being missing (instead of only radio's with the required attribute) bugzilla@jessica.w3.org
• [Bug 11395] Use media queries to select appropriate <track> elements bugzilla@jessica.w3.org
• [Bug 12025] New: [bug?] how to handle this snippet? bugzilla@jessica.w3.org
• [Bug 12024] New: Should make it clear that when an <object> navigates to a resource given in its data="" attribute, the fetching is done by the <object>'s algorithm and _not_ the "navigate" algorithm. In particular, there's a note in the <object> section about appcaches m bugzilla@jessica.w3.org
• [Bug 11212] Make all the radio button group suffering from being missing (instead of only radio's with the required attribute) bugzilla@jessica.w3.org
• [Bug 11960] Consider making the global scope pollution by names/ids quirks-only bugzilla@jessica.w3.org

Wednesday, 9 February 2011

• [Bug 11393] End tag fails to break out of foreign content bugzilla@jessica.w3.org
• [Bug 11393] End tag fails to break out of foreign content bugzilla@jessica.w3.org
• [Bug 11191] Run scripts based on a parser flag rather than on being a fragment parser bugzilla@jessica.w3.org
• [Bug 11191] Run scripts based on a parser flag rather than on being a fragment parser bugzilla@jessica.w3.org
• [Bug 11393] End tag fails to break out of foreign content bugzilla@jessica.w3.org
• [Bug 12023] New: How shall invalid code points from U+D800 to U+DFFF be handled - a replacement character U+FFFD REPLACEMENT CHARACTER for each byte or the whole sequence (I assume the latter) bugzilla@jessica.w3.org
• [Bug 12021] Is <time>2011</time> acceptable? The formulation "precisedate" suggests that it is not, but an example says that "the year is not marked up at all, since marking it up would not be particularly useful", implying (IMHO) that it would be _possible_ to use < bugzilla@jessica.w3.org
• [Bug 12022] New: Shouldn't the iframe element be made into a void element? You're saying its descendents should 'represent nothing'. bugzilla@jessica.w3.org
• [Bug 12018] hello world !! bugzilla@jessica.w3.org
• [Bug 12018] hello world !! bugzilla@jessica.w3.org
• [Bug 12019] hello world !! bugzilla@jessica.w3.org
• [Bug 12021] New: Is <time>2011</time> acceptable? The formulation "precisedate" suggests that it is not, but an example says that "the year is not marked up at all, since marking it up would not be particularly useful", implying (IMHO) that it would be _possible_ to use < bugzilla@jessica.w3.org
• [Bug 12020] New: "One byte in the range F5 to FD, followed by three bytes in the range 80 to BF, not followed by a byte in the range 80 to BF" should be "One byte in the range F8 to FD, followed by three bytes in the range 80 to BF, not followed by a byte in the range 80 bugzilla@jessica.w3.org
• [Bug 12019] New: hello world !! bugzilla@jessica.w3.org
• [Bug 12018] New: hello world !! bugzilla@jessica.w3.org
• [Bug 12017] Keeping IMG aspect ratio bugzilla@jessica.w3.org
• [Bug 12017] New: Keeping IMG aspect ratio bugzilla@jessica.w3.org
• [Bug 11191] Run scripts based on a parser flag rather than on being a fragment parser bugzilla@jessica.w3.org
• [Bug 11599] Please allow external body (like external script and style) bugzilla@jessica.w3.org
• [Bug 11532] From section 6.1.5 The javascript: protocol, >When a URL using the javascript: protocol is dereferenced The "protocol" seems to be used about URI schemes with a trailing colon, but in other places schemes are referred to. All instances of "protocol" in th bugzilla@jessica.w3.org
• [Bug 11532] From section 6.1.5 The javascript: protocol, >When a URL using the javascript: protocol is dereferenced The "protocol" seems to be used about URI schemes with a trailing colon, but in other places schemes are referred to. All instances of "protocol" in th bugzilla@jessica.w3.org
• [Bug 11981] There's a race condition with autoplay if the autoplay attribute is removed in e.g. 'loadstart' event listener bugzilla@jessica.w3.org
• [Bug 11393] End tag fails to break out of foreign content bugzilla@jessica.w3.org
• [Bug 11194] Some <dd>s in the HTML tokenizer are <dd><p>s but most aren't. bugzilla@jessica.w3.org
• [Bug 11194] Some <dd>s in the HTML tokenizer are <dd><p>s but most aren't. bugzilla@jessica.w3.org
• [Bug 11091] Clarify whether importNode copies the 'already executed' flag bugzilla@jessica.w3.org
• [Bug 11091] Clarify whether importNode copies the 'already executed' flag bugzilla@jessica.w3.org
• [Bug 12015] "at the time the element's "already started" flag was set" should be "at the time the element's "already started" flag was FIRST set". bugzilla@jessica.w3.org
• [Bug 11298] Surrogate catching doesn't belong in input stream preprocessing bugzilla@jessica.w3.org
• [Bug 11298] Surrogate catching doesn't belong in input stream preprocessing bugzilla@jessica.w3.org
• [Bug 11426] Meta prescan should run on the first 1024 bytes bugzilla@jessica.w3.org
• [Bug 11426] Meta prescan should run on the first 1024 bytes bugzilla@jessica.w3.org

Tuesday, 8 February 2011

• [Bug 11301] "Run" and "execute" shouldn't mean different things, it's extremely confusing. Rename "run" to "attempt to execute" or something. bugzilla@jessica.w3.org
• [Bug 11721] Typo: "unforseen". The quick brown fox jumped over the lazy dog. bugzilla@jessica.w3.org
• [Bug 12011] The first example has "&lt" (two times) instead of "<" in end tags. bugzilla@jessica.w3.org
• [Bug 11105] Prevent execution of scripts in documents that don't have a browsing context after 'already started' has been set bugzilla@jessica.w3.org
• [Bug 11105] Prevent execution of scripts in documents that don't have a browsing context after 'already started' has been set bugzilla@jessica.w3.org
• [Bug 11301] "Run" and "execute" shouldn't mean different things, it's extremely confusing. Rename "run" to "attempt to execute" or something. bugzilla@jessica.w3.org
• [Bug 11323] Don't run scripts when the owner doc isn't the inserter parser's doc or when the owner doc is not the same at "run" and "execute" time bugzilla@jessica.w3.org
• [Bug 11301] "Run" and "execute" shouldn't mean different things, it's extremely confusing. Rename "run" to "attempt to execute" or something. bugzilla@jessica.w3.org
• [Bug 12015] "at the time the element's "already started" flag was set" should be "at the time the element's "already started" flag was FIRST set". bugzilla@jessica.w3.org
• [Bug 11090] Add a note about XSLT-created scripts bugzilla@jessica.w3.org
• [Bug 11323] Don't run scripts when the owner doc isn't the inserter parser's doc or when the owner doc is not the same at "run" and "execute" time bugzilla@jessica.w3.org
• [Bug 12015] "at the time the element's "already started" flag was set" should be "at the time the element's "already started" flag was FIRST set". bugzilla@jessica.w3.org
• [Bug 12015] New: "at the time the element's "already started" flag was set" should be "at the time the element's "already started" flag was FIRST set". bugzilla@jessica.w3.org
• [Bug 11657] My worry is that this doesn't cover all the different kinds of textual transformations. Yes, it does cover obliqueness and weight, it does not cover letter spacing and other textual attributes that may be of some use to developers. bugzilla@jessica.w3.org
• [Bug 11239] Canvas support accessible caret tracking independent of Focus Ring tracking bugzilla@jessica.w3.org
• [Bug 7601] refer to pronunciations for TTS PLS with link rel value "pronunciation" bugzilla@jessica.w3.org
• [Bug 10486] References to "image" ARIA role should be "img" bugzilla@jessica.w3.org
• [Bug 10152] [polyglot] i18n comment 5 : Mention lang and xml:lang bugzilla@jessica.w3.org
• [Bug 10249] Canvas requires a content selection method bugzilla@jessica.w3.org
• [Bug 10518] Add example showing how to use <a> elements in image maps bugzilla@jessica.w3.org
• [Bug 10618] Use "unmapped" rather than "no role" in the weak/strong ARIA tables bugzilla@jessica.w3.org
• [Bug 10723] support for media fragment URIs in relevant HTML5 elements bugzilla@jessica.w3.org
• [Bug 10788] @srcdoc in polyglot documents bugzilla@jessica.w3.org
• [Bug 10808] text with unknown direction gets corrupted when inserted in content with opposite direction bugzilla@jessica.w3.org
• [Bug 10823] i18n comment 19 : when an input value is remembered, its direction should be remembered too bugzilla@jessica.w3.org
• [Bug 10828] i18n comment 4 : at least by default, <br> should constitute a bidi paragraph break bugzilla@jessica.w3.org
• [Bug 10830] i18n comment : Please add support for rb bugzilla@jessica.w3.org
• [Bug 10904] <video> element needs to support some form of parental control solution bugzilla@jessica.w3.org
• [Bug 11239] Canvas support accessible caret tracking independent of Focus Ring tracking bugzilla@jessica.w3.org
• [Bug 12013] New: Markup of the VAT element example missing some semi-colons, mangling the left angle brackets bugzilla@jessica.w3.org
• [Bug 12011] New: The first example has "&lt" (two times) instead of "<" in end tags. bugzilla@jessica.w3.org
• [Bug 7601] refer to pronunciations for TTS PLS with link rel value "pronunciation" bugzilla@jessica.w3.org
• [Bug 9452] Handling of additional tracks of a multitrack audio/video resource bugzilla@jessica.w3.org
• [Bug 12002] User agents should provide controls to enable or disable the display of closed captions, audio description tracks, and other additional data associated with the video stream, though such features should, again, not interfere with the page's normal renderi bugzilla@jessica.w3.org
• [Bug 11956] restrict use of role=presentation bugzilla@jessica.w3.org
• [Bug 7601] refer to pronunciations for TTS PLS with link rel value "pronunciation" bugzilla@jessica.w3.org
• [Bug 11916] 2d.drawImage.incomplete partially invalid bugzilla@jessica.w3.org
• [Bug 11825] math-parse02.html invalid bugzilla@jessica.w3.org
• [Bug 11917] Wrong description of correct test 2d.imageData.create1.zero bugzilla@jessica.w3.org
• [Bug 11921] Fix references to test2.w3.org bugzilla@jessica.w3.org
• [Bug 11680] step 17: "value a value" typo? bugzilla@jessica.w3.org
• [Bug 11347] Submitting a partially downloaded form bugzilla@jessica.w3.org
• [Bug 11673] I need to send live data from device to URL on remote system. Would be nice to connect WebSocket, but simple access to buffer callback to package and send data to remote URL. Having access to data after closing recording interupts asynchronous processin bugzilla@jessica.w3.org
• [Bug 12004] Use http://w3c-test.org and not http://test2.w3.org bugzilla@jessica.w3.org
• [Bug 11921] Fix references to test2.w3.org bugzilla@jessica.w3.org
• [Bug 11441] "The img must not be used as a layout tool." Missing "element"? bugzilla@jessica.w3.org
• [Bug 12008] New: In the first example, "</" appears as "&lt;/". I.e., the entity has been escaped one time too many. bugzilla@jessica.w3.org
• [Bug 11690] "need a date" not xreffed bugzilla@jessica.w3.org
• [Bug 12006] This algorithm should also return the boundary used so XMLHttpRequest can set the Content-Type header appropriately. bugzilla@jessica.w3.org
• [Bug 12006] New: This algorithm should also return the boundary used so XMLHttpRequest can set the Content-Type header appropriately. bugzilla@jessica.w3.org
• [Bug 12005] New: It would be nice if "constructing the form data set" was an actual algorithm term and included the steps before about gathering the controls associated with the form. That way FormData(HTMLFormElement) is easier to define. And I like easy. bugzilla@jessica.w3.org
• [Bug 11711] What about sandboxed XHTML ? bugzilla@jessica.w3.org
• [Bug 11714] Not a bug, but a suggestion — add an example like this: “Price: €99 <small>(VAT included)</small>” bugzilla@jessica.w3.org
• [Bug 11715] Map HTML <article><a rel=author> to Atom <entry><author> bugzilla@jessica.w3.org
• [Bug 11722] make 404 page redirect faster or not say "File Not Found" until redirect script has failed bugzilla@jessica.w3.org
• [Bug 12004] Use http://w3c-test.org and not http://test2.w3.org bugzilla@jessica.w3.org
• [Bug 12004] New: Use http://w3c-test.org and not http://test2.w3.org bugzilla@jessica.w3.org
• [Bug 11721] Typo: "unforseen". The quick brown fox jumped over the lazy dog. bugzilla@jessica.w3.org
• [Bug 11721] Typo: "unforseen". The quick brown fox jumped over the lazy dog. bugzilla@jessica.w3.org
• [Bug 11533] clarify if specially focusable elements mean "all elements with defined valid tabindex" or "elements with a tabindex that allows sequential focusing." bugzilla@jessica.w3.org
• [Bug 11441] "The img must not be used as a layout tool." Missing "element"? bugzilla@jessica.w3.org
• [Bug 11441] "The img must not be used as a layout tool." Missing "element"? bugzilla@jessica.w3.org
• [Bug 11715] Map HTML <article><a rel=author> to Atom <entry><author> bugzilla@jessica.w3.org
• [Bug 11714] Not a bug, but a suggestion — add an example like this: “Price: €99 <small>(VAT included)</small>” bugzilla@jessica.w3.org
• [Bug 11714] Not a bug, but a suggestion — add an example like this: “Price: €99 <small>(VAT included)</small>” bugzilla@jessica.w3.org
• [Bug 11712] typo: "labeld" should be "labeled" bugzilla@jessica.w3.org
• [Bug 11712] typo: "labeld" should be "labeled" bugzilla@jessica.w3.org
• [Bug 11711] What about sandboxed XHTML ? bugzilla@jessica.w3.org
• [Bug 11708] step 17: to which precision should "the moment that this algorithm was invoked" be given? bugzilla@jessica.w3.org
• [Bug 11708] step 17: to which precision should "the moment that this algorithm was invoked" be given? bugzilla@jessica.w3.org
• [Bug 11705] Why does the definition of "middle" differ from the one in SVG 1.1 10.9.2? bugzilla@jessica.w3.org
• [Bug 11705] Why does the definition of "middle" differ from the one in SVG 1.1 10.9.2? bugzilla@jessica.w3.org
• [Bug 11707] [device] Developers only need video and audio streams. The type attribute should either be video or audio. bugzilla@jessica.w3.org
• [Bug 11802] [device] Suggestion for how to filter the list bugzilla@jessica.w3.org
• [Bug 11958] [device] Use "peripheral" as the base generic device class keyword bugzilla@jessica.w3.org
• [Bug 11935] [device] There is no mention of <device> in the parsing algorithm. Could you please add it to the list of self-closing tags. bugzilla@jessica.w3.org
• [Bug 11751] Adding support for audiovisual devices would definetively bee a flash-killer. You have my vote. bugzilla@jessica.w3.org
• [Bug 11704] step 5: <link rel=icon> bugzilla@jessica.w3.org
• [Bug 11704] step 5: <link rel=icon> bugzilla@jessica.w3.org
• [Bug 11670] "The setTransform(a, b, c, d, e, f) method must [...] invoke the transform(a, b, c, d, e, f) method" - so if I set CanvasRenderingContext2D.prototype.transform=function(){alert()}, then calling setTransform would trigger the alert? Probably this shouldn't bugzilla@jessica.w3.org
• [Bug 11694] "best representation" does not define how to normalize decimal part of second bugzilla@jessica.w3.org
• [Bug 11694] "best representation" does not define how to normalize decimal part of second bugzilla@jessica.w3.org
• [Bug 11692] step 11: "a rel attribute whose value includes the bookmark keyword" is not well defined bugzilla@jessica.w3.org
• [Bug 11692] step 11: "a rel attribute whose value includes the bookmark keyword" is not well defined bugzilla@jessica.w3.org
• [Bug 11690] "need a date" not xreffed bugzilla@jessica.w3.org
• [Bug 11689] step 8: be explicit about the order in which things are located and removed bugzilla@jessica.w3.org
• [Bug 11690] "need a date" not xreffed bugzilla@jessica.w3.org
• [Bug 11689] step 8: be explicit about the order in which things are located and removed bugzilla@jessica.w3.org
• [Bug 11678] <input type='email' multiple> should have the last comma stripped or being valid with a ending comma bugzilla@jessica.w3.org
• [Bug 11686] step 11: missing "of" in "the descendants the title element," bugzilla@jessica.w3.org
• [Bug 11686] step 11: missing "of" in "the descendants the title element," bugzilla@jessica.w3.org
• [Bug 11685] step 11+16.4: factor out the common steps bugzilla@jessica.w3.org
• [Bug 11685] step 11+16.4: factor out the common steps bugzilla@jessica.w3.org

Monday, 7 February 2011

• [Bug 11684] step 10: the body element isn't defined as sectioning content, so heading will always be null bugzilla@jessica.w3.org
• [Bug 11684] step 10: the body element isn't defined as sectioning content, so heading will always be null bugzilla@jessica.w3.org
• [Bug 11680] step 17: "value a value" typo? bugzilla@jessica.w3.org
• [Bug 11680] step 17: "value a value" typo? bugzilla@jessica.w3.org
• [Bug 11680] step 17: "value a value" typo? bugzilla@jessica.w3.org
• [Bug 11347] Submitting a partially downloaded form bugzilla@jessica.w3.org
• [Bug 11673] I need to send live data from device to URL on remote system. Would be nice to connect WebSocket, but simple access to buffer callback to package and send data to remote URL. Having access to data after closing recording interupts asynchronous processin bugzilla@jessica.w3.org
• [Bug 11597] mismatch between parsing rule and valid syntax for meta refresh URL bugzilla@jessica.w3.org
• [Bug 11597] mismatch between parsing rule and valid syntax for meta refresh URL bugzilla@jessica.w3.org
• [Bug 11663] "non-shortest form" is more established than "overlong form" bugzilla@jessica.w3.org
• [Bug 11673] I need to send live data from device to URL on remote system. Would be nice to connect WebSocket, but simple access to buffer callback to package and send data to remote URL. Having access to data after closing recording interupts asynchronous processin bugzilla@jessica.w3.org
• [Bug 11668] Make the following note into a security warning: "It is possible that the output of this algorithm, if parsed with an HTML parser, will not return the original tree structure." and add an example of an attack (ack Eduardo Vela Nava) bugzilla@jessica.w3.org
• [Bug 11668] Make the following note into a security warning: "It is possible that the output of this algorithm, if parsed with an HTML parser, will not return the original tree structure." and add an example of an attack (ack Eduardo Vela Nava) bugzilla@jessica.w3.org
• [Bug 11427] should allow use of xml:id for XHTML5 bugzilla@jessica.w3.org
• [Bug 11328] Canvas authors needs to be able to assess pixel resolution to rescale canvas elements bugzilla@jessica.w3.org
• [Bug 12003] "for either returns a Document"? "for" there is probably extra. bugzilla@jessica.w3.org
• [Bug 12003] New: "for either returns a Document"? "for" there is probably extra. bugzilla@jessica.w3.org
• [Bug 11988] "then set to true." +it bugzilla@jessica.w3.org
• [Bug 11999] poster frame algo doesn't handle absent poster attribute bugzilla@jessica.w3.org
• [Bug 11995] Parliament Square, London 09/12/2010 bugzilla@jessica.w3.org
• [Bug 11993] <!DOCTYPE html> <html lang="ja"> <head> <title>samplegragh01</title> <link href="sample_graph_vbar.css" type="text/css" rel="stylesheet" /> <script type="text/javascript" src="rendering-mode.js"></script> <!--[if IE]><script type="text/javascript" src=". bugzilla@jessica.w3.org
• [Bug 11992] <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> <html lang="ja"> <head> <title>samplegragh01</title> <link href="sample_graph_vbar.css" type="text/css" rel="stylesheet" /> <script t bugzilla@jessica.w3.org
• [Bug 12002] User agents should provide controls to enable or disable the display of closed captions, audio description tracks, and other additional data associated with the video stream, though such features should, again, not interfere with the page's normal renderi bugzilla@jessica.w3.org
• [Bug 12001] Please enter your feedback, carefully indicating the title of the section for which you are submitting feedback, quoting the text that's wrong today if appropriate. If you're suggesting a new feature, it's really important to say what the problem you're t bugzilla@jessica.w3.org
• [Bug 11997] dfg fsd terbe drtgre 5wfsdf hdg bugzilla@jessica.w3.org
• [Bug 12002] User agents should provide controls to enable or disable the display of closed captions, audio description tracks, and other additional data associated with the video stream, though such features should, again, not interfere with the page's normal renderi bugzilla@jessica.w3.org
• [Bug 12000] <!DOCTYPE html> <html lang="ja"> <head> <link rel="alternate" href="http://www.html5.jp/index.rdf" type="application/rss+xml" title="HTML5.JP RSS Feed" /> <link rel="stylesheet" href="/common/css/style.css" type="text/css" /> <link rel="stylesheet" href=" bugzilla@jessica.w3.org
• [Bug 12002] User agents should provide controls to enable or disable the display of closed captions, audio description tracks, and other additional data associated with the video stream, though such features should, again, not interfere with the page's normal renderi bugzilla@jessica.w3.org
• [Bug 12002] User agents should provide controls to enable or disable the display of closed captions, audio description tracks, and other additional data associated with the video stream, though such features should, again, not interfere with the page's normal renderi bugzilla@jessica.w3.org
• [Bug 12002] New: User agents should provide controls to enable or disable the display of closed captions, audio description tracks, and other additional data associated with the video stream, though such features should, again, not interfere with the page's normal renderi bugzilla@jessica.w3.org
• [Bug 12001] New: Please enter your feedback, carefully indicating the title of the section for which you are submitting feedback, quoting the text that's wrong today if appropriate. If you're suggesting a new feature, it's really important to say what the problem you're t bugzilla@jessica.w3.org
• [Bug 12000] New: <!DOCTYPE html> <html lang="ja"> <head> <link rel="alternate" href="http://www.html5.jp/index.rdf" type="application/rss+xml" title="HTML5.JP RSS Feed" /> <link rel="stylesheet" href="/common/css/style.css" type="text/css" /> <link rel="stylesheet" href=" bugzilla@jessica.w3.org
• [Bug 11999] New: poster frame algo doesn't handle absent poster attribute bugzilla@jessica.w3.org
• [Bug 11960] Consider making the global scope pollution by names/ids quirks-only bugzilla@jessica.w3.org
• [Bug 11997] New: dfg fsd terbe drtgre 5wfsdf hdg bugzilla@jessica.w3.org
• [Bug 11995] New: Parliament Square, London 09/12/2010 bugzilla@jessica.w3.org
• [Bug 11994] lulwut? i am 12 year old and what isthis? bugzilla@jessica.w3.org
• [Bug 11994] New: lulwut? i am 12 year old and what isthis? bugzilla@jessica.w3.org
• [Bug 11993] New: <!DOCTYPE html> <html lang="ja"> <head> <title>samplegragh01</title> <link href="sample_graph_vbar.css" type="text/css" rel="stylesheet" /> <script type="text/javascript" src="rendering-mode.js"></script> <!--[if IE]><script type="text/javascript" src=". bugzilla@jessica.w3.org
• [Bug 11992] New: <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> <html lang="ja"> <head> <title>samplegragh01</title> <link href="sample_graph_vbar.css" type="text/css" rel="stylesheet" /> <script t bugzilla@jessica.w3.org

Sunday, 6 February 2011

• [Bug 11991] Document should state that percentage heights and widths are not valid bugzilla@jessica.w3.org
• [Bug 11991] Document should state that percentage heights and widths are not valid bugzilla@jessica.w3.org
• [Bug 11970] onsubmit on element form: invalid return bugzilla@jessica.w3.org
• [Bug 11991] Document should state that percentage heights and widths are not valid bugzilla@jessica.w3.org
• [Bug 11991] Document should state that percentage heights and widths are not valid bugzilla@jessica.w3.org
• [Bug 11991] New: Document should state that percentage heights and widths are not valid bugzilla@jessica.w3.org
• [Bug 11984] Simplify <video> for implementors and authors by ignoring the Content-Type HTTP header bugzilla@jessica.w3.org

Saturday, 5 February 2011

• [Bug 11988] New: "then set to true." +it bugzilla@jessica.w3.org
• [Bug 7601] refer to pronunciations for TTS PLS with link rel value "pronunciation" bugzilla@jessica.w3.org
• [Bug 11984] Simplify <video> for implementors and authors by ignoring the Content-Type HTTP header bugzilla@jessica.w3.org
• [Bug 11984] Simplify <video> for implementors and authors by ignoring the Content-Type HTTP header bugzilla@jessica.w3.org
• [Bug 11984] Simplify <video> for implementors and authors by ignoring the Content-Type HTTP header bugzilla@jessica.w3.org
• [Bug 11984] Simplify <video> for implementors and authors by ignoring the Content-Type HTTP header bugzilla@jessica.w3.org
• [Bug 11984] Simplify <video> for implementors and authors by ignoring the Content-Type HTTP header bugzilla@jessica.w3.org
• [Bug 11984] Simplify <video> for implementors and authors by ignoring the Content-Type HTTP header bugzilla@jessica.w3.org
• [Bug 11984] New: Simplify <video> for implementors and authors by ignoring the Content-Type HTTP header bugzilla@jessica.w3.org

Friday, 4 February 2011

• [Bug 11983] I hate niggers. I hate niggers. I hate niggers. I hate niggers. I hate niggers. I hate niggers. I hate niggers. I hate niggers. I hate niggers. I hate niggers. I hate niggers. I hate niggers. bugzilla@jessica.w3.org
• [Bug 11983] New: I hate niggers. I hate niggers. I hate niggers. I hate niggers. I hate niggers. I hate niggers. I hate niggers. I hate niggers. I hate niggers. I hate niggers. I hate niggers. I hate niggers. bugzilla@jessica.w3.org
• [Bug 11982] hi.. my name is lucy... I wonder about this new version of HTML 5.0 as HTML, if you guys can like to receive an email with all of you and tutorial information on this new version. can this be possible? my email is: luc_lawless@yahoo.com I thank you, luc bugzilla@jessica.w3.org
• [Bug 11982] New: hi.. my name is lucy... I wonder about this new version of HTML 5.0 as HTML, if you guys can like to receive an email with all of you and tutorial information on this new version. can this be possible? my email is: luc_lawless@yahoo.com I thank you, luc bugzilla@jessica.w3.org
• [Bug 11579] Support for IDNs in e-mail addresses should be "should" or "must", not just "may" bugzilla@jessica.w3.org
• [Bug 11977] HTML5 spec. seems to unnecessarily ban strict mode event handlers bugzilla@jessica.w3.org
• [Bug 11981] There's a race condition with autoplay if the autoplay attribute is removed in e.g. 'loadstart' event listener bugzilla@jessica.w3.org
• [Bug 11981] New: There's a race condition with autoplay if the autoplay attribute is removed in e.g. 'loadstart' event listener bugzilla@jessica.w3.org
• [Bug 11973] HTML Spec confuses character sets with character encodings bugzilla@jessica.w3.org
• [Bug 11979] this is test bugzilla@jessica.w3.org
• [Bug 11579] Support for IDNs in e-mail addresses should be "should" or "must", not just "may" bugzilla@jessica.w3.org
• [Bug 11973] HTML Spec confuses character sets with character encodings bugzilla@jessica.w3.org
• [Bug 11392] 2.6.3. - typo - "will have" should read "has" bugzilla@jessica.w3.org
• [Bug 11979] New: this is test bugzilla@jessica.w3.org
• [Bug 11393] End tag fails to break out of foreign content bugzilla@jessica.w3.org
• [Bug 11912] HTML5 provides an opportunity to fix a long-running problem with HTTP Authentication. HTTP Authentication is important, because it is the only way to execute a request with 100% certainty that the user has provided an authentication secret. Furthermore, bugzilla@jessica.w3.org

Thursday, 3 February 2011

• [Bug 11977] HTML5 spec. seems to unnecessarily ban strict mode event handlers bugzilla@jessica.w3.org
• [Bug 11977] HTML5 spec. seems to unnecessarily ban strict mode event handlers bugzilla@jessica.w3.org
• [Bug 11977] New: HTML5 spec. seems to unnecessarily ban strict mode event handlers bugzilla@jessica.w3.org
• [Bug 11368] Missing Typographic Convention - Switch Construct bugzilla@jessica.w3.org
• [Bug 11935] There is no mention of <device> in the parsing algorithm. Could you please add it to the list of self-closing tags. bugzilla@jessica.w3.org
• [Bug 11342] TextMetrics should include distance from textBaseline to each of the baselines in the text bugzilla@jessica.w3.org
• [Bug 11935] There is no mention of <device> in the parsing algorithm. Could you please add it to the list of self-closing tags. bugzilla@jessica.w3.org
• [Bug 11320] IE and Gecko also invoke onerror for compile time syntax errors bugzilla@jessica.w3.org
• [Bug 11320] IE and Gecko also invoke onerror for compile time syntax errors bugzilla@jessica.w3.org
• [Bug 11320] IE and Gecko also invoke onerror for compile time syntax errors bugzilla@jessica.w3.org
• [Bug 11960] Consider making the global scope pollution by names/ids quirks-only bugzilla@jessica.w3.org
• [Bug 11262] Is there no U+0000 NULL handling in the Attribute value (single-quoted) state? bugzilla@jessica.w3.org
• [Bug 11262] Is there no U+0000 NULL handling in the Attribute value (single-quoted) state? bugzilla@jessica.w3.org
• [Bug 11646] step 13: copypasta in "the character at position is not a U+003A COLON character" bugzilla@jessica.w3.org
• [Bug 11262] Is there no U+0000 NULL handling in the Attribute value (single-quoted) state? bugzilla@jessica.w3.org
• [Bug 11262] Is there no U+0000 NULL handling in the Attribute value (single-quoted) state? bugzilla@jessica.w3.org
• [Bug 11646] step 13: copypasta in "the character at position is not a U+003A COLON character" bugzilla@jessica.w3.org
• [Bug 11973] HTML Spec confuses character sets with character encodings bugzilla@jessica.w3.org
• [Bug 11647] Use exactly 2 digits for hours in WebVTT timestamps bugzilla@jessica.w3.org
• [Bug 11643] step 19: value4 cannot be greater than 999 bugzilla@jessica.w3.org
• [Bug 11393] End tag fails to break out of foreign content bugzilla@jessica.w3.org
• [Bug 11643] step 19: value4 cannot be greater than 999 bugzilla@jessica.w3.org
• [Bug 11645] "may not be useful to everyone" misuses RFC2119 in a note bugzilla@jessica.w3.org
• [Bug 11644] There are three occurrences of 'codepoint' without the space. bugzilla@jessica.w3.org
• [Bug 11645] "may not be useful to everyone" misuses RFC2119 in a note bugzilla@jessica.w3.org
• [Bug 11393] End tag fails to break out of foreign content bugzilla@jessica.w3.org
• [Bug 11644] There are three occurrences of 'codepoint' without the space. bugzilla@jessica.w3.org
• [Bug 11642] copypasta with "the five character string" and odd escape strings bugzilla@jessica.w3.org
• [Bug 11633] rm "does" in step 7 "but does the first elevent characters do not exactly equal" bugzilla@jessica.w3.org
• [Bug 11642] copypasta with "the five character string" and odd escape strings bugzilla@jessica.w3.org
• [Bug 11633] rm "does" in step 7 "but does the first elevent characters do not exactly equal" bugzilla@jessica.w3.org
• [Bug 11973] HTML Spec confuses character sets with character encodings bugzilla@jessica.w3.org
• [Bug 11392] 2.6.3. - typo - "will have" should read "has" bugzilla@jessica.w3.org
• [Bug 11367] 1.10 - Typo - missing "a" bugzilla@jessica.w3.org
• [Bug 11379] [pending URL spec] definition of hierarchical URL inconsistent with rfc 3986 bugzilla@jessica.w3.org
• [Bug 11392] 2.6.3. - typo - "will have" should read "has" bugzilla@jessica.w3.org
• [Bug 11393] End tag fails to break out of foreign content bugzilla@jessica.w3.org
• [Bug 11279] the "assigned access key" section doesn't seem to know if it's a definition or a requirement. Should probably be rephrased to more correctly use RFC2119. bugzilla@jessica.w3.org
• [Bug 11279] the "assigned access key" section doesn't seem to know if it's a definition or a requirement. Should probably be rephrased to more correctly use RFC2119. bugzilla@jessica.w3.org
• [Bug 11973] HTML Spec confuses character sets with character encodings bugzilla@jessica.w3.org
• [Bug 11973] HTML Spec confuses character sets with character encodings bugzilla@jessica.w3.org
• [Bug 11973] HTML Spec confuses character sets with character encodings bugzilla@jessica.w3.org
• [Bug 11973] HTML Spec confuses character sets with character encodings bugzilla@jessica.w3.org
• [Bug 11973] HTML Spec confuses character sets with character encodings bugzilla@jessica.w3.org
• [Bug 11973] HTML Spec confuses character sets with character encodings bugzilla@jessica.w3.org
• [Bug 11973] New: HTML Spec confuses character sets with character encodings bugzilla@jessica.w3.org
• [Bug 11972] New: s/HTML elements elements/HTML elements/ bugzilla@jessica.w3.org
• [Bug 11971] New: /added, removed, or changed/set, changed, or removed/ bugzilla@jessica.w3.org
• [Bug 11960] Consider making the global scope pollution by names/ids quirks-only bugzilla@jessica.w3.org
• [Bug 11368] Missing Typographic Convention - Switch Construct bugzilla@jessica.w3.org
• [Bug 7798] I'm missing the height property in TextMetrics bugzilla@jessica.w3.org
• [Bug 11342] TextMetrics should include distance from textBaseline to each of the baselines in the text bugzilla@jessica.w3.org
• [Bug 8722] focus behaviour should be same for canvas regions as for elements bugzilla@jessica.w3.org
• [Bug 10249] Canvas requires a content selection method bugzilla@jessica.w3.org
• [Bug 11239] Canvas support accessible caret tracking independent of Focus Ring tracking bugzilla@jessica.w3.org
• [Bug 10938] Add <textual/> - a visible textual substitute element w/link capability bugzilla@jessica.w3.org
• [Bug 10713] Drag and Drop: Add guidance for keyboard-only interaction bugzilla@jessica.w3.org
• [Bug 10252] HTML5 hard-binds "Action" to accesskey key-press bugzilla@jessica.w3.org
• [Bug 10249] Canvas requires a content selection method bugzilla@jessica.w3.org
• [Bug 9817] Details element Focus problem bugzilla@jessica.w3.org
• [Bug 10720] Remove modifications to Extensibility section bugzilla@jessica.w3.org
• [Bug 11960] Consider making the global scope pollution by names/ids quirks-only bugzilla@jessica.w3.org
• [Bug 11960] Consider making the global scope pollution by names/ids quirks-only bugzilla@jessica.w3.org
• [Bug 11963] The namedItem(key) method must return the first node in the collection that matches the following requirements: •It is an a, applet, area, embed, form, frame, frameset, iframe, img, or object element with a name attribute equal to key, or, •It is an e bugzilla@jessica.w3.org
• [Bug 11295] Make script-inserted external scripts that have .async=false execute in the insertion order, default to true bugzilla@jessica.w3.org
• [Bug 11295] Make script-inserted external scripts that have .async=false execute in the insertion order, default to true bugzilla@jessica.w3.org
• [Bug 11295] Make script-inserted external scripts that have .async=false execute in the insertion order, default to true bugzilla@jessica.w3.org
• [Bug 11295] Make script-inserted external scripts that have .async=false execute in the insertion order, default to true bugzilla@jessica.w3.org
• [Bug 11342] The TextMetrics baseline must provide a baseline property bugzilla@jessica.w3.org
• [Bug 11969] Thank you for giving us precious resource. bugzilla@jessica.w3.org
• [Bug 11970] New: onsubmit on element form: invalid return bugzilla@jessica.w3.org
• [Bug 11342] The TextMetrics baseline must provide a baseline property bugzilla@jessica.w3.org
• [Bug 11969] New: Thank you for giving us precious resource. bugzilla@jessica.w3.org
• [Bug 11946] "The discarded bits mean that, for instance, atob("YQ") and atob("YR") both return "a"." was meant to be a note. Do you really want it to be normative text? bugzilla@jessica.w3.org
• [Bug 11959] Hi, user agents are "encouraged" to make it possible to view tooltips without the use of a pointing device (it means while browsing with the keyboard for instance). Why don't we make this an obligation instead of an encouragement ? If we don't make it a " bugzilla@jessica.w3.org
• [Bug 11242] Canvas must define what HTML elements may be used in the DOM Subtree bugzilla@jessica.w3.org
• [Bug 11342] The TextMetrics baseline must provide a baseline property bugzilla@jessica.w3.org
• [Bug 11239] Canvas support accessible caret tracking independent of Focus Ring tracking bugzilla@jessica.w3.org
• [Bug 7601] refer to pronunciations for TTS PLS with link rel value "pronunciation" bugzilla@jessica.w3.org
• [Bug 11960] Consider making the global scope pollution by names/ids quirks-only bugzilla@jessica.w3.org
• [Bug 11968] <!-- Load the Google AJAX API Loader --> <script type="text/javascript" src="http://www.google.com/jsapi"></script> <!-- Load the Google Friend Connect javascript library. --> <script type="text/javascript"> google.load('friendconnect', '0.8'); </script> bugzilla@jessica.w3.org
• [Bug 11968] New: <!-- Load the Google AJAX API Loader --> <script type="text/javascript" src="http://www.google.com/jsapi"></script> <!-- Load the Google Friend Connect javascript library. --> <script type="text/javascript"> google.load('friendconnect', '0.8'); </script> bugzilla@jessica.w3.org

Wednesday, 2 February 2011

• [Bug 7601] refer to pronunciations for TTS PLS with link rel value "pronunciation" bugzilla@jessica.w3.org
• [Bug 11960] Consider making the global scope pollution by names/ids quirks-only bugzilla@jessica.w3.org
• [Bug 11955] The canvas should be tainted when drawing text with a cross-origin font (unless CORS was used to allow it) bugzilla@jessica.w3.org
• [Bug 7601] refer to pronunciations for TTS PLS with link rel value "pronunciation" bugzilla@jessica.w3.org
• [Bug 7601] refer to pronunciations for TTS PLS with link rel value "pronunciation" bugzilla@jessica.w3.org
• [Bug 7475] Semantics of rel=first and rel=index breaks specs and implementations bugzilla@jessica.w3.org
• [Bug 7601] refer to pronunciations for TTS PLS with link rel value "pronunciation" bugzilla@jessica.w3.org
• [Bug 7601] refer to pronunciations for TTS PLS with link rel value "pronunciation" bugzilla@jessica.w3.org
• [Bug 7601] refer to pronunciations for TTS PLS with link rel value "pronunciation" bugzilla@jessica.w3.org
• [Bug 11912] HTML5 provides an opportunity to fix a long-running problem with HTTP Authentication. HTTP Authentication is important, because it is the only way to execute a request with 100% certainty that the user has provided an authentication secret. Furthermore, bugzilla@jessica.w3.org
• [Bug 11960] Consider making the global scope pollution by names/ids quirks-only bugzilla@jessica.w3.org
• [Bug 11963] The namedItem(key) method must return the first node in the collection that matches the following requirements: •It is an a, applet, area, embed, form, frame, frameset, iframe, img, or object element with a name attribute equal to key, or, •It is an e bugzilla@jessica.w3.org
• [Bug 11960] Consider making the global scope pollution by names/ids quirks-only bugzilla@jessica.w3.org
• [Bug 11963] The namedItem(key) method must return the first node in the collection that matches the following requirements: •It is an a, applet, area, embed, form, frame, frameset, iframe, img, or object element with a name attribute equal to key, or, •It is an e bugzilla@jessica.w3.org
• [Bug 11963] The namedItem(key) method must return the first node in the collection that matches the following requirements: •It is an a, applet, area, embed, form, frame, frameset, iframe, img, or object element with a name attribute equal to key, or, •It is an e bugzilla@jessica.w3.org
• [Bug 11963] New: The namedItem(key) method must return the first node in the collection that matches the following requirements: •It is an a, applet, area, embed, form, frame, frameset, iframe, img, or object element with a name attribute equal to key, or, •It is an e bugzilla@jessica.w3.org
• [Bug 11962] New: Add HTML tag support for generation of PDF documents or Post Scripts bugzilla@jessica.w3.org
• [Bug 11960] Consider making the global scope pollution by names/ids quirks-only bugzilla@jessica.w3.org
• [Bug 11912] HTML5 provides an opportunity to fix a long-running problem with HTTP Authentication. HTTP Authentication is important, because it is the only way to execute a request with 100% certainty that the user has provided an authentication secret. Furthermore, bugzilla@jessica.w3.org
• [Bug 11960] Consider making the global scope pollution by names/ids quirks-only bugzilla@jessica.w3.org
• [Bug 11960] Consider making the global scope pollution by names/ids quirks-only bugzilla@jessica.w3.org
• [Bug 11960] New: Consider making the global scope pollution by names/ids quirks-only bugzilla@jessica.w3.org
• [Bug 11959] New: Hi, user agents are "encouraged" to make it possible to view tooltips without the use of a pointing device (it means while browsing with the keyboard for instance). Why don't we make this an obligation instead of an encouragement ? If we don't make it a " bugzilla@jessica.w3.org
• [Bug 11958] Rather than use the USB/rs232 keywords, I would recommend going with the keyword "peripheral" for any device attached to the computer. This way it would not matter if the device in question is USB, 1394, or something platform exclusive. This will future p bugzilla@jessica.w3.org
• [Bug 11958] Rather than use the USB/rs232 keywords, I would recommend going with the keyword "peripheral" for any device attached to the computer. This way it would not matter if the device in question is USB, 1394, or something platform exclusive. This will future p bugzilla@jessica.w3.org
• [Bug 11958] New: Rather than use the USB/rs232 keywords, I would recommend going with the keyword "peripheral" for any device attached to the computer. This way it would not matter if the device in question is USB, 1394, or something platform exclusive. This will future p bugzilla@jessica.w3.org
• [Bug 11956] restrict use of role=presentation bugzilla@jessica.w3.org
• [Bug 11956] New: restrict use of role=presentation bugzilla@jessica.w3.org
• [Bug 11955] The canvas should be tainted when drawing text with a cross-origin font (unless CORS was used to allow it) bugzilla@jessica.w3.org
• [Bug 11955] New: The canvas should be tainted when drawing text with a cross-origin font (unless CORS was used to allow it) bugzilla@jessica.w3.org
• [Bug 11129] Remove forminput, formchange and related dispatch methods bugzilla@jessica.w3.org
• [Bug 11953] New: I think you should cut the word "anyway" twice in step 1.Otherwise.1 and 1.Otherwise.2 bugzilla@jessica.w3.org
• [Bug 11952] New: "the drop target has to listen to at least three events" That isn't true anymore with the dropzone attribute, right? (I know this section is non-normative...) bugzilla@jessica.w3.org
• [Bug 11951] New: One part of this section says "Binary data with a file name" and another part says "optionally with a file name". So is it optional or not? bugzilla@jessica.w3.org
• [Bug 11912] HTML5 provides an opportunity to fix a long-running problem with HTTP Authentication. HTTP Authentication is important, because it is the only way to execute a request with 100% certainty that the user has provided an authentication secret. Furthermore, bugzilla@jessica.w3.org

Tuesday, 1 February 2011

• [Bug 11912] HTML5 provides an opportunity to fix a long-running problem with HTTP Authentication. HTTP Authentication is important, because it is the only way to execute a request with 100% certainty that the user has provided an authentication secret. Furthermore, bugzilla@jessica.w3.org
• [Bug 11883] <?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"> <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en"> <head> <title> :: Rupert Shr bugzilla@jessica.w3.org
• [Bug 11893] define lexical processing rules for ARIA attributes bugzilla@jessica.w3.org
• [Bug 11892] explicitly state that ARIA states and properties are formal/normative HTML attributes bugzilla@jessica.w3.org
• [Bug 11342] The TextMetrics baseline must provide a baseline property bugzilla@jessica.w3.org
• [Bug 8885] Fallback mechanism for embedded content bugzilla@jessica.w3.org
• [Bug 10938] Add <textual/> - a visible textual substitute element w/link capability bugzilla@jessica.w3.org
• [Bug 10843] Support user control over the visual presentation of caption text. bugzilla@jessica.w3.org
• [Bug 10842] Support the isolation of speech from other background sounds in AV media bugzilla@jessica.w3.org
• [Bug 10841] We require a method to allow the user to control playback timing in order to have more time to understand the material. bugzilla@jessica.w3.org
• [Bug 10709] @title should be a required attribute for FRAME and IFRAME in HTML5 bugzilla@jessica.w3.org
• [Bug 8885] Fallback mechanism for embedded content bugzilla@jessica.w3.org
• [Bug 10693] Need a means for navigating between related timed tracks of media elements bugzilla@jessica.w3.org
• [Bug 8885] Fallback mechanism for embedded content bugzilla@jessica.w3.org
• [Bug 11944] In the element "table" sub-element "thead" the example is incorrect. The "thead" and "tbody" elements are opened but no cloing tag is found. bugzilla@jessica.w3.org
• [Bug 11941] One of the most important features that html5 is missing in lack of 'required' attribute in select tag. While all other tags are just fine for data driven web apps, lacking of this feature in select tag really puts us to write 'extra' code for required op bugzilla@jessica.w3.org
• [Bug 11946] "The discarded bits mean that, for instance, atob("YQ") and atob("YR") both return "a"." was meant to be a note. Do you really want it to be normative text? bugzilla@jessica.w3.org
• [Bug 11946] "The discarded bits mean that, for instance, atob("YQ") and atob("YR") both return "a"." was meant to be a note. Do you really want it to be normative text? bugzilla@jessica.w3.org
• [Bug 11945] The table displays weirdly in WebKit -- some entries ("Z" and "m") spill over between columns, and "y" isn't aligned to the bottom. In Gecko and Opera, it doesn't display in columns at all. How about sticking with <dl> and CSS columns like in my version bugzilla@jessica.w3.org
• [Bug 11946] New: "The discarded bits mean that, for instance, atob("YQ") and atob("YR") both return "a"." was meant to be a note. Do you really want it to be normative text? bugzilla@jessica.w3.org
• [Bug 11945] New: The table displays weirdly in WebKit -- some entries ("Z" and "m") spill over between columns, and "y" isn't aligned to the bottom. In Gecko and Opera, it doesn't display in columns at all. How about sticking with <dl> and CSS columns like in my version bugzilla@jessica.w3.org
• [Bug 11944] New: In the element "table" sub-element "thead" the example is incorrect. The "thead" and "tbody" elements are opened but no cloing tag is found. bugzilla@jessica.w3.org
• [Bug 11943] Typo: "exeption" (wasn't in the original text :) ) bugzilla@jessica.w3.org
• [Bug 11943] New: Typo: "exeption" (wasn't in the original text :) ) bugzilla@jessica.w3.org
• [Bug 11941] One of the most important features that html5 is missing in lack of 'required' attribute in select tag. While all other tags are just fine for data driven web apps, lacking of this feature in select tag really puts us to write 'extra' code for required op bugzilla@jessica.w3.org
• [Bug 11941] One of the most important features that html5 is missing in lack of 'required' attribute in select tag. While all other tags are just fine for data driven web apps, lacking of this feature in select tag really puts us to write 'extra' code for required op bugzilla@jessica.w3.org
• [Bug 11941] One of the most important features that html5 is missing in lack of 'required' attribute in select tag. While all other tags are just fine for data driven web apps, lacking of this feature in select tag really puts us to write 'extra' code for required op bugzilla@jessica.w3.org
• [Bug 11942] New: new feature suggestion: add inputmode attribute to <input> and <textarea> This already exists in XHTML Basic: http://www.w3.org/TR/2010/REC-xhtml-basic-20101123/#s_inputmode Rationale is explained in XHTML basic... Nir Dagan nir@nirdagan.com bugzilla@jessica.w3.org
• [Bug 11941] One of the most important features that html5 is missing in lack of 'required' attribute in select tag. While all other tags are just fine for data driven web apps, lacking of this feature in select tag really puts us to write 'extra' code for required op bugzilla@jessica.w3.org
• [Bug 11941] New: One of the most important features that html5 is missing in lack of 'required' attribute in select tag. While all other tags are just fine for data driven web apps, lacking of this feature in select tag really puts us to write 'extra' code for required op bugzilla@jessica.w3.org
• [Bug 11936] Progress element max and value IDL attributes should be float, not double bugzilla@jessica.w3.org
• [Bug 11937] Progress element should be indeterminate if the value attribute isn't a valid float bugzilla@jessica.w3.org
• [Bug 11939] Progress element max IDL attribute sholud reflect the maximum value instead of the content attribute bugzilla@jessica.w3.org
• [Bug 11938] Progress element value IDL attribute default value should be 0 instead of -1 bugzilla@jessica.w3.org
• [Bug 11938] Progress element value IDL attribute default value should be 0 instead of -1 bugzilla@jessica.w3.org
• [Bug 11935] There is no mention of <device> in the parsing algorithm. Could you please add it to the list of self-closing tags. bugzilla@jessica.w3.org
• [Bug 11940] New: Please specify reality and deal with raster images and SVG in embed being handled by the UA rather than a plugin or ignored bugzilla@jessica.w3.org
• [Bug 11935] There is no mention of <device> in the parsing algorithm. Could you please add it to the list of self-closing tags. bugzilla@jessica.w3.org
• [Bug 11939] New: Progress element max IDL attribute sholud reflect the maximum value instead of the content attribute bugzilla@jessica.w3.org
• [Bug 11938] New: Progress element value IDL attribute default value should be -1 instead of 0 bugzilla@jessica.w3.org
• [Bug 11816] Link broken: www.whatwg.org/specs/web-apps/current-work/html5-letter.pdf bugzilla@jessica.w3.org
• [Bug 11937] New: Progress element should be indeterminate if the value attribute isn't a valid float bugzilla@jessica.w3.org
• [Bug 11936] New: Progress element max and value IDL attributes should be float, not double bugzilla@jessica.w3.org
• [Bug 11934] biarkan aku menjaga perasaan ini bugzilla@jessica.w3.org
• [Bug 11932] testing this ok? bugzilla@jessica.w3.org
• [Bug 11932] testing this ok? bugzilla@jessica.w3.org
• [Bug 11933] testing this ok? bugzilla@jessica.w3.org
• [Bug 11935] There is no mention of <device> in the parsing algorithm. Could you please add it to the list of self-closing tags. bugzilla@jessica.w3.org
• [Bug 11935] New: There is no mention of <device> in the parsing algorithm. Could you please add it to the list of self-closing tags. bugzilla@jessica.w3.org
• [Bug 11934] New: biarkan aku menjaga perasaan ini bugzilla@jessica.w3.org
• [Bug 11933] New: testing this ok? bugzilla@jessica.w3.org
• [Bug 11932] New: testing this ok? bugzilla@jessica.w3.org
• [Bug 11909] The principles of Polyglot Markup - validity? well-formed? DOM-equality? bugzilla@jessica.w3.org
• [Bug 11909] The principles of Polyglot Markup - validity? well-formed? DOM-equality? bugzilla@jessica.w3.org
• [Bug 11912] HTML5 provides an opportunity to fix a long-running problem with HTTP Authentication. HTTP Authentication is important, because it is the only way to execute a request with 100% certainty that the user has provided an authentication secret. Furthermore, bugzilla@jessica.w3.org
• [Bug 11688] Please add a note about loading appcache master entries that are listed in NETWORK section bugzilla@jessica.w3.org
• [Bug 11688] Please add a note about loading appcache master entries that are listed in NETWORK section bugzilla@jessica.w3.org
• [Bug 11912] HTML5 provides an opportunity to fix a long-running problem with HTTP Authentication. HTTP Authentication is important, because it is the only way to execute a request with 100% certainty that the user has provided an authentication secret. Furthermore, bugzilla@jessica.w3.org
• [Bug 11687] Make the non-normative parts of the definition of "application cache" into notes, to not mislead people into thinking they're normative. Only the list of what's in an appcache is normative here. bugzilla@jessica.w3.org
• [Bug 11687] Make the non-normative parts of the definition of "application cache" into notes, to not mislead people into thinking they're normative. Only the list of what's in an appcache is normative here. bugzilla@jessica.w3.org

Last message date: Monday, 28 February 2011 23:56:44 UTC