Saturday, 28 February 2009
- Re: @rel syntax in RDFa (relevant to ISSUE-60 discussion), was: Using XMLNS in link/@rel
- Re: @rel syntax in RDFa (relevant to ISSUE-60 discussion), was: Using XMLNS in link/@rel
- Re: @rel syntax in RDFa (relevant to ISSUE-60 discussion), was: Using XMLNS in link/@rel
- Re: @rel syntax in RDFa (relevant to ISSUE-60 discussion), was: Using XMLNS in link/@rel
- Re: Draft text for summary attribute definition
- Re: @rel syntax in RDFa (relevant to ISSUE-60 discussion), was: Using XMLNS in link/@rel
- Re: Draft text for summary attribute definition
- Re: @rel syntax in RDFa (relevant to ISSUE-60 discussion), was: Using XMLNS in link/@rel
- Re: @rel syntax in RDFa (relevant to ISSUE-60 discussion), was: Using XMLNS in link/@rel
- Re: @rel syntax in RDFa (relevant to ISSUE-60 discussion), was: Using XMLNS in link/@rel
- Re: @rel syntax in RDFa (relevant to ISSUE-60 discussion), was: Using XMLNS in link/@rel
- Re: @rel syntax in RDFa (relevant to ISSUE-60 discussion), was: Using XMLNS in link/@rel
- Re: Draft text for summary attribute definition
- Re: @rel syntax in RDFa (relevant to ISSUE-60 discussion), was: Using XMLNS in link/@rel
- Re: @rel syntax in RDFa (relevant to ISSUE-60 discussion), was: Using XMLNS in link/@rel
- Re: @rel syntax in RDFa (relevant to ISSUE-60 discussion), was: Using XMLNS in link/@rel
- Re: Draft text for summary attribute definition
- Re: @rel syntax in RDFa (relevant to ISSUE-60 discussion), was: Using XMLNS in link/@rel
- Re: @rel syntax in RDFa (relevant to ISSUE-60 discussion), was: Using XMLNS in link/@rel
- Re: @rel syntax in RDFa (relevant to ISSUE-60 discussion), was: Using XMLNS in link/@rel
- Re: @rel syntax in RDFa (relevant to ISSUE-60 discussion), was: Using XMLNS in link/@rel
- Re: summary="" in HTML5 ISSUE-32
- Re: @rel syntax in RDFa (relevant to ISSUE-60 discussion), was: Using XMLNS in link/@rel
- Re: @rel syntax in RDFa (relevant to ISSUE-60 discussion), was: Using XMLNS in link/@rel
- Re: @rel syntax in RDFa (relevant to ISSUE-60 discussion), was: Using XMLNS in link/@rel
- Re: summary="" in HTML5 ISSUE-32
- [Bug 6637] New: Put boolean and enumerated attributes next to each other
- Re: @rel syntax in RDFa (relevant to ISSUE-60 discussion), was: Using XMLNS in link/@rel
Friday, 27 February 2009
- Re: @rel syntax in RDFa (relevant to ISSUE-60 discussion), was: Using XMLNS in link/@rel
- Re: @rel syntax in RDFa (relevant to ISSUE-60 discussion), was: Using XMLNS in link/@rel
- Re: @rel syntax in RDFa (relevant to ISSUE-60 discussion), was: Using XMLNS in link/@rel
- Re: @rel syntax in RDFa (relevant to ISSUE-60 discussion), was: Using XMLNS in link/@rel
- Re: @rel syntax in RDFa (relevant to ISSUE-60 discussion), was: Using XMLNS in link/@rel
- Re: @rel syntax in RDFa (relevant to ISSUE-60 discussion), was: Using XMLNS in link/@rel
- Re: @rel syntax in RDFa (relevant to ISSUE-60 discussion), was: Using XMLNS in link/@rel
- Re: @rel syntax in RDFa (relevant to ISSUE-60 discussion), was: Using XMLNS in link/@rel
- Re: @rel syntax in RDFa (relevant to ISSUE-60 discussion), was: Using XMLNS in link/@rel
- Re: @rel syntax in RDFa (relevant to ISSUE-60 discussion), was: Using XMLNS in link/@rel
- Re: @rel syntax in RDFa (relevant to ISSUE-60 discussion), was: Using XMLNS in link/@rel
- Re: @rel syntax in RDFa (relevant to ISSUE-60 discussion), was: Using XMLNS in link/@rel
- Re: @rel syntax in RDFa (relevant to ISSUE-60 discussion), was: Using XMLNS in link/@rel
- Re: @rel syntax in RDFa (relevant to ISSUE-60 discussion), was: Using XMLNS in link/@rel
- Assessing interest in meeting during the November W3C Tech Plenary/AC Meetings Week (poll coming)
- Re: summary="" in HTML5 ISSUE-32
- Re: @rel syntax in RDFa (relevant to ISSUE-60 discussion), was: Using XMLNS in link/@rel
- Re: @rel syntax in RDFa (relevant to ISSUE-60 discussion), was: Using XMLNS in link/@rel
- Require quotes around attributes for more characters
- [Bug 6630] New: Optionalness of start tags when element is empty
- Re: @rel syntax in RDFa (relevant to ISSUE-60 discussion), was: Using XMLNS in link/@rel
- Re: @rel syntax in RDFa (relevant to ISSUE-60 discussion), was: Using XMLNS in link/@rel
- Re: @rel syntax in RDFa (relevant to ISSUE-60 discussion), was: Using XMLNS in link/@rel
- Re: @rel syntax in RDFa (relevant to ISSUE-60 discussion), was: Using XMLNS in link/@rel
- Re: @rel syntax in RDFa (relevant to ISSUE-60 discussion), was: Using XMLNS in link/@rel
- Re: @rel syntax in RDFa (relevant to ISSUE-60 discussion), was: Using XMLNS in link/@rel
- Re: @rel syntax in RDFa (relevant to ISSUE-60 discussion), was: Using XMLNS in link/@rel
- Re: @rel syntax in RDFa (relevant to ISSUE-60 discussion), was: Using XMLNS in link/@rel
- Re: @rel syntax in RDFa (relevant to ISSUE-60 discussion), was: Using XMLNS in link/@rel
- Re: summary="" in HTML5 ISSUE-32
- Re: summary="" in HTML5 ISSUE-32
- Draft text for summary attribute definition
- Re: summary="" in HTML5 ISSUE-32
- Re: summary="" in HTML5 ISSUE-32
- Re: summary="" in HTML5 ISSUE-32
- Re: summary="" in HTML5 ISSUE-32
- @rel syntax in RDFa (relevant to ISSUE-60 discussion), was: Using XMLNS in link/@rel
- Re: summary="" in HTML5 ISSUE-32
- Re: summary="" in HTML5 ISSUE-32
- Re: summary="" and Universal Design in HTML5
- Re: summary="" in HTML5 ISSUE-32
- Re: summary="" in HTML5 ISSUE-32
- H:TML Status section updated [was: Moving forward on deciding]
- Re: summary="" in HTML5 ISSUE-32
- Re: summary="" in HTML5 ISSUE-32
- [Bug 6628] New: WebSocket.URL and EventSource.URL should return the absolute URL
- Re: summary="" in HTML5 ISSUE-32
- Re: summary="" in HTML5 ISSUE-32
- Re: summary="" in HTML5 ISSUE-32
- Re: summary="" in HTML5 ISSUE-32
- Re: summary="" in HTML5 ISSUE-32
- Re: summary="" in HTML5 ISSUE-32
- Re: summary="" in HTML5 ISSUE-32
- Re: summary="" in HTML5 ISSUE-32
- Re: summary="" in HTML5 ISSUE-32
- RE: disinterested chairing [was Re: summary="" in HTML5]
- Re: summary="" in HTML5 ISSUE-32
- Re: summary="" in HTML5 ISSUE-32
- Re: disinterested chairing [was Re: summary="" in HTML5]
Thursday, 26 February 2009
- Re: summary="" in HTML5 ISSUE-32
- Re: summary="" in HTML5 ISSUE-32
- Re: summary="" in HTML5 ISSUE-32
- Re: summary="" in HTML5 ISSUE-32
- Re: summary="" in HTML5 ISSUE-32
- Re: summary="" in HTML5 ISSUE-32
- Re: summary="" in HTML5 ISSUE-32
- Re: summary="" in HTML5 ISSUE-32
- Re: summary="" in HTML5 ISSUE-32
- Re: summary="" in HTML5 ISSUE-32
- Re: summary="" in HTML5 ISSUE-32
- Re: summary="" in HTML5 ISSUE-32
- Re: summary="" in HTML5 ISSUE-32
- Re: summary="" in HTML5 ISSUE-32
- Re: summary="" in HTML5 ISSUE-32
- Re: summary="" in HTML5 ISSUE-32
- Re: summary="" in HTML5 ISSUE-32
- Re: summary="" in HTML5 ISSUE-32
- Re: summary="" in HTML5 ISSUE-32
- Re: summary="" in HTML5 ISSUE-32
- Re: summary="" in HTML5 ISSUE-32
- Re: summary="" in HTML5 ISSUE-32
- Re: summary="" in HTML5 ISSUE-32
- Re: summary="" in HTML5 ISSUE-32
- minutes: HTML WG Weekly 26 Feb 2009
- Re: disinterested chairing [was Re: summary="" in HTML5]
- disinterested chairing [was Re: summary="" in HTML5]
- Re: {agenda} HTML WG telcon 2009-02-26
- Re: {agenda} HTML WG telcon 2009-02-26
- Re: summary="" in HTML5 ISSUE-32
- Re: summary="" in HTML5 ISSUE-32
- Re: summary="" in HTML5 ISSUE-32
- Re: summary="" in HTML5 ISSUE-32
- Re: summary="" in HTML5 ISSUE-32
- Re: summary="" in HTML5 ISSUE-32
- Re: summary="" in HTML5 ISSUE-32
- Re: summary="" in HTML5 ISSUE-32
- Re: summary="" in HTML5 ISSUE-32
- Re: summary="" in HTML5 ISSUE-32
- Re: summary="" in HTML5 ISSUE-32
- Re: summary="" in HTML5 ISSUE-32
- Re: summary="" in HTML5 ISSUE-32
- Re: summary="" in HTML5 ISSUE-32
- Re: summary="" in HTML5 ISSUE-32
- Re: summary="" in HTML5 ISSUE-32
- Re: summary="" in HTML5 ISSUE-32
- Re: summary="" in HTML5 ISSUE-32
- Re: summary="" in HTML5 ISSUE-32
- Re: summary="" in HTML5 ISSUE-32
- Re: summary="" in HTML5 ISSUE-32
- Re: summary="" in HTML5 ISSUE-32
- Re: Dimension attributes and video
- Re: bufferingThrottled and bufferingRate
- Re: summary="" in HTML5 ISSUE-32
- Re: Dimension attributes and video
- Re: Dimension attributes and video
- Re: Dimension attributes and video
- Re: Dimension attributes and video
Wednesday, 25 February 2009
- Re: Dimension attributes and video
- Re: summary="" in HTML5 ISSUE-32
- Re: "Where's the Beef?" department (was RE: Example canvas element use - accessibility concerns)
- Re: summary="" in HTML5 ISSUE-32
- Re: "Where's the Beef?" department (was RE: Example canvas element use - accessibility concerns)
- Re: summary="" in HTML5 ISSUE-32
- Re: summary="" in HTML5 ISSUE-32
- Re: summary="" in HTML5 ISSUE-32
- Re: summary="" in HTML5 ISSUE-32
- RE: summary="" in HTML5 ISSUE-32
- Re: summary="" in HTML5 ISSUE-32
- Re: summary="" in HTML5 ISSUE-32
- Re: summary="" in HTML5 ISSUE-32
- Re: summary="" in HTML5 ISSUE-32
- Re: summary="" in HTML5 ISSUE-32
- Re: summary="" in HTML5 ISSUE-32
- Re: summary="" in HTML5 ISSUE-32
- Re: HTML 5 Spec, broken link (anchor)
- Re: summary="" in HTML5 ISSUE-32
- Re: summary="" in HTML5 ISSUE-32
- Re: summary="" in HTML5 ISSUE-32
- HTML 5 Spec, broken link (anchor)
- Re: summary="" in HTML5 ISSUE-32
- Dimension attributes and video
- Re: summary="" in HTML5 ISSUE-32
- Re: summary="" in HTML5 ISSUE-32
- Re: summary="" in HTML5 ISSUE-32
- Re: summary="" in HTML5 ISSUE-32
- Re: summary="" in HTML5 ISSUE-32
- Re: summary="" in HTML5 ISSUE-32
- Re: summary="" in HTML5 ISSUE-32
- Re: summary="" in HTML5 ISSUE-32
- Re: summary="" in HTML5 ISSUE-32
- Re: summary="" in HTML5 ISSUE-32
- Re: Foster-parenting and taint
- Re: Foster-parenting and taint
- Re: summary="" in HTML5 ISSUE-32
- Foster-parenting and taint
- Re: summary="" in HTML5 ISSUE-32
- Re: another example canvas use- cufon - another accessibility concern and spec contradiction
- Re: Example canvas element use - accessibility concerns
- Re: Example canvas element use - accessibility concerns
- RE: Example canvas element use - accessibility concerns
- Re: Example canvas element use - accessibility concerns
- Re: "Where's the Beef?" department (was RE: Example canvas element use - accessibility concerns)
- RE: "Where's the Beef?" department (was RE: Example canvas element use - accessibility concerns)
- Re: summary="" in HTML5
- Re: Example canvas element use - accessibility concerns
- {agenda} HTML WG telcon 2009-02-26
- Re: "Where's the Beef?" department (was RE: Example canvas element use - accessibility concerns)
- "Where's the Beef?" department (was RE: Example canvas element use - accessibility concerns)
Tuesday, 24 February 2009
- Re: summary="" in HTML5
- Re: summary="" in HTML5 (2 of 2)
- RE: summary="" in HTML5
- another example canvas use- cufon - another accessibility concern and spec contradiction
- RE: summary="" in HTML5 (2 of 2)
- Re: ISSUE-4: Versioning, namespace URIs and MIME types
- [Bug 6618] New: </body> and </html> early on handled in a Gecko/WebKit/Presto-inconsisten way
- Re: summary="" in HTML5
- Re: R2866 : better talk about "CSS display" instead of "CSS tables"
- Re: summary="" in HTML5
- Re: summary="" in HTML5
- Re: summary="" in HTML5
- Re: R2866 : better talk about "CSS display" instead of "CSS tables"
- R2866 : better talk about "CSS display" instead of "CSS tables"
- Re: frameset-ok as flag vs. insertion mode
- Re: Example canvas element use - accessibility concerns
- Re: summary="" in HTML5
- RE: Example canvas element use - accessibility concerns
- Re: summary="" in HTML5
- Re: Use and abuse of @summary
- summary="" in HTML5
- Re: Example canvas element use - accessibility concerns
- RE: Example canvas element use - accessibility concerns
- Re: Drop foster-parented stuff on the floor if parent gone
Monday, 23 February 2009
- Re: Use and abuse of @summary
- Re: frameset-ok as flag vs. insertion mode
- Re: Drop foster-parented stuff on the floor if parent gone
- Re: ISSUE-54 doctype-legacy-compat, was: Input on the agenda
- Re: Example canvas element use - accessibility concerns
- Re: Input on the agenda
- Re: Example canvas element use - accessibility concerns
- Re: Example canvas element use - accessibility concerns
- RE: Example canvas element use - accessibility concerns
- RE: FW: [Re: TR/web-forms-2 -> TR/html5]
- Re: [Re: TR/web-forms-2 -> TR/html5]
- Re: Use and abuse of @summary
- frameset-ok as flag vs. insertion mode
- Re: Use and abuse of @summary
- Re: Use and abuse of @summary
- Re: Drop foster-parented stuff on the floor if parent gone
- Re: FW: [Re: TR/web-forms-2 -> TR/html5]
- Re: Drop foster-parented stuff on the floor if parent gone
- Re: Use and abuse of @summary
- [Bug 6614] New: Restricting multiple character encoding declarations per document
- ISSUE-54, was: Input on the agenda
- Re: Use and abuse of @summary
- Re: Use and abuse of @summary
- Input on the agenda
- Re: Example canvas element use - accessibility concerns
- Re: Use and abuse of @summary
- Re: Use and abuse of @summary
- Re: Use and abuse of @summary
- Re: Use and abuse of @summary
- [Bug 6613] New: Allow <meta charset="UTF-8"/> in XHTML
- FW: [Re: TR/web-forms-2 -> TR/html5]
- Re: play() sometimes doesn't do anything now that load() is async
- Re: Example canvas element use - accessibility concerns
- On subsetting the spec [was: Re: ACTION-95, ISSUE-65: Plan to publish a new WD of HTML-5]
Sunday, 22 February 2009
- Re: TR/web-forms-2 -> TR/html5
- Re: Lose Focus When Hidden? (SVG ISSUE-2031)
- [Bug 6610] New: add a preventable forced-fragment method
- [Bug 6609] New: negative keywords-not meta tags
- [Bug 6608] New: please undeprecate <center> for older browsers
- [Bug 6607] New: wrapping text to limit line length without a table
- [Bug 6606] New: generic 3rd-party <mark>, Smart Tags, and Activities prevention
- Re: Lose Focus When Hidden? (SVG ISSUE-2031)
- Re: Lose Focus When Hidden? (SVG ISSUE-2031)
Saturday, 21 February 2009
- RE: Example canvas element use - accessibility concerns
- RE: Example canvas element use - accessibility concerns
- fieldset: a CSS block formatting context?
- Re: Example canvas element use - accessibility concerns
- Re: Example canvas element use - accessibility concerns
- Re: Example canvas element use - accessibility concerns
- Re: Media element events
- RE: Example canvas element use - accessibility concerns
- RE: Example canvas element use - accessibility concerns
- Re: Caption@title instead of table@summary?
- RE: Example canvas element use - accessibility concerns
- RE: Example canvas element use - accessibility concerns
- RE: Example canvas element use - accessibility concerns
- Re: Example canvas element use - accessibility concerns
- RE: Example canvas element use - accessibility concerns
- Re: Example canvas element use - accessibility concerns
Friday, 20 February 2009
- Re: Example canvas element use - accessibility concerns
- Re: Example canvas element use - accessibility concerns
- RE: Example canvas element use - accessibility concerns
- Re: Caption@title instead of table@summary?
- Re: Caption and summary survey
- Entropy w.r.t. Namespace Discussion
- Re: ISSUE-4: Versioning, namespace URIs and MIME types ISSUE-60
- Re: video: various width/height attributes
- Re: ISSUE-4: Versioning, namespace URIs and MIME types ISSUE-60
- Re: Caption and summary survey
- Re: Example canvas element use - accessibility concerns
- Re: Caption and summary survey
- Re: Use and abuse of @summary
- Caption and summary survey
- Re: bufferingThrottled and bufferingRate
- Re: ISSUE-4: Versioning, namespace URIs and MIME types ISSUE-60
- Re: ISSUE-4: Versioning, namespace URIs and MIME types ISSUE-60
- Re: several messages
Thursday, 19 February 2009
- Re: Example canvas element use - accessibility concerns
- Re: Example canvas element use - accessibility concerns
- RE: Example canvas element use - accessibility concerns
- Re: ISSUE-4: Versioning, namespace URIs and MIME types
- Re: Reuse of 1999 XHTML namespace, text/html and application/xhtml+xml media types
- Re: DOM idiosyncracies and made-up tag names
- Re: DOM idiosyncracies and made-up tag names
- DOM idiosyncracies and made-up tag names
- Re: Use and abuse of @summary
- Re: ISSUE-4: Versioning, namespace URIs and MIME types
- Re: ISSUE-4: Versioning, namespace URIs and MIME types
- Re: ISSUE-4: Versioning, namespace URIs and MIME types
- Re: ISSUE-4: Versioning, namespace URIs and MIME types
- RE: ISSUE-4: Versioning, namespace URIs and MIME types
- Re: ISSUE-4: Versioning, namespace URIs and MIME types
- RE: ISSUE-4: Versioning, namespace URIs and MIME types
- Re: Example canvas element use - accessibility concerns
- Re: Use and abuse of @summary
- RE: Example canvas element use - accessibility concerns
- RE: ISSUE-4: Versioning, namespace URIs and MIME types
- RE: Example canvas element use - accessibility concerns
- Re: Example canvas element use - accessibility concerns
- Re: Example canvas element use - accessibility concerns
- RE: ISSUE-4: Versioning, namespace URIs and MIME types
- Re: Example canvas element use - accessibility concerns
- RE: ISSUE-4: Versioning, namespace URIs and MIME types
Wednesday, 18 February 2009
- Re: ISSUE-4: Versioning, namespace URIs and MIME types
- Re: several messages
- Review of xhtml-media-types
- Re: ISSUE-4: Versioning, namespace URIs and MIME types
- Re: Caption@title instead of table@summary?
- Re: Reuse of 1999 XHTML namespace, text/html and application/xhtml+xml media types
- Re: ISSUE-4: Versioning, namespace URIs and MIME types
- Re: ISSUE-4: Versioning, namespace URIs and MIME types
- RE: ISSUE-4: Versioning, namespace URIs and MIME types
- RE: Example canvas element use - accessibility concerns
- RE: ISSUE-4: Versioning, namespace URIs and MIME types
- Re: Caption@title instead of table@summary?
- Re: Use and abuse of @summary
- Re: ISSUE-4: Versioning, namespace URIs and MIME types ISSUE-60
- Re: ISSUE-4: Versioning, namespace URIs and MIME types ISSUE-60
- RE: ISSUE-4: Versioning, namespace URIs and MIME types
- Re: ISSUE-4: Versioning, namespace URIs and MIME types ISSUE-60
- Re: ISSUE-4: Versioning, namespace URIs and MIME types ISSUE-60
- Re: Use and abuse of @summary
- Re: ISSUE-4: Versioning, namespace URIs and MIME types ISSUE-60
- Re: Example canvas element use - accessibility concerns
- Re: Example canvas element use - accessibility concerns
- Re: ISSUE-4: Versioning, namespace URIs and MIME types ISSUE-60
- Re: Example canvas element use - accessibility concerns
- Re: ISSUE-4: Versioning, namespace URIs and MIME types ISSUE-60
- Re: Example canvas element use - accessibility concerns
- Re: Use and abuse of @summary
- Re: Example canvas element use - accessibility concerns
- Re: Example canvas element use - accessibility concerns
- Re: Caption@title instead of table@summary?
- Re: ISSUE-4: Versioning, namespace URIs and MIME types ISSUE-60
- Re: Use and abuse of @summary
- Re: ISSUE-4: Versioning, namespace URIs and MIME types ISSUE-60
- (no subject)
- Re: ISSUE-4: Versioning, namespace URIs and MIME types
- Re: ISSUE-4: Versioning, namespace URIs and MIME types
- Re: ISSUE-4: Versioning, namespace URIs and MIME types
- Re: ISSUE-4: Versioning, namespace URIs and MIME types
- Re: Use and abuse of @summary
- Re: Caption@title instead of table@summary?
- Re: ISSUE-4: Versioning, namespace URIs and MIME types
- Re: Use and abuse of @summary
- Re: Need differentiator between "no alt text provided" and "no alt text necessary"
- Re: ISSUE-4: Versioning, namespace URIs and MIME types
- Re: fragid navigation and pct-encoded
- Re: Joint task force on ARIA user agent implementation
- Re: Example canvas element use - accessibility concerns
- Re: fragid navigation and pct-encoded
- Re: fragid navigation and pct-encoded
- Re: Example canvas element use - accessibility concerns
- Re: Example canvas element use - accessibility concerns
- Re: fragid navigation and pct-encoded
- Re: Example canvas element use - accessibility concerns
- {agenda} HTML WG telcon 2009-02-19
- Re: fragid navigation and pct-encoded
- Re: Caption@title instead of table@summary?
- Re: Example canvas element use - accessibility concerns
- Re: Example canvas element use - accessibility concerns
- Re: Example canvas element use - accessibility concerns
- Re: Caption@title instead of table@summary?
- Re: Example canvas element use - accessibility concerns
- Re: Example canvas element use - accessibility concerns
- Re: Example canvas element use - accessibility concerns
- Re: Example canvas element use - accessibility concerns
- Re: Example canvas element use - accessibility concerns
- Re: Need differentiator between "no alt text provided" and "no alt text necessary"
- Re: Example canvas element use - accessibility concerns
- Re: Use and abuse of @summary
- Re: ISSUE-4: Versioning, namespace URIs and MIME types
- Example canvas element use - accessibility concerns
- Re: Caption@title instead of table@summary?
- Re: Caption@title instead of table@summary?
- Re: Caption@title instead of table@summary?
- Re: Caption@title instead of table@summary?
- Use and abuse of @summary
- Re: Caption@title instead of table@summary?
- Re: fragid navigation and pct-encoded
- Re: fragid navigation and pct-encoded
- Re: fragid navigation and pct-encoded
- Re: fragid navigation and pct-encoded
- Re: fragid navigation and pct-encoded
- Caption@title instead of table@summary?
- Re: fragid navigation and pct-encoded
- Re: table/@summary, Re: ISSUE-4: Versioning, namespace URIs and MIME types
- Re: google supports rel="canonical" (ISSUE-27 rel-ownership)
- Re: fragid navigation and pct-encoded
- Re: fragid navigation and pct-encoded
- Re: fragid navigation and pct-encoded
- Re: ISSUE-4: Versioning, namespace URIs and MIME types
- Re: google supports rel="canonical" (ISSUE-27 rel-ownership)
- Re: ISSUE-4: Versioning, namespace URIs and MIME types
Tuesday, 17 February 2009
- RE: ISSUE-4: Versioning, namespace URIs and MIME types
- RE: ISSUE-4: Versioning, namespace URIs and MIME types
- Re: ISSUE-4: Versioning, namespace URIs and MIME types
- Re: [whatwg] The <iframe> element and sandboxing ideas
- google supports rel="canonical" (ISSUE-27 rel-ownership)
- Re: table/@summary, Re: ISSUE-4: Versioning, namespace URIs and MIME types
- Re: ISSUE-4: Versioning, namespace URIs and MIME types
- Re: ISSUE-4: Versioning, namespace URIs and MIME types
- table/@summary, Re: ISSUE-4: Versioning, namespace URIs and MIME types
- Re: ISSUE-4: Versioning, namespace URIs and MIME types
- RE: ISSUE-4: Versioning, namespace URIs and MIME types
- Re: ISSUE-4: Versioning, namespace URIs and MIME types
- RE: ISSUE-4: Versioning, namespace URIs and MIME types
- Re: ISSUE-4: Versioning, namespace URIs and MIME types
- Re: ISSUE-4: Versioning, namespace URIs and MIME types
- WG Decision - spec license use cases
- RE: ISSUE-4: Versioning, namespace URIs and MIME types
- Re: ISSUE-4: Versioning, namespace URIs and MIME types
- RE: ISSUE-4: Versioning, namespace URIs and MIME types
- Re: ISSUE-4: Versioning, namespace URIs and MIME types
- Re: What's the problem? "Reuse of 1998 XHTML namespace is potentially misleading/wrong"
- Re: What's the problem? "Reuse of 1998 XHTML namespace is potentially misleading/wrong"
- Re: What's the problem? "Reuse of 1998 XHTML namespace is potentially misleading/wrong"
- RE: ISSUE-4: Versioning, namespace URIs and MIME types
- Re: table caption as a short description, @summary as a long description
- Re: ISSUE-4: Versioning, namespace URIs and MIME types
- [Bug 6590] New: character encoding mapping needs to be used for form submission too
- Re: ISSUE-4: Versioning, namespace URIs and MIME types
- RE: ISSUE-4: Versioning, namespace URIs and MIME types
- Re: table caption as a short description, @summary as a long description
- Re: ISSUE-4: Versioning, namespace URIs and MIME types (was Re: What's the problem? "Reuse of 1998 XHTML namespace is potentially misleading/wrong")
- RE: ISSUE-4: Versioning, namespace URIs and MIME types (was Re: What's the problem? "Reuse of 1998 XHTML namespace is potentially misleading/wrong")
- Re: What's the problem? "Reuse of 1998 XHTML namespace is potentially misleading/wrong"
- RE: What's the problem? "Reuse of 1998 XHTML namespace is potentially misleading/wrong"
- Re: What's the problem? "Reuse of 1998 XHTML namespace is potentially misleading/wrong"
- Re: What's the problem? "Reuse of 1998 XHTML namespace is potentially misleading/wrong"
- ISSUE-4: Versioning, namespace URIs and MIME types (was Re: What's the problem? "Reuse of 1998 XHTML namespace is potentially misleading/wrong")
Monday, 16 February 2009
- RE: What's the problem? "Reuse of 1998 XHTML namespace is potentially misleading/wrong"
- RE: What's the problem? "Reuse of 1998 XHTML namespace is potentially misleading/wrong"
- Re: What's the problem? "Reuse of 1998 XHTML namespace is potentially misleading/wrong"
- What's the problem with Reuse of 1998 XHTML namespace?
- Re: What's the problem? "Reuse of 1998 XHTML namespace is potentially misleading/wrong"
- RE: What's the problem? "Reuse of 1998 XHTML namespace is potentially misleading/wrong"
- Re: What's the problem? "Reuse of 1998 XHTML namespace is potentially misleading/wrong"
- What's the problem with Reuse of 1998 XHTML namespace?
- Re: What's the problem? "Reuse of 1998 XHTML namespace is potentially misleading/wrong"
- announce list [was: Re: publication decision [was: details on report of PFWG HTML5 actions & issues status]]
- Re: What's the problem? "Reuse of 1998 XHTML namespace is potentially misleading/wrong"
- RE: What's the problem? "Reuse of 1998 XHTML namespace is potentially misleading/wrong"
- Re: XHTML namespace, DOCTYPE, and other versioning mechanisms
- Re: XHTML namespace, DOCTYPE, and other versioning mechanisms
- XHTML namespace, DOCTYPE, and other versioning mechanisms
- Re: What's the problem? "Reuse of 1998 XHTML namespace is potentially misleading/wrong"
- RE: What's the problem? "Reuse of 1998 XHTML namespace is potentially misleading/wrong"
- Re: What's the problem? "Reuse of 1998 XHTML namespace is potentially misleading/wrong"
- Re: What's the problem? "Reuse of 1998 XHTML namespace is potentially misleading/wrong"
- Re: What's the problem? "Reuse of 1998 XHTML namespace is potentially misleading/wrong"
- RE: What's the problem? "Reuse of 1998 XHTML namespace is potentially misleading/wrong"
- Re: What's the problem? "Reuse of 1998 XHTML namespace is potentially misleading/wrong"
- RE: What's the problem? "Reuse of 1998 XHTML namespace is potentially misleading/wrong"
- [Bug 6586] New: Zero margin quirk not quite right
- [Bug 6585] New: Rendering: <marquee bgcolor>
- Re: priority based loading of web page elements
- Re: priority based loading of web page elements
- Re: priority based loading of web page elements
Sunday, 15 February 2009
- priority based loading of web page elements
- Re: [html5] proposal to add <text> element.
- Re: [html5] proposal to add <text> element.
- Re: [html5] proposal to add <text> element.
- Re: [html5] proposal to add <text> element.
- Re: TR/web-forms-2 -> TR/html5
- Re: [html5] proposal to add <text> element.
- Re: TR/web-forms-2 -> TR/html5
- Minor parsing wording comments
- Re: The <iframe> element and sandboxing ideas
- Re: [html5] proposal to add <text> element.
Saturday, 14 February 2009
Friday, 13 February 2009
Saturday, 14 February 2009
- RE: Spec license use cases - WG Decision on the Record?
- Re: publication decision [was: details on report of PFWG HTML5 actions & issues status]
- Re: Spec license use cases - WG Decision on the Record?
- Re: Spec license use cases - WG Decision on the Record?
Friday, 13 February 2009
- Re: The <iframe> element and sandboxing ideas
- RE: Implementation of head@profile
- Re: The <iframe> element and sandboxing ideas
- Re: designMode and scripts (designModeScriptBlocked)
- Re: publication decision [was: details on report of PFWG HTML5 actions & issues status]
- Re: publication decision [was: details on report of PFWG HTML5 actions & issues status]
- Re: publication decision [was: details on report of PFWG HTML5 actions & issues status]
- Re: publication decision [was: details on report of PFWG HTML5 actions & issues status]
- table caption as a short description, @summary as a long description
- Re: revised table headers design is OK, right?
- Re: details on report of PFWG HTML5 actions & issues status
- Re: details on report of PFWG HTML5 actions & issues status
- Re: details on report of PFWG HTML5 actions & issues status
- Re: details on report of PFWG HTML5 actions & issues status
- Re: details on report of PFWG HTML5 actions & issues status
- Re: details on report of PFWG HTML5 actions & issues status
- Re: Implementation of head@profile
- Re: details on report of PFWG HTML5 actions & issues status
- Re: revised table headers design is OK, right?
- Re: details on report of PFWG HTML5 actions & issues status
- Re: details on report of PFWG HTML5 actions & issues status
- Re: details on report of PFWG HTML5 actions & issues status
- Re: details on report of PFWG HTML5 actions & issues status
- Re: Table feedback
- Re: Character Set Alias Matching
- Re: Comparing conformance requirements against real-world docs
- Re: HTML is a declarative mark-up language
- Re: What's the problem? "Reuse of 1998 XHTML namespace is potentially misleading/wrong"
- Re: window.onerror initial value
- Re: Lose Focus When Hidden? (SVG ISSUE-2031)
- Re: What's the problem? "Reuse of 1998 XHTML namespace is potentially misleading/wrong"
- Re: What's the problem? "Reuse of 1998 XHTML namespace is potentially misleading/wrong"
Thursday, 12 February 2009
- Re: TR/web-forms-2 -> TR/html5
- TR/web-forms-2 -> TR/html5
- The status and compatibility of web standards
- details on report of PFWG HTML5 actions & issues status
- Re: What's the problem? "Reuse of 1998 XHTML namespace is potentially misleading/wrong"
- Re: What's the problem? "Reuse of 1998 XHTML namespace is potentially misleading/wrong"
- Re: What's the problem? "Reuse of 1998 XHTML namespace is potentially misleading/wrong"
- Re: What's the problem? "Reuse of 1998 XHTML namespace is potentially misleading/wrong"
- Re: What's the problem? "Reuse of 1998 XHTML namespace is potentially misleading/wrong"
- Re: What's the problem? "Reuse of 1998 XHTML namespace is potentially misleading/wrong"
- Re: What's the problem? "Reuse of 1998 XHTML namespace is potentially misleading/wrong"
- Re: revised table headers design is OK, right?
- Re: a11y : cell headers order has to be consistent and ordered (was: revised table headers design is OK, right?)
- Re: What's the problem? "Reuse of 1998 XHTML namespace is potentially misleading/wrong"
- Re: What's the problem? "Reuse of 1998 XHTML namespace is potentially misleading/wrong"
- Re: What's the problem? "Reuse of 1998 XHTML namespace is potentially misleading/wrong"
- Re: What's the problem? "Reuse of 1998 XHTML namespace is potentially misleading/wrong"
- Re: What's the problem? "Reuse of 1998 XHTML namespace is potentially misleading/wrong"
- Re: revised table headers design is OK, right?
- Re: What's the problem? "Reuse of 1998 XHTML namespace is potentially misleading/wrong"
- Re: What's the problem? "Reuse of 1998 XHTML namespace is potentially misleading/wrong"
- Re: revised table headers design is OK, right?
- Re: Need differentiator between "no alt text provided" and "no alt text necessary"
- Re: What's the problem? "Reuse of 1998 XHTML namespace is potentially misleading/wrong"
- Re: What's the problem? "Reuse of 1998 XHTML namespace is potentially misleading/wrong"
- Re: Need differentiator between "no alt text provided" and "no alt text necessary"
- Re: alt / no alt / etc Re: "downplayed errors"
- [Bug 6563] New: Specify if innerHTML setting should use the quirkiness of the document
- [Bug 6562] New: Define parsing quirks
- Re: cloneNode() and script execution
- Re: Proposed amends to <small> element
- Re: Need differentiator between "no alt text provided" and "no alt text necessary"
- Re: several messages
- Re: Proposed amends to <small> element
- Re: [html5] proposal to add <text> element.
- Re: Proposed amends to <small> element
- Re: Placing elements in the HTML namespace
- Re: Proposed amends to <small> element
- Change to AAA
- Re: What's the problem? "Reuse of 1998 XHTML namespace is potentially misleading/wrong"
- Re: alt / no alt / etc Re: "downplayed errors"
Wednesday, 11 February 2009
- Re: What's the problem? "Reuse of 1998 XHTML namespace is potentially misleading/wrong"
- Re: Need differentiator between "no alt text provided" and "no alt text necessary"
- Re: head@profile: another dropped attribute
- Re: What's the problem? "Reuse of 1998 XHTML namespace is potentially misleading/wrong"
- Re: What's the problem? "Reuse of 1998 XHTML namespace is potentially misleading/wrong"
- Re: What's the problem? "Reuse of 1998 XHTML namespace is potentially misleading/wrong"
- Re: What's the problem? "Reuse of 1998 XHTML namespace is potentially misleading/wrong"
- Action-83: 16x16 IE icon
- RE: Spec license
- Re: What's the problem? "Reuse of 1998 XHTML namespace is potentially misleading/wrong"
- RE: What's the problem? "Reuse of 1998 XHTML namespace is potentially misleading/wrong"
- Re: revised table headers design is OK, right?
- Re: What's the problem? "Reuse of 1998 XHTML namespace is potentially misleading/wrong"
- Re: What's the problem? "Reuse of 1998 XHTML namespace is potentially misleading/wrong"
- Re: What's the problem? "Reuse of 1998 XHTML namespace is potentially misleading/wrong"
- Re: What's the problem? "Reuse of 1998 XHTML namespace is potentially misleading/wrong"
- revised table headers design is OK, right?
- RE: What's the problem? "Reuse of 1998 XHTML namespace is potentially misleading/wrong"
- Re: What's the problem? "Reuse of 1998 XHTML namespace is potentially misleading/wrong"
- What's the problem? "Reuse of 1998 XHTML namespace is potentially misleading/wrong"
- Re: alt / no alt / etc Re: "downplayed errors"
- designMode and scripts (designModeScriptBlocked)
- Re: Joint task force on ARIA user agent implementation
- Re: Fwd: table, tbody, tr (was : Rendering section feedback)
- Re: Rendering section feedback
- Re: Rendering section feedback
- Fwd: table, tbody, tr (was : Rendering section feedback)
- Re: IE compat with coords parsing
- Re: Conditional branch in tree builder based on DOM state
- Re: [html5] proposal to add <text> element.
- Re: Rendering section feedback
- Re: Rendering section feedback
- Re: [html5] proposal to add <text> element.
- Re: [html5] proposal to add <text> element.
- alt / no alt / etc Re: "downplayed errors"
- Re: [html5] proposal to add <text> element.
- Re: Rendering section feedback
- Re: [html5] proposal to add <text> element.
- [Bug 6556] New: When parsing legacy color returns an error
- Re: Rendering section feedback
- Re: [Bug 6543] New: Mint a new element for figure captions
- Rendering section feedback
- Re: "downplayed errors"
- [html5] proposal to add <text> element.
Tuesday, 10 February 2009
- Re: "downplayed errors"
- Re: "downplayed errors"
- Re: "downplayed errors"
- Re: "downplayed errors"
- Re: Default (informal) Style Sheet
- Re: Default (informal) Style Sheet
- Re: "downplayed errors"
- Re: "downplayed errors"
- Re: "downplayed errors"
Monday, 9 February 2009
- Joint task force on ARIA user agent implementation
- [Bug 6546] New: List event handler attributes for certain elements
- [Bug 6544] New: Allow width=0 on <img> and <iframe>
- Re: [Bug 6543] New: Mint a new element for figure captions
- [Bug 6543] New: Mint a new element for figure captions
Sunday, 8 February 2009
Saturday, 7 February 2009
- URL Parsing: Add note of what unreserved becomes
- Re: Need differentiator between "no alt text provided" and "no alt text necessary"
- Re: Need differentiator between "no alt text provided" and "no alt text necessary"
Friday, 6 February 2009
- Re: Need differentiator between "no alt text provided" and "no alt text necessary"
- Re: Need differentiator between "no alt text provided" and "no alt text necessary"
- Re: Need differentiator between "no alt text provided" and "no alt text necessary"
- Re: Rendering: default style for <figure>
- Re: head@profile: another dropped attribute
- Re: Rendering: default style for <figure>
- Rendering: default style for <figure>
- [Bug 6536] New: Time element examples should be in the context of a goal-oriented microformat use case
- Re: Need differentiator between "no alt text provided" and "no alt text necessary"
- Re: head@profile: another dropped attribute
- Re: "downplayed errors"
- Re: "downplayed errors"
- Re: simple shorthand syntax proposal
- Re: Design principles - building from justification
- Re: head@profile: another dropped attribute
- ISSUE-66 image analysis heuristics
- Re: Design principles - building from justification
- Re: head@profile: another dropped attribute
- Re: head@profile: another dropped attribute
- Re: Design principles - building from justification
- Re: simple shorthand syntax proposal
Thursday, 5 February 2009
- Re: Design principles - building from justification
- Re: simple shorthand syntax proposal
- RE: Design principles - building from justification
- Re: Design principles - building from justification
- Re: Design principles - building from justification
- Re: simple shorthand syntax proposal
- Re: Design principles - building from justification
- RE: simple shorthand syntax proposal
- Design principles - building from justification
- Re: simple shorthand syntax proposal
- Re: simple shorthand syntax proposal
- Re: head@profile: another dropped attribute
- Re: head@profile: another dropped attribute
- Re: head@profile: another dropped attribute
- Re: head@profile: another dropped attribute
- Re: simple shorthand syntax proposal
- Re: simple shorthand syntax proposal
- Rendering Margins and Padding
- Re: simple shorthand syntax proposal
- Re: simple shorthand syntax proposal
- Re: simple shorthand syntax proposal
- Re: simple shorthand syntax proposal
- Re: head@profile: another dropped attribute
- Re: simple shorthand syntax proposal
- Re: simple shorthand syntax proposal
- Re: simple shorthand syntax proposal
- RE: simple shorthand syntax proposal
- RE: simple shorthand syntax proposal
- simple shorthand syntax proposal
- Re: Style sheet for W3C version of the spec
- Re: head@profile: another dropped attribute
- Rendering: more typos
- Rendering: typos
- Re: head@profile: another dropped attribute
- Re: "downplayed errors"
- Re: Style sheet for W3C version of the spec
- Re: head@profile: another dropped attribute
- Re: head@profile: another dropped attribute
- Re: head@profile: another dropped attribute
- Re: head@profile: another dropped attribute
- Re: head@profile: another dropped attribute
- Re: head@profile: another dropped attribute
- "downplayed errors"
- Re: head@profile: another dropped attribute
- Re: head@profile: another dropped attribute
- Re: head@profile: another dropped attribute
- Re: Style sheet for W3C version of the spec
- Re: Style sheet for W3C version of the spec
- Re: Style sheet for W3C version of the spec
- Re: head@profile: another dropped attribute
- Re: head@profile: another dropped attribute
- Re: Style sheet for W3C version of the spec
- RE: head@profile: another dropped attribute
- Re: head@profile: another dropped attribute
- Re: Implementation of head@profile
- RE: Implementation of head@profile
- Implementation of head@profile
- Style sheet for W3C version of the spec
- head@profile: another dropped attribute
Wednesday, 4 February 2009
- Re: Rendering: align=right and 'margin-right:auto'
- Re: table-summary argument
- Re: [html-author] Updates to the HTML Reference
- Re: Rendering: align=right and 'margin-right:auto'
- Rendering: comments
- Re: Re: [html-author] Updates to the HTML Reference
- Rendering: align=right and 'margin-right:auto'
- Re: Spec license
- [Bug 6529] New: value DOM attribute for input element in File Upload state
- Re: [html-author] Updates to the HTML Reference
- Re: Spec license
- Re: [html-author] Updates to the HTML Reference
- Re: Spec license
- Re: Spec license
- Re: table-summary argument
- Re: table-summary argument
Tuesday, 3 February 2009
- Re: table-summary argument
- RE: table-summary argument
- Re: table-summary argument
- Re: Spec license
- RE: Spec license
- Re: Spec license
- Re: Spec license
- Re: Spec license
- Re: table-summary argument
- Re: Spec license
- Re: Spec license
- Re: Spec license
- Re: Spec license
- Re: Spec license
- Re: Spec license
- Re: Charter (was: Re: Discussions with plh)
- Re: table-summary argument
- Re: table-summary argument
- [html-author] Updates to the HTML Reference
- Re: [html-author] Updates to the HTML Reference
- Re: Spec license
- table-summary argument
- Re: Spec license
- Re: Spec license
- Re: Rendering feedback
- Re: Rendering feedback
- Re: Spec license
- Re: Spec license
- Re: Spec license
- Re: Spec license
- Re: Spec license (was: Re: Discussions with plh)
- Re: Spec license (was: Re: Discussions with plh)
- Re: Discussions with plh [was: Moving Forward]
- Re: Discussions with plh [was: Moving Forward]
- Re: Spec license
- Re: Need differentiator between "no alt text provided" and "no alt text necessary"
- Re: Spec license
- Spec license (was: Re: Discussions with plh)
- Re: Need differentiator between "no alt text provided" and "no alt text necessary"
- Re: Need differentiator between "no alt text provided" and "no alt text necessary"
- Re: Need differentiator between "no alt text provided" and "no alt text necessary"
- Re: [html-author] Updates to the HTML Reference
- Re: Need differentiator between "no alt text provided" and "no alt text necessary"
- Re: Need differentiator between "no alt text provided" and "no alt text necessary"
Monday, 2 February 2009
- Re: Need differentiator between "no alt text provided" and "no alt text necessary"
- Re: Need differentiator between "no alt text provided" and "no alt text necessary"
- Re: HTML is a declarative mark-up language
- Re: Need differentiator between "no alt text provided" and "no alt text necessary"
- Re: Discussions with plh [was: Moving Forward]
- Re: Need differentiator between "no alt text provided" and "no alt text necessary"
- Re: Need differentiator between "no alt text provided" and "no alt text necessary"
- Re: Discussions with plh [was: Moving Forward]
- Re: Need differentiator between "no alt text provided" and "no alt text necessary"
- Re: Need differentiator between "no alt text provided" and "no alt text necessary"
- Re: Need differentiator between "no alt text provided" and "no alt text necessary"
- Re: Discussions with plh [was: Moving Forward]
- Need differentiator between "no alt text provided" and "no alt text necessary"
- Re: Discussions with plh [was: Moving Forward]
- Re: Discussions with plh [was: Moving Forward]
- Re: Discussions with plh [was: Moving Forward]
- Re: Discussions with plh (License)
- Re: Discussions with plh (License)
- Re: Rendering feedback
- Discussions with plh [was: Moving Forward]
- Re: Rendering feedback
- Rendering feedback
- Re: [html-author] Updates to the HTML Reference
- scribe volunteers?
- Re: [html-author] Updates to the HTML Reference
- Re: Table feedback
- [Bug 6516] New: obsolete attributes on HTMLDocument assume there is a body element
- [Bug 6515] New: the body element event handler attributes and missing Window object
- Re: Decision Policy [was: Intended Audience]
- Re: Decision Policy [was: Intended Audience]
- Re: Decision Policy [was: Intended Audience]
- Re: Decision Policy [was: Intended Audience]
- Re: HTML is a declarative mark-up language
- Re: HTML is a declarative mark-up language
Sunday, 1 February 2009
- Re: [html-author] Updates to the HTML Reference
- Re: [html-author] Updates to the HTML Reference
- [html-author] Updates to the HTML Reference
- Re: Decision Policy [was: Intended Audience]
- Character Set Alias Matching
- Re: Drop foster-parented stuff on the floor if parent gone
- Floating point number feedback
- Re: HTML is a declarative mark-up language
- Re: HTML is a declarative mark-up language
- Re: HTML is a declarative mark-up language
- Re: HTML is a declarative mark-up language
- Re: Decision Policy [was: Intended Audience]