public-html@w3.org from June 2008 by date

Monday, 30 June 2008

• Re: URIs in HTML5 and issues arising Ian Hickson
• Re: URIs in HTML5 and issues arising Ian Hickson
• Re: URIs in HTML5 and issues arising Ian Hickson
• [Bug 5823] New: Scope allowable on a td bugzilla@wiggum.w3.org
• [Bug 5822] New: The headers attribute should be able to reference a td bugzilla@wiggum.w3.org
• Re: URIs in HTML5 and issues arising Henri Sivonen
• Re: URIs in HTML5 and issues arising Michael(tm) Smith
• Re: URIs in HTML5 and issues arising Tim Bray
• Re: URIs in HTML5 and issues arising Henri Sivonen
• Re: encoding of characters in query parameters, was: Confusing use of "URI" to refer to IRIs, and IRI handling in the DOM Maciej Stachowiak
• Re: URIs in HTML5 and issues arising Robert J Burns
• Re: URIs in HTML5 and issues arising Julian Reschke
• Re: URIs in HTML5 and issues arising Philip Taylor
• RE: encoding of characters in query parameters, was: Confusing use of "URI" to refer to IRIs, and IRI handling in the DOM Brian Smith
• encoding of characters in query parameters, was: Confusing use of "URI" to refer to IRIs, and IRI handling in the DOM Julian Reschke
• Re: heads-up about "new" URLs section in HTML5 editor's draft Philip TAYLOR (Ret'd)
• Re: heads-up about "new" URLs section in HTML5 editor's draft Robert J Burns
• Re: URIs in HTML5 and issues arising Henri Sivonen
• Re: URIs in HTML5 and issues arising Ian Hickson
• Re: URIs in HTML5 and issues arising Anne van Kesteren
• Re: URIs in HTML5 and issues arising Julian Reschke
• Re: URIs in HTML5 and issues arising Julian Reschke
• Re: URIs in HTML5 and issues arising Ian Hickson
• Re: heads-up about "new" URLs section in HTML5 editor's draft Ian Hickson
• Re: URIs in HTML5 and issues arising Julian Reschke
• HTML5 "URL" definition vs. Web architecture [was: heads-up about "new" URLs section in HTML5 editor's draft] Michael(tm) Smith
• Re: heads-up about "new" URLs section in HTML5 editor's draft Roy T. Fielding
• Five things that are still broken in browsers, ten years later Karl Dubost
• Re: URIs in HTML5 and issues arising Karl Dubost

Sunday, 29 June 2008

• Re: Percent-encoded fragment identfiers and id matching - (was: Fragment Identifiers for HTML5) Michael A. Puls II
• Re: URIs in HTML5 and issues arising Ian Hickson
• Re: URIs in HTML5 and issues arising Maciej Stachowiak
• Re: Confusing use of "URI" to refer to IRIs, and IRI handling in the DOM Maciej Stachowiak
• Re: URIs in HTML5 and issues arising Robert J Burns
• Re: URIs in HTML5 and issues arising Julian Reschke
• Re: URIs in HTML5 and issues arising Philip Taylor
• Re: Confusing use of "URI" to refer to IRIs, and IRI handling in the DOM Robert J Burns
• Re: URIs in HTML5 and issues arising Julian Reschke
• Re: Confusing use of "URI" to refer to IRIs, and IRI handling in the DOM Henri Sivonen
• Re: Confusing use of "URI" to refer to IRIs, and IRI handling in the DOM Julian Reschke
• URIs in HTML5 and issues arising Ian Hickson
• Re: Confusing use of "URI" to refer to IRIs, and IRI handling in the DOM Henri Sivonen
• Re: expected results for URI encoding tests? Ian Hickson
• Re: Confusing use of "URI" to refer to IRIs, and IRI handling in the DOM Julian Reschke
• Re: Confusing use of "URI" to refer to IRIs, and IRI handling in the DOM Ian Hickson
• Re: Confusing use of "URI" to refer to IRIs, and IRI handling in the DOM Julian Reschke
• Re: Confusing use of "URI" to refer to IRIs, and IRI handling in the DOM Ian Hickson
• Re: Confusing use of "URI" to refer to IRIs, and IRI handling in the DOM Julian Reschke
• Re: Confusing use of "URI" to refer to IRIs, and IRI handling in the DOM Julian Reschke
• Re: Confusing use of "URI" to refer to IRIs, and IRI handling in the DOM Robert J Burns
• Re: Confusing use of "URI" to refer to IRIs, and IRI handling in the DOM Ian Hickson
• Re: Confusing use of "URI" to refer to IRIs, and IRI handling in the DOM Philip TAYLOR (Ret'd)
• Re: Percent-encoded fragment identfiers and id matching - (was: Fragment Identifiers for HTML5) Ian Hickson
• Re: Confusing use of "URI" to refer to IRIs, and IRI handling in the DOM Smylers
• Re: Confusing use of "URI" to refer to IRIs, and IRI handling in the DOM Smylers
• Re: Confusing use of "URI" to refer to IRIs, and IRI handling in the DOM Smylers
• Re: Confusing use of "URI" to refer to IRIs, and IRI handling in the DOM Julian Reschke
• [Bug 5821] New: meta/@scheme missing bugzilla@wiggum.w3.org

Saturday, 28 June 2008

• Re: Confusing use of "URI" to refer to IRIs, and IRI handling in the DOM Philip TAYLOR (Ret'd)
• Re: Confusing use of "URI" to refer to IRIs, and IRI handling in the DOM Charles McCathieNevile
• Re: heads-up about "new" URLs section in HTML5 editor's draft Robert J Burns
• RE: Confusing use of "URI" to refer to IRIs, and IRI handling in the DOM Justin James
• Re: Confusing use of "URI" to refer to IRIs, and IRI handling in the DOM Julian Reschke
• Re: Confusing use of "URI" to refer to IRIs, and IRI handling in the DOM Smylers
• RE: Confusing use of "URI" to refer to IRIs, and IRI handling in the DOM Brian Smith
• Re: Dangers of non-UTF-8 Re: Details on internal encoding declarations Julian Reschke
• Re: Dangers of non-UTF-8 Re: Details on internal encoding declarations Ian Hickson
• [Bug 5820] New: Work on WebSockets bugzilla@wiggum.w3.org
• Re: heads-up about "new" URLs section in HTML5 editor's draft Julian Reschke
• Re: heads-up about "new" URLs section in HTML5 editor's draft Anne van Kesteren
• Re: heads-up about "new" URLs section in HTML5 editor's draft Julian Reschke
• Re: heads-up about "new" URLs section in HTML5 editor's draft Anne van Kesteren
• Re: Spaces in URLs Julian Reschke
• Spaces in URLs Ian Hickson

Friday, 27 June 2008

• Re: Whitespace in attribute values Ian Hickson
• Re: Confusing use of "URI" to refer to IRIs, and IRI handling in the DOM Ian Hickson
• Re: Spec review: "URI (or IRI)" Ian Hickson
• Re: heads-up about "new" URLs section in HTML5 editor's draft Julian Reschke
• Re: heads-up about "new" URLs section in HTML5 editor's draft T.V Raman
• Re: heads-up about "new" URLs section in HTML5 editor's draft Mark Baker
• RE: heads-up about "new" URLs section in HTML5 editor's draft Justin James
• RE: heads-up about "new" URLs section in HTML5 editor's draft Justin James
• Re: heads-up about "new" URLs section in HTML5 editor's draft Philip TAYLOR (Ret'd)
• Re: expected results for URI encoding tests? Ian Hickson
• Re: heads-up about "new" URLs section in HTML5 editor's draft Mark Baker
• Re: heads-up about "new" URLs section in HTML5 editor's draft Julian Reschke
• Re: expected results for URI encoding tests? Julian Reschke
• RE: heads-up about "new" URLs section in HTML5 editor's draft Justin James
• Re: expected results for URI encoding tests? Philip Taylor
• Re: heads-up about "new" URLs section in HTML5 editor's draft Julian Reschke
• Re: expected results for URI encoding tests? Julian Reschke
• Re: heads-up about "new" URLs section in HTML5 editor's draft Mark Baker
• Re: expected results for URI encoding tests? Dan Connolly
• linking mail to issues was re: some other topic Charles McCathieNevile
• Re: expected results for URI encoding tests? Philip Taylor
• Re: @headers on th too or just td? Michael(tm) Smith
• Re: @headers on th too or just td? Ben 'Cerbera' Millard
• Re: @headers on th too or just td? Robert J Burns
• Re: @headers on th too or just td? Robert J Burns
• Re: @headers on th too or just td? Leif Halvard Silli
• Re: @headers on th too or just td? Steven Faulkner
• Re: @headers on th too or just td? Leif Halvard Silli
• Re: expected results for URI encoding tests? Julian Reschke
• Re: expected results for URI encoding tests? Philip Taylor
• Re: @headers on th too or just td? Michael(tm) Smith
• Re: SVG in HTML5 draft proposal Robin Berjon
• Re: SVG in HTML5 draft proposal Henri Sivonen
• Re: expected results for URI encoding tests? Julian Reschke
• Re: expected results for URI encoding tests? Philip Taylor
• adohoc URI test results for IE7, Re: expected results for URI encoding tests? Julian Reschke
• [Bug 5815] New: foreignObject in the SVG namespace should be scoping bugzilla@wiggum.w3.org
• Re: @headers on th too or just td? Ben 'Cerbera' Millard
• Re: @headers on th too or just td? Joshue O Connor
• heads-up about "new" URLs section in HTML5 editor's draft Michael(tm) Smith
• Re: @headers on th too or just td? Steven Faulkner
• [Bug 5814] New: Resolve the callback issue bugzilla@wiggum.w3.org
• Re: @headers on th too or just td? Joshue O Connor
• Re: SVG in HTML5 draft proposal David Woolley

Thursday, 26 June 2008

• Re: @headers on th too or just td? Leif Halvard Silli
• Re: expected results for URI encoding tests? Ian Hickson
• Re: @headers on th too or just td? Dan Connolly
• Re: expected results for URI encoding tests? Dan Connolly
• Re: expected results for URI encoding tests? Julian Reschke
• Re: @headers on th too or just td? Robert J Burns
• Re: expected results for URI encoding tests? Ian Hickson
• Re: @headers on th too or just td? Charles McCathieNevile
• expected results for URI encoding tests? Dan Connolly
• @headers on th too or just td? Dan Connolly
• Strict version description is wrong Kristof Zelechovski
• Re: ISSUE-54 (html5-doctype-vs-xslt): XSLT 1.0 can not generate HTML5 documents [HTML 5 spec] Philip TAYLOR (Ret'd)
• Re: ISSUE-54 (html5-doctype-vs-xslt): XSLT 1.0 can not generate HTML5 documents [HTML 5 spec] Dan Connolly
• Request for PFWG WAI review of @summary for tabular data Joshue O Connor
• Re: ISSUE-55 (head-profile): head/@profile missing, but used in other specifications/formats Dan Connolly
• [Bug 5807] User Agent display of title attribute content not defined bugzilla@wiggum.w3.org
• [Bug 5809] New: Mitigate data loss when conforming documents are coerced to XML 1.0 bugzilla@wiggum.w3.org
• [Bug 5808] New: Define a way to coerce HTML5 parser output to an XML 1.0 4th ed. + Namespaces 1.0 infoset bugzilla@wiggum.w3.org
• [Bug 5807] User Agent display of title attribute content not defined bugzilla@wiggum.w3.org
• asking for UA developer's feedback on Content-Disposition filename I18N issue Julian Reschke
• ISSUE-55 (head-profile): head/@profile missing, but used in other specifications/formats HTML Issue Tracking Issue Tracker
• [Bug 5807] New: User Agent display of title attribute content not defined bugzilla@wiggum.w3.org
• Re: ProgressEvent and unreachable networkState LOADED in HTMLMediaElement Philip Jägenstedt
• Re: ISSUE-54 (html5-doctype-vs-xslt): XSLT 1.0 can not generate HTML5 documents [HTML 5 spec] Henri Sivonen
• Re: ISSUE-54 (html5-doctype-vs-xslt): XSLT 1.0 can not generate HTML5 documents [HTML 5 spec] Julian Reschke
• Re: ISSUE-54 (html5-doctype-vs-xslt): XSLT 1.0 can not generate HTML5 documents [HTML 5 spec] Sam Ruby
• ISSUE-54 (html5-doctype-vs-xslt): XSLT 1.0 can not generate HTML5 documents [HTML 5 spec] HTML Issue Tracking Issue Tracker

Wednesday, 25 June 2008

• [Bug 5803] New: HTML5 serialization is not compatible with XSLT bugzilla@wiggum.w3.org
• [Bug 5802] New: No mention of %uXXXX escapes bugzilla@wiggum.w3.org
• [Bug 5801] New: Conformance rules for xmlns unintuitively different for HTML and foreign content bugzilla@wiggum.w3.org
• ProgressEvent and unreachable networkState LOADED in HTMLMediaElement Philip Jägenstedt
• RE: Proposed Final Review of W3C TAG Finding "Passwords in the Clear" Justin James
• Re: Proposed Final Review of W3C TAG Finding "Passwords in the Clear" Mark Baker
• RE: Proposed Final Review of W3C TAG Finding "Passwords in the Clear" Justin James
• Re: Proposed Final Review of W3C TAG Finding "Passwords in the Clear" Ian Hickson

Tuesday, 24 June 2008

• Proposed Final Review of W3C TAG Finding "Passwords in the Clear" David Orchard
• [Bug 5798] New: Deferring end tag eating to after head gives weird errors bugzilla@wiggum.w3.org
• [Bug 5796] New: <li><div><p><li> no longer matches IE bugzilla@wiggum.w3.org
• Re: <canvas> JPEG quality Philip Taylor
• Canvas miscellaneous comments Philip Taylor
• [Bug 5793] New: Editorial: "Act as if" hard to follow bugzilla@wiggum.w3.org
• [Bug 5792] New: li/dd/dt end tag in body when no corresponding elt on stack bugzilla@wiggum.w3.org
• Re: In body other end tag handling convoluted to get at most one error Henri Sivonen
• Re: URI parsing Julian Reschke
• Re: URI parsing Ian Hickson
• Re: URI parsing Julian Reschke
• Re: URI parsing Julian Reschke
• Re: URI parsing Ian Hickson
• URI parsing Julian Reschke
• RE: DOM Storage feedback Robert O'Callahan
• RE: DOM Storage feedback Sunava Dutta
• RE: DOM Storage feedback Ian Hickson
• RE: DOM Storage feedback Zhenbin Xu

Monday, 23 June 2008

• The header element's textual content Geoffrey Sneddon
• [Bug 5787] New: Rename "script that will execute as soon as the parser resumes" bugzilla@wiggum.w3.org
• Re: Fragment Identifiers for HTML5 Andrew Sidwell
• Re: Trying out SVG and MathML parsing Henri Sivonen
• Re: ISSUE-53 (mediatypereg): Need to update media type registrations [HTML 5 spec] Lachlan Hunt
• Re: SVG in HTML5 draft proposal Henri Sivonen
• Re: Fragment Identifiers for HTML5 Julian Reschke
• ISSUE-53 (mediatypereg): Need to update media type registrations [HTML 5 spec] HTML Issue Tracking Issue Tracker

Sunday, 22 June 2008

• Re: Empty attribute syntax and the DOM and CSS Daniel Schattenkirchner
• Percent-encoded fragment identfiers and id matching - (was: Fragment Identifiers for HTML5) Michael A. Puls II
• Re: Fragment Identifiers for HTML5 Michael A. Puls II
• Re: Empty attribute syntax and the DOM and CSS Philip Taylor
• Re: Empty attribute syntax and the DOM and CSS Daniel Schattenkirchner
• Re: Empty attribute syntax and the DOM and CSS Lachlan Hunt
• Empty attribute syntax and the DOM and CSS Daniel Schattenkirchner
• Re: Fragment Identifiers for HTML5 Robert J Burns

Saturday, 21 June 2008

• Re: Canvas line style comments Philip Taylor
• Re: Fragment Identifiers for HTML5 Michael A. Puls II
• Fragment Identifiers for HTML5 Julian Reschke

Friday, 20 June 2008

• RE: DOM Storage feedback Ian Hickson
• Re: Missing src on img/audio/video and fallback content Ian Hickson
• RE: DOM Storage feedback Zhenbin Xu
• Re: [Bug 5776] New: Authors need more control over handling of embedded resources Robert J Burns
• Missing src on img/audio/video and fallback content Philip Jägenstedt
• [Bug 5777] New: referencing subordinate text or asides should be through an alternate attribute bugzilla@wiggum.w3.org
• [Bug 5776] New: Authors need more control over handling of linked resources bugzilla@wiggum.w3.org
• Re: changes in HTML5 draft regarding XHTML1 Roland Merrick
• Re: changes in HTML5 draft regarding XHTML1 Michael(tm) Smith
• RE: DOM Storage feedback Ian Hickson
• RE: DOM Storage feedback Zhenbin Xu

Thursday, 19 June 2008

• Re: Canvas path transformations Philip Taylor
• Re: Trying out SVG and MathML parsing Philip Taylor
• Re: DOM Storage feedback Maciej Stachowiak
• Re: DOM Storage feedback Adam Roben
• Trying out SVG and MathML parsing Henri Sivonen
• [Bug 5773] New: Authors need more control over handling of linked resources bugzilla@wiggum.w3.org
• [Bug 5772] New: ID value types too restrictive and inflexible for some use cases bugzilla@wiggum.w3.org
• Re: changes in HTML5 draft regarding XHTML1 Roland Merrick
• Re: changes in HTML5 draft regarding XHTML1 Karl Dubost
• Re: changes in HTML5 draft regarding XHTML1 Roland Merrick
• Re: DOM Storage feedback Maciej Stachowiak
• RE: DOM Storage feedback Ian Hickson
• RE: Race conditions in HTML 5? Bonner, Matt
• RE: Questions on HTML 5 differences from HTML 4 Bonner, Matt

Wednesday, 18 June 2008

• [Bug 5769] New: HTMLMediaElement.currentLoop readonly? bugzilla@wiggum.w3.org
• <scene> Dmitry Turin
• Re: favicon content-type sniffing Ian Hickson
• [Bug 5768] New: content sniffing should be allowed on link elements with a relationship type of icon bugzilla@wiggum.w3.org

Tuesday, 17 June 2008

• favicon content-type sniffing Philip Taylor
• Re: Outline algorithm Ian Hickson
• [Bug 5766] New: priority request: reply to outline e-mail bugzilla@wiggum.w3.org
• Re: Re-entrant invocation of the tree builder Ian Hickson
• Re-entrant invocation of the tree builder Henri Sivonen
• HTML WG f2f at October W3C TPAC: Registration open Michael(tm) Smith

Monday, 16 June 2008

• Re: What about backward compatibility? Bill Mason
• What about backward compatibility? Daniel Hejduk
• RE: drastic reduction of HTML WG issue tracker contributors: explanation please? Dan Connolly
• RE: drastic reduction of HTML WG issue tracker contributors: explanation please? Justin James
• Re: drastic reduction of HTML WG issue tracker contributors: explanation please? Steven Faulkner
• Re: drastic reduction of HTML WG issue tracker contributors: explanation please? Philip TAYLOR (Ret'd)
• Re: drastic reduction of HTML WG issue tracker contributors: explanation please? Karl Dubost
• drastic reduction of HTML WG issue tracker contributors: explanation please? Gregory J. Rosmaita
• Re: bugzilla fyi - gmail marks new account confirmation as spam Michael(tm) Smith
• bugzilla fyi - gmail marks new account confirmation as spam Michael A. Puls II
• Re: <canvas> JPEG quality Lachlan Hunt

Sunday, 15 June 2008

• [Bug 5759] New: Newly introduced void elements are not mentioned in "Writing HTML Documents" section bugzilla@wiggum.w3.org
• Re: Failing To Understand The Creating An Outline Section Ian Hickson
• [Bug 5758] New: insufficient accessibility fallback for <audio> or <video> bugzilla@wiggum.w3.org

Saturday, 14 June 2008

• Re: responding to bugzilla: Do's and Don'ts Michael(tm) Smith
• [Bug 5757] New: MediaElement features are needed on OBJECT element bugzilla@wiggum.w3.org
• [Bug 5756] New: Need UA norms for exposing (non-displayed) HTML document data bugzilla@wiggum.w3.org
• [Bug 5755] New: Need to expose media metadata properties bugzilla@wiggum.w3.org
• [Bug 5754] New: List elements content model issues bugzilla@wiggum.w3.org
• responding to bugzilla: Do's and Don'ts Michael(tm) Smith
• notification of new bugzilla issues Cc'ed here Michael(tm) Smith
• [Bug 5753] New: parsing issues with legacy UAs bugzilla@wiggum.w3.org
• [Bug 5752] New: Parsing should be specified for future updates bugzilla@wiggum.w3.org
• [Bug 5751] New: IGNORE ME (sorry for noise...) bugzilla@wiggum.w3.org
• Why public-html-bugzilla@w3.org? Why bugzilla? Michael(tm) Smith
• new list: public-html-bugzilla@w3.org Michael(tm) Smith

Friday, 13 June 2008

• [Fwd: [Bug 5744] Improved Fragment Identifiers] Erik Wilde
• [Fwd: [Bug 5744] Improved Fragment Identifiers] Erik Wilde
• Clarification on chairing for the group Michael(tm) Smith
• [Fwd: [Bug 5744] Improved Fragment Identifiers] Erik Wilde
• [Bug 5744] Improved Fragment Identifiers Erik Wilde
• [CfP] process proposal for a special meeting or meetings for fact-finding on issues related to @alt in HTML5 Al Gilman
• Unsupported transport-layer encodings Philip Taylor
• dataset case issue Anne van Kesteren
• isContentEditable is a boolean Simon Pieters
• Re: <canvas> JPEG quality Ian Hickson
• Re: Canvas line style comments Ian Hickson
• Re: Canvas gradient comments Ian Hickson
• changes in HTML5 draft regarding XHTML1 Michael(tm) Smith
• Re: several messages about radial gradients Ian Hickson
• Re: [author-guide] Describing the Syntax Michael A. Puls II
• Re: Canvas ImageData comments Ian Hickson
• Re: Canvas ImageData comments Ian Hickson
• Re: X(HT)ML Fragment Identifiers Michael(tm) Smith
• Re: X(HT)ML Fragment Identifiers Erik Wilde
• Re: improved HTML fragment identifiers Michael(tm) Smith
• Re: Canvas arc comments Ian Hickson
• Re: improved HTML fragment identifiers Erik Wilde

Thursday, 12 June 2008

• Re: X(HT)ML Fragment Identifiers Erik Wilde
• Re: Canvas security comments Ian Hickson
• Re: Canvas shadows should not be optional Ian Hickson
• Re: [canvas] 2d context fillRect() negative values for width/height Ian Hickson
• [author-guide] Describing the Syntax Lachlan Hunt
• Re: ARIA and CURIE "clarification" Michael(tm) Smith
• ARIA and CURIE "clarification" Gregory J. Rosmaita
• Re: mechanism to provide a summary of high density information easily discernible from a cursory visual glance Joshue O Connor
• Re: X(HT)ML Fragment Identifiers Ian Hickson
• Re: X(HT)ML Fragment Identifiers Robert J Burns
• Re: X(HT)ML Fragment Identifiers Philip TAYLOR (Ret'd)
• Re: X(HT)ML Fragment Identifiers Michael(tm) Smith
• Re: X(HT)ML Fragment Identifiers Michael(tm) Smith
• RE: Race conditions in HTML 5? Ian Hickson
• RE: Race conditions in HTML 5? Bonner, Matt

Wednesday, 11 June 2008

• Re: HTML WG co-chair, issues process Ian Hickson
• Failing To Understand The Creating An Outline Section Geoffrey Sneddon
• Re: HTML WG co-chair, issues process Philip TAYLOR (Ret'd)
• Re: HTML WG co-chair, issues process Ian Hickson
• HTML WG co-chair, issues process Dan Connolly
• Adjusting MathML attributes: definitionURL Henri Sivonen
• mechanism to provide a summary of high density information easily discernible from a cursory visual glance Robert J Burns
• Completed logging of issues with HTML5 draft Robert J Burns
• Re: Questions on HTML 5 differences from HTML 4 Anne van Kesteren
• Re: Proposal: ARIA-ROLE & CSS definition integration Pat Hayes

Tuesday, 10 June 2008

• Re: Race conditions in HTML 5? Boris Zbarsky
• RE: Race conditions in HTML 5? Bonner, Matt
• Re: Proposal: ARIA-ROLE & CSS definition integration James Craig
• RE: Race conditions in HTML 5? Ian Hickson
• RE: Race conditions in HTML 5? Bonner, Matt
• RE: Proposal: ARIA-ROLE & CSS definition integration Justin James
• Re: Questions on HTML 5 differences from HTML 4 Jon Barnett
• Re: Questions on HTML 5 differences from HTML 4 Jon Barnett
• Questions on HTML 5 differences from HTML 4 Bonner, Matt
• Re: Race conditions in HTML 5? Ian Hickson
• Re: Race conditions in HTML 5? Boris Zbarsky
• Re: Race conditions in HTML 5? Jim Jewett
• RE: Proposal: ARIA-ROLE & CSS definition integration Pat Hayes
• Re: Proposal: ARIA-ROLE & CSS definition integration Andrew Sidwell
• Re: Space characters in map name Henri Sivonen
• Re: How to add features to HTML5 (Was: tracker already has ternary state - RAISED) Steven Faulkner
• RE: Proposal: ARIA-ROLE & CSS definition integration Justin James
• Re: Race conditions in HTML 5? Boris Zbarsky
• Re: How to add features to HTML5 (Was: tracker already has ternary state - RAISED) Laura Carlson
• Race conditions in HTML 5? Bonner, Matt

Monday, 9 June 2008

• Re: X(HT)ML Fragment Identifiers Robert J Burns
• Re: improved HTML fragment identifiers Erik Wilde
• Re: X(HT)ML Fragment Identifiers Erik Wilde
• How to add features to HTML5 (Was: tracker already has ternary state - RAISED) Ian Hickson
• Re: Proposal: ARIA-ROLE & CSS definition integration Pat Hayes
• Re: Space characters in map name Michael A. Puls II
• RE: Proposal: ARIA-ROLE & CSS definition integration Pat Hayes
• Space characters in map name Henri Sivonen
• Events and disabled form controls Simon Pieters
• RE: Proposal: ARIA-ROLE & CSS definition integration Justin James
• Re: Proposal: ARIA-ROLE & CSS definition integration James Craig
• RE: Liaison with CSS WG to provide a mechanism for expressing the style of document semantics Justin James
• RE: Proposal: ARIA-ROLE & CSS definition integration Justin James
• RE: Proposal: ARIA-ROLE & CSS definition integration Justin James

Sunday, 8 June 2008

• Re: Proposal: ARIA-ROLE & CSS definition integration James Craig
• Re: Proposal: ARIA-ROLE & CSS definition integration Dannii
• RE: Proposal: ARIA-ROLE & CSS definition integration Justin James

Saturday, 7 June 2008

• RE: Questions on <datatemplate> (ref. call for exclusions) Bonner, Matt
• Re: X(HT)ML Fragment Identifiers Robert J Burns
• Re: improved HTML fragment identifiers Anne van Kesteren
• Re: improved HTML fragment identifiers Michael(tm) Smith
• Re: improved HTML fragment identifiers Michael(tm) Smith
• Re: Questions on <datatemplate> (ref. call for exclusions) Ian Hickson
• RE: Questions on <datatemplate> (ref. call for exclusions) Bonner, Matt
• Re: Questions on <datatemplate> (ref. call for exclusions) Philip Taylor
• Questions on <datatemplate> (ref. call for exclusions) Bonner, Matt (IPG)
• improved HTML fragment identifiers Erik Wilde

Friday, 6 June 2008

• Re: Proposal: ARIA-ROLE & CSS definition integration James Craig
• beforeprint / afterprint Anne van Kesteren
• Re: Other aria representations [was: Re: ARIA as stop-gap] Aaron M Leventhal
• Re: Placement of <base> & xml:base interaction Ian Hickson
• Other aria representations [was: Re: ARIA as stop-gap] Jim Jewett

Thursday, 5 June 2008

• a @name [was: ISSUE-47, Markup support for bookmark and clipping support of documents] Jim Jewett
• Re: <canvas> JPEG quality Philip Taylor
• Re: <canvas> JPEG quality Anne van Kesteren
• Re: <canvas> JPEG quality Dannii
• <canvas> JPEG quality Anne van Kesteren
• Re: Text presentation of image maps with <object> (detailed review of Semantics) Simon Pieters
• Is now a good time to start writing validator test cases systematically? Henri Sivonen
• Re: Liaison with CSS WG to provide a mechanism for expressing the style of document semantics Robert J Burns
• Re: Text presentation of image maps with <object> (detailed review of Semantics) Ian Hickson
• RE: Liaison with CSS WG to provide a mechanism for expressing the style of document semantics Justin James
• RE: ARIA as stop-gap (was Re: Next steps for the ARIA syntax discussion) Justin James
• Re: Proposal: ARIA-ROLE & CSS definition integration Olivier GENDRIN
• Re: Next steps for the ARIA syntax discussion Mark Birbeck

Wednesday, 4 June 2008

• We will have a telecon this week [was: No teleconference next week] Michael(tm) Smith
• Re: ARIA as stop-gap (was Re: Next steps for the ARIA syntax discussion) Leif Halvard Silli
• Re: Liaison with CSS WG to provide a mechanism for expressing the style of document semantics Robert J Burns
• RE: ARIA as stop-gap (was Re: Next steps for the ARIA syntax discussion) Justin James
• RE: Proposal: ARIA-ROLE & CSS definition integration Justin James
• Re: ARIA as stop-gap (was Re: Next steps for the ARIA syntax discussion) Leif Halvard Silli
• namespace-well-formedness and setting innerHTML in XML Simon Pieters
• Prefixes and setting innerHTML in XML Simon Pieters
• Re: [whatwg] Is EBCDIC support needed for not breaking the Web? Anne van Kesteren
• Re: [whatwg] Is EBCDIC support needed for not breaking the Web? Marek Pawlowski
• Syntax vs. the DOM Henri Sivonen
• Re: Next steps for the ARIA syntax discussion Elliotte Harold
• Re: Next steps for the ARIA syntax discussion ashok malhotra
• Re: Next steps for the ARIA syntax discussion Elliotte Harold
• Re: Proposal: ARIA-ROLE & CSS definition integration Olivier GENDRIN
• Re: Next steps for the ARIA syntax discussion Mark Birbeck
• Re: Next steps for the ARIA syntax discussion Robert J Burns
• Re: TAG concensus reached on ARIA implementation. Julian Reschke
• DOM-level conformance discrepancies between HTML5 and XHTML5 Henri Sivonen
• RE: Proposal: Default style definitions for elements Justin James
• RE: Liaison with CSS WG to provide a mechanism for expressing the style of document semantics Justin James
• Re: Liaison with CSS WG to provide a mechanism for expressing the style of document semantics Andrew Sidwell
• RE: Liaison with CSS WG to provide a mechanism for expressing the style of document semantics Justin James

Tuesday, 3 June 2008

• Re: Proposal: Default style definitions for elements Boris Zbarsky
• Proposal: ARIA-ROLE & CSS definition integration Justin James
• RE: Proposal: Default style definitions for elements Justin James
• Re: Proposal: Default style definitions for elements Anne van Kesteren
• Re: Proposal: Default style definitions for elements Boris Zbarsky
• Re: Proposal: Default style definitions for elements Robert J Burns
• RE: UA norm for redirects (both META and http) Justin James
• Proposal: Default style definitions for elements Justin James
• Re: Next steps for the ARIA syntax discussion Charles McCathieNevile
• Re: Liaison with CSS WG to provide a mechanism for expressing the style of document semantics Robert J Burns
• Re: Next steps for the ARIA syntax discussion Robert J Burns
• Re: Next steps for the ARIA syntax discussion Charles McCathieNevile
• Handling of undefined in createPattern() Simon Pieters
• RE: Liaison with CSS WG to provide a mechanism for expressing the style of document semantics Justin James
• Re: ISSUE-48 (marks-content-markup-attribute): 'marks' content markup attribute for Q (quotation) and BLOCKQUOTE [HTML 5 spec] Olivier GENDRIN
• Re: section 3.5.3 scrollIntoView Ian Hickson
• Re: 3.5.2. Focus Ian Hickson
• Re: Next steps for the ARIA syntax discussion Robert J Burns
• Re: ISSUE-48 (marks-content-markup-attribute): 'marks' content markup attribute for Q (quotation) and BLOCKQUOTE [HTML 5 spec] Robert J Burns
• Spec review results I Jens Meiert
• Re: ISSUE-48 (marks-content-markup-attribute): 'marks' content markup attribute for Q (quotation) and BLOCKQUOTE [HTML 5 spec] Olivier GENDRIN

Monday, 2 June 2008

• Re: ISSUE-48 (marks-content-markup-attribute): 'marks' content markup attribute for Q (quotation) and BLOCKQUOTE [HTML 5 spec] Robert J Burns
• RE: TAG concensus reached on ARIA implementation. Williams, Stuart (HP Labs, Bristol)
• Re: List Of Numbers Produces Incorrect Output (part of detailed review of common microsyntaxes) Geoffrey Sneddon
• Re: ISSUE-47, Markup support for bookmark and clipping support of documents Robert J Burns
• Re: ISSUE-48 (marks-content-markup-attribute): 'marks' content markup attribute for Q (quotation) and BLOCKQUOTE [HTML 5 spec] Robert J Burns
• Re: Liaison with CSS WG to provide a mechanism for expressing the style of document semantics Robert J Burns
• Common validation problems since last similar report Henri Sivonen
• Re: When can a node's prefix or localName contain a colon? Simon Pieters
• Re: No teleconference next week Chris Lilley
• Re: UA norm for redirects (both META and http) Robert J Burns
• TAG concensus reached on ARIA implementation. Williams, Stuart (HP Labs, Bristol)
• Re: When can a node's prefix or localName contain a colon? Cameron McCormack
• Re: When can a node's prefix or localName contain a colon? Simon Pieters
• Re: [whatwg] Is EBCDIC support needed for not breaking the Web? Simon Montagu
• Re: [whatwg] Is EBCDIC support needed for not breaking the Web? Henri Sivonen
• Re: When can a node's prefix or localName contain a colon? Cameron McCormack
• Re: When can a node's prefix or localName contain a colon? Ian Hickson
• Re: When can a node's prefix or localName contain a colon? Boris Zbarsky
• Re: When can a node's prefix or localName contain a colon? Ian Hickson
• Re: When can a node's prefix or localName contain a colon? Boris Zbarsky
• Re: [whatwg] Is EBCDIC support needed for not breaking the Web? Benjamin Smedberg
• Re: ISSUE-47, Markup support for bookmark and clipping support of documents Andrew Sidwell
• Re: ISSUE-48 (marks-content-markup-attribute): 'marks' content markup attribute for Q (quotation) and BLOCKQUOTE [HTML 5 spec] Andrew Sidwell

Sunday, 1 June 2008

• Re: When can a node's prefix or localName contain a colon? Cameron McCormack
• Re: innerHTML in XML Ian Hickson
• RE: Liaison with CSS WG to provide a mechanism for expressing the style of document semantics Justin James
• RE: UA norm for redirects (both META and http) Justin James
• RE: UA norm for redirects (both META and http) Justin James
• Re: [whatwg] Is EBCDIC support needed for not breaking the Web? Henri Sivonen
• Re: [whatwg] Is EBCDIC support needed for not breaking the Web? Bjoern Hoehrmann
• Re: UA norm for redirects (both META and http) Robert J Burns
• Re: UA norm for redirects (both META and http) Kornel Lesinski
• Is EBCDIC support needed for not breaking the Web? Henri Sivonen
• Re: UA norm for redirects (both META and http) Robert J Burns
• Re: UA norm for redirects (both META and http) Thomas Broyer
• Re: Liaison with CSS WG to provide a mechanism for expressing the style of document semantics Robert J Burns
• Re: UA norm for redirects (both META and http) Robert J Burns
• Re: innerHTML in XML Cameron McCormack
• Re: innerHTML in XML Julian Reschke
• Re: innerHTML in XML Cameron McCormack
• Re: innerHTML in XML Julian Reschke
• Re: innerHTML in XML Ian Hickson
• Re: When can a node's prefix or localName contain a colon? Cameron McCormack
• Re: innerHTML in XML Cameron McCormack
• Re: innerHTML in XML Thomas Broyer
• Re: When can a node's prefix or localName contain a colon? Geoffrey Sneddon
• RE: Liaison with CSS WG to provide a mechanism for expressing the style of document semantics Justin James
• When can a node's prefix or localName contain a colon? Cameron McCormack
• RE: UA norm for redirects (both META and http) Justin James
• RE: UA norm for redirects (both META and http) Justin James
• innerHTML in XML Cameron McCormack
• Re: Next steps for the ARIA syntax discussion Charles McCathieNevile
• Re: Next steps for the ARIA syntax discussion Charles McCathieNevile
• Re: Next steps for the ARIA syntax discussion Cameron McCormack
• Re: Next steps for the ARIA syntax discussion Charles McCathieNevile

Last message date: Monday, 30 June 2008 21:54:19 UTC