public-html@w3.org from July 2009 by date

Friday, 31 July 2009

• Re: [DRAFT] Heartbeat poll Maciej Stachowiak
• xmlns in the HTML5 DOM (was Re: [DRAFT] Heartbeat poll) Maciej Stachowiak
• Re: canvas text: line-height and getting .font Ian Hickson
• Re: Publishing a new draft (HTML5+RDFa) Sam Ruby
• Re: canvas text: web fonts Ian Hickson
• Re: [DRAFT] Heartbeat poll - update Sam Ruby
• Re: canvas text: ctx.font='inherit' Ian Hickson
• Re: Publishing a new draft (HTML5+RDFa) Ian Hickson
• Re: [DRAFT] Heartbeat poll - update Manu Sporny
• Re: [DRAFT] Heartbeat poll - update Sam Ruby
• Re: Publishing a new draft (HTML5+RDFa) Sam Ruby
• Re: Helping Canvas Tag Be Accessible Richard Schwerdtfeger
• Re: Publishing a new draft (HTML5+RDFa) Julian Reschke
• Re: Publishing a new draft Leif Halvard Silli
• Re: Google to pay for HTMLWG invited experts at TPAC 2009 Ian Hickson
• Re: [DRAFT] Heartbeat poll Manu Sporny
• Google to pay for HTMLWG invited experts at TPAC 2009 Ian Hickson
• Re: Publishing a new draft (HTML5+RDFa) Ian Hickson
• Re: Publishing a new draft (HTML5+RDFa) Joe D Williams
• Re: Publishing a new draft Leif Halvard Silli
• Re: Publishing a new draft (HTML5+RDFa) Ben Adida
• Re: Publishing a new draft Anne van Kesteren
• Re: Publishing a new draft (HTML5+RDFa) Ben Adida
• Re: Publishing a new draft Leif Halvard Silli
• Re: Publishing a new draft Anne van Kesteren
• Re: Publishing a new draft Leif Halvard Silli
• Re: PHP code only allowed in XHTML 5? Raul Tabasso
• Re: Fwd: Progress on video accessibility Leif Halvard Silli
• Re: Publishing a new draft Anne van Kesteren
• [DRAFT] Heartbeat poll Sam Ruby
• [Bug 7179] <xmp> should close <p> (does in IE and WebKit) bugzilla@wiggum.w3.org
• Re: Publishing a new draft (HTML5+RDFa) Sam Ruby
• Re: Publishing a new draft (HTML5+RDFa) Sam Ruby
• Re: Publishing a new draft (HTML5+RDFa) Michael Hausenblas
• Re: Publishing a new draft (HTML5+RDFa) Maciej Stachowiak
• Re: Publishing a new draft (HTML5+RDFa) Ian Hickson
• Re: Publishing a new draft (HTML5+RDFa) Michael Hausenblas
• Re: Publishing a new draft (HTML5+RDFa) Ian Hickson
• Fwd: Progress on video accessibility Silvia Pfeiffer
• Re: Publishing a new draft (HTML5+RDFa) Manu Sporny
• RE: [HTML5] 2.8 Character encodings Larry Masinter
• RE: Publishing a new draft (HTML5+RDFa) John Foliot
• RE: [HTML5] 2.8 Character encodings Larry Masinter
• Re: Publishing a new draft (HTML5+RDFa) Ian Hickson
• Re: Publishing a new draft (HTML5+RDFa) Maciej Stachowiak
• Re: Publishing a new draft (HTML5+RDFa) Sam Ruby
• Re: Publishing a new draft (HTML5+RDFa) Sam Ruby
• Re: Publishing a new draft (HTML5+RDFa) Maciej Stachowiak
• Re: Publishing a new draft (HTML5+RDFa) Sam Ruby
• Re: Publishing a new draft (HTML5+RDFa) Maciej Stachowiak
• Re: Publishing a new draft (HTML5+RDFa) Leif Halvard Silli
• Re: 4.11.6.3 Using the input element to define a command and input type=image Ian Hickson
• RE: Publishing a new draft (HTML5+RDFa) John Foliot
• RE: [HTML5] 2.8 Character encodings Ian Hickson
• Re: Publishing a new draft (HTML5+RDFa) Leif Halvard Silli
• Re: HTMLUnknownElement Ian Hickson

Thursday, 30 July 2009

• Re: Publishing a new draft (HTML5+RDFa) Maciej Stachowiak
• Re: Editorial: obsolete attributes should be lowercase Ian Hickson
• Re: Publishing a new draft (HTML5+RDFa) Maciej Stachowiak
• Re: Accessibility Procedure Comment Laura Carlson
• Re: Synonym elements (for implementors) Ian Hickson
• Re: Helping Canvas Tag Be Accessible Lachlan Hunt
• Re: Publishing a new draft (HTML5+RDFa) Sam Ruby
• Re: Default margins for new elements Ian Hickson
• Re: Publishing a new draft Leif Halvard Silli
• Re: comments on draft-barth-mime-sniffing Ian Hickson
• Re: Publishing a new draft (HTML5+RDFa) Leif Halvard Silli
• Fwd: Status Update on ARIA Last Call Comments Sam Ruby
• Re: Publishing a new draft (HTML5+RDFa) Sam Ruby
• Re: Publishing a new draft (HTML5+RDFa) Ben Adida
• Re: [HTML5] 2.8 Character encodings Anne van Kesteren
• Re: Publishing a new draft (HTML5+RDFa) Sam Ruby
• Re: Helping Canvas Tag Be Accessible Anne van Kesteren
• Re: Helping Canvas Tag Be Accessible Laura Carlson
• Re: Helping Canvas Tag Be Accessible Anne van Kesteren
• Re: Publishing a new draft (HTML5+RDFa) Ben Adida
• Re: HTML WG Issue tracker ACTION-131 Draft ALT spec Joe D Williams
• Re: Helping Canvas Tag Be Accessible Richard Schwerdtfeger
• Re: PHP code only allowed in XHTML 5? Leif Halvard Silli
• Re: Helping Canvas Tag Be Accessible Sam Ruby
• Re: Helping Canvas Tag Be Accessible Anne van Kesteren
• Re: Helping Canvas Tag Be Accessible Anne van Kesteren
• Re: Helping Canvas Tag Be Accessible Richard Schwerdtfeger
• Re: Helping Canvas Tag Be Accessible Steven Faulkner
• Re: Helping Canvas Tag Be Accessible Anne van Kesteren
• Re: Helping Canvas Tag Be Accessible Richard Schwerdtfeger
• Re: Helping Canvas Tag Be Accessible Richard Schwerdtfeger
• Re: regrets, voting Sam Ruby
• RE: HTML WG Issue tracker ACTION-131 Draft ALT spec Steven Faulkner
• regrets, voting Larry Masinter
• WebIDL checker Dominique Hazael-Massieux
• Re: Publishing a new draft (HTML5+RDFa) Ian Hickson
• Re: Publishing a new draft (HTML5+RDFa) Sam Ruby
• Re: Publishing a new draft (HTML5+RDFa) Jonas Sicking
• Re: Publishing a new draft (HTML5+RDFa) Joe D Williams
• Re: {agenda} HTML WG telcon 2009-07-30 Joe D Williams
• Re: Publishing a new draft (HTML5+RDFa) Manu Sporny

Wednesday, 29 July 2009

• Re: [free-aria] Re: Seeking feedback on HTML5 video accessibility experiment Silvia Pfeiffer
• Re: {agenda} HTML WG telcon 2009-07-30 Sam Ruby
• Re: PHP code only allowed in XHTML 5? Thomas Broyer
• Re: Seeking feedback on HTML5 video accessibility experiment John Foliot
• Re: Don't reopen active formatting elements for whitespace Ian Hickson
• Re: Don't reopen active formatting elements for whitespace Simon Pieters
• Re: Don't reopen active formatting elements for whitespace Ian Hickson
• Re: spellcheck DOM attribute sets content attributes to states, leaving case undefined Ian Hickson
• Re: equals sign in unquoted attribute Ian Hickson
• Re: PHP code only allowed in XHTML 5? Leif Halvard Silli
• Re: PHP code only allowed in XHTML 5? Leif Halvard Silli
• Re: PHP code only allowed in XHTML 5? Patrick H. Lauke
• Re: PHP code only allowed in XHTML 5? Leif Halvard Silli
• Re: PHP code only allowed in XHTML 5? Patrick H. Lauke
• Re: PHP code only allowed in XHTML 5? Leif Halvard Silli
• Re: [Bug 7075] New: The embed element should be deprecated Joe D Williams
• Re: PHP code only allowed in XHTML 5? Geoffrey Sneddon
• Re: PHP code only allowed in XHTML 5? Leif Halvard Silli
• Re: PHP code only allowed in XHTML 5? Tom Morris
• Re: PHP code only allowed in XHTML 5? Matthew Ratzloff
• Infinite loop in fragment case Geoffrey Sneddon
• Re: equals sign in unquoted attribute Lachlan Hunt
• Re: PHP code only allowed in XHTML 5? Lachlan Hunt
• Re: Publishing a new draft Sam Ruby
• Re: Publishing a new draft Joshue O Connor
• Re: Codecs for <video> and <audio> Silvia Pfeiffer
• Re: Publishing a new draft Leif Halvard Silli
• Re: Codecs for <video> and <audio> Sierk Bornemann
• RE: Publishing a new draft (was: Draft of @summary text for HTML 5 poll) Ian Hickson
• Re: Publishing a new draft Simon Pieters
• RE: Publishing a new draft (was: Draft of @summary text for HTML 5 poll) John Foliot
• Re: Publishing a new draft (was: Draft of @summary text for HTML 5 poll) Maciej Stachowiak
• RE: Publishing a new draft (was: Draft of @summary text for HTML 5 poll) Larry Masinter
• Re: Codecs for <video> and <audio> Silvia Pfeiffer
• [Bug 7161] If a heading has title text and then an image below it, then more text, how is the figure element handled in header and hgroup elements? bugzilla@wiggum.w3.org
• Re: PHP code only allowed in XHTML 5? Leif Halvard Silli
• Re: PHP code only allowed in XHTML 5? Leif Halvard Silli
• Re: Publishing a new draft Leif Halvard Silli
• re: HTML5 Microdata feedback/questions Ian Hickson
• Re: equals sign in unquoted attribute Ian Hickson
• Re: Normative warnings (was: Re: ACTION-128: Draft @summary voting text in conjunction with PF) Ian Hickson
• Re: postMessage: origin serialized too early Ian Hickson
• Re: several messages Ian Hickson
• {agenda} HTML WG telcon 2009-07-30 Chris Wilson

Tuesday, 28 July 2009

• Re: Codecs for <video> and <audio> Sierk Bornemann
• RE: <video>RE: Codecs for <video> and <audio> (survey of positions on ISSUE-7 video-codecs) John Foliot
• Re: <video>RE: Codecs for <video> and <audio> (survey of positions on ISSUE-7 video-codecs) David Singer
• <video>RE: Codecs for <video> and <audio> (survey of positions on ISSUE-7 video-codecs) John Foliot
• Re: FW: New Version Notification for draft-duerst-iri-bis-06 Ian Hickson
• Re: Selecting multiple options in a select element without multiple Ian Hickson
• Re: Codecs for <video> and <audio> (survey of positions on ISSUE-7 video-codecs) Dan Connolly
• Re: Codecs for <video> and <audio> (survey of positions on ISSUE-7 video-codecs) Sam Ruby
• Re: Codecs for <video> and <audio> (survey of positions on ISSUE-7 video-codecs) Dan Connolly
• Re: Accessibility Procedure Comment Sam Ruby
• Accessibility Procedure Comment Laura Carlson
• Selecting multiple options in a select element without multiple Geoffrey Sneddon
• Re: [whatwg] New HTML5 spec GIT collaboration repository Geoffrey Sneddon
• Re: document.write from script-inserted external script Ian Hickson
• Re: [whatwg] New HTML5 spec GIT collaboration repository Manu Sporny
• Re: [whatwg] A New Way Forward for HTML5 (revised) Manu Sporny
• Re: [whatwg] New HTML5 spec GIT collaboration repository Manu Sporny
• [Bug 7153] Want standardization of .naturalWidth and .naturalHeight, which some browsers already have bugzilla@wiggum.w3.org

Monday, 27 July 2009

• Re: Restricting maximum upload size Ian Hickson
• Re: Reasoning behind the async attribute Ian Hickson
• Re: [whatwg] New HTML5 spec GIT collaboration repository Cameron McCormack
• Re: Scripts that are in noembed or noscript containers at the time of attempted run Ian Hickson
• Re: [whatwg] A New Way Forward for HTML5 (revised) Sam Ruby
• Re: [whatwg] A New Way Forward for HTML5 (revised) Peter Kasting
• RE: [whatwg] A New Way Forward for HTML5 (revised) John Foliot
• Re: [whatwg] A New Way Forward for HTML5 (revised) Sam Ruby
• Re: [whatwg] New HTML5 spec GIT collaboration repository Geoffrey Sneddon
• New HTML5 spec GIT collaboration repository Manu Sporny
• Re: Fwd: Draft of @summary text for HTML 5 poll Joshue O Connor
• Re: [whatwg] A New Way Forward for HTML5 (revised) Sam Ruby
• Re: Media elements may never load, may load the wrong source, etc Philip Jägenstedt
• Re: Discussion: Accessibility Issues Procedure Geoffrey Sneddon
• Captions (Was: Discussion: Accessibility Issues Procedure) Ian Hickson
• Re: Discussion: Accessibility Issues Procedure Silvia Pfeiffer
• RE: Discussion: Accessibility Issues Procedure Ian Hickson
• Re: Discussion: Accessibility Issues Procedure Maciej Stachowiak
• RE: [whatwg] A New Way Forward for HTML5 (revised) John Foliot
• RE: Discussion: Accessibility Issues Procedure John Foliot
• Re: [whatwg] A New Way Forward for HTML5 (revised) Jeremy Orlow
• Re: [whatwg] A New Way Forward for HTML5 (revised) Maciej Stachowiak
• Re: [Bug 7146] New: goog Ian Hickson
• Re: [whatwg] A New Way Forward for HTML5 (revised) Manu Sporny
• Re: Discussion: Accessibility Issues Procedure Maciej Stachowiak
• [Bug 7146] goog bugzilla@wiggum.w3.org
• Re: [Bug 7146] New: goog Manu Sporny
• Re: [whatwg] A New Way Forward for HTML5 (revised) Manu Sporny
• Re: Discussion: Accessibility Issues Procedure Ian Hickson
• Re: [whatwg] A New Way Forward for HTML5 (revised) Maciej Stachowiak
• [Bug 7146] New: goog bugzilla@wiggum.w3.org
• Re: [whatwg] A New Way Forward for HTML5 (revised) Peter Kasting
• Re: [whatwg] A New Way Forward for HTML5 (revised) Manu Sporny
• Re: [whatwg] A New Way Forward for HTML5 (revised) Peter Kasting
• Re: [whatwg] A New Way Forward for HTML5 (revised) Manu Sporny

Sunday, 26 July 2009

• [Bug 7145] New: Valid date strings should accept ambiguous inputs, like "2009" or "2007-01". bugzilla@wiggum.w3.org
• Re: Discussion: Accessibility Issues Procedure Sam Ruby
• Re: Discussion: Accessibility Issues Procedure Sam Ruby
• Re: Discussion: Accessibility Issues Procedure Shelley Powers
• Re: Discussion: Accessibility Issues Procedure Sam Ruby
• Re: Discussion: Accessibility Issues Procedure Steven Faulkner
• Re: Discussion: Accessibility Issues Procedure Shelley Powers
• Re: Discussion: Accessibility Issues Procedure Sam Ruby
• Re: Non-character NCRs treated differently from literal non-characters Ian Hickson
• Re: Comments on "one vocabulary, two serializations" Maciej Stachowiak
• RE: Comments on "one vocabulary, two serializations" Larry Masinter
• Re: Comments on "one vocabulary, two serializations" Maciej Stachowiak
• Comments on "one vocabulary, two serializations" Larry Masinter
• Re: Discussion: Accessibility Issues Procedure Shelley Powers
• Re: Discussion: Accessibility Issues Procedure Ian Hickson
• Re: Media elements may never load, may load the wrong source, etc Ian Hickson
• [Bug 7140] test bugzilla@wiggum.w3.org
• Re: Discussion: Accessibility Issues Procedure Sam Ruby
• Re: Discussion: Accessibility Issues Procedure Maciej Stachowiak

Saturday, 25 July 2009

• [Bug 7144] New: I am not sure if we are ditching ALT in favour of legend. You don't make this clear here. Some of your alt examples here resemble longdesc, which I am in favour of ditching completely. I'd be interested to see your answer on whatwg list about this bugzilla@wiggum.w3.org
• [Bug 7143] New: "attributes marked with an asterisk cannot be specified on body elements" is confusing, since <body onload=""> is pretty common. Of course that's the attribute specified on a tag, but still, I'm just a simple author reading the spec for the first time :) bugzilla@wiggum.w3.org
• Re: Submitting comments form within the spec itself Doug Schepers
• Re: Submitting comments form within the spec itself Ian Hickson
• [Bug 7142] New: Shouldn't SERIALISE_ERR be SERIALIZE_ERR ? bugzilla@wiggum.w3.org
• [Bug 7141] New: Typo: "A members..." bugzilla@wiggum.w3.org
• [Bug 7140] New: test bugzilla@wiggum.w3.org
• Re: Feature Strings and Fallback for SVG (was: [svg-developers] Re: Forcing browsers to render SVG in text/html context) David Leunen
• Re: Discussion: Accessibility Issues Procedure William Loughborough
• Re: Discussion: Accessibility Issues Procedure William Loughborough
• Re: Discussion: Accessibility Issues Procedure William Loughborough
• Re: Discussion: Accessibility Issues Procedure Sam Ruby
• Re: Discussion: Accessibility Issues Procedure William Loughborough
• Re: Discussion: Accessibility Issues Procedure Maciej Stachowiak
• Re: Discussion: Accessibility Issues Procedure Ian Hickson
• Re: Discussion: Accessibility Issues Procedure William Loughborough
• Re: Submitting comments form within the spec itself Maciej Stachowiak
• Re: Submitting comments form within the spec itself Ian Hickson
• [Bug 7139] test bugzilla@wiggum.w3.org
• Re: [whatwg] "due consideration" Maciej Stachowiak
• Re: Submitting comments form within the spec itself Maciej Stachowiak
• Re: Discussion: Accessibility Issues Procedure Maciej Stachowiak
• Re: A New Way Forward for HTML5 Karl Dubost

Friday, 24 July 2009

• Re: [whatwg] A New Way Forward for HTML5 Michael Enright
• Helping Canvas Tag Be Accessible Steven Faulkner
• [Bug 7139] New: test bugzilla@wiggum.w3.org
• Submitting comments form within the spec itself Ian Hickson
• [Bug 7138] New: Need to get window.mediaMode into another spec bugzilla@wiggum.w3.org
• [Bug 7137] New: Need to fill in the references section. bugzilla@wiggum.w3.org
• Re: Draft Formal Reply (was: Draft of @summary text for HTML 5 poll) Laura Carlson
• Re: Draft Formal Reply (was: Draft of @summary text for HTML 5 poll) Shelley Powers
• Re: Microdata and Linked Data Peter Mika
• Draft Formal Reply (was: Draft of @summary text for HTML 5 poll) Sam Ruby
• Discussion: Accessibility Issues Procedure Laura Carlson
• Publishing a new draft (was: Draft of @summary text for HTML 5 poll) Sam Ruby
• Re: [whatwg] "due consideration" Anne van Kesteren
• Re: [whatwg] Microdata and Linked Data Peter Mika
• Re: Microdata and Linked Data Julian Reschke
• Re: [whatwg] Microdata and Linked Data Eduard Pascual
• Microdata and Linked Data Peter Mika
• Re: [whatwg] "due consideration" Eduard Pascual
• Re: Draft of @summary text for HTML 5 poll Maciej Stachowiak
• Re: Draft of @summary text for HTML 5 poll Julian Reschke
• Re: Draft of @summary text for HTML 5 poll Cameron McCormack
• Re: Draft of @summary text for HTML 5 poll Ian Hickson
• Re: Draft of @summary text for HTML 5 poll Laura Carlson
• Re: "due consideration" Maciej Stachowiak
• Re: [HTML5] DOMContentLoaded fires before CSS resources loaded? Maciej Stachowiak
• Re: [whatwg] A New Way Forward for HTML5 Lachlan Hunt
• Re: ISSUE-73 (Overlap of "predefined vocabularies" with other specifications), was: Concerns about new section "predefined vocabularies" Julian Reschke
• RE: [whatwg] A New Way Forward for HTML5 Justin James
• Re: [whatwg] A New Way Forward for HTML5 Manu Sporny
• Re: [whatwg] A New Way Forward for HTML5 Manu Sporny
• Re: ISSUE-73 (Overlap of "predefined vocabularies" with other specifications), was: Concerns about new section "predefined vocabularies" Ian Hickson
• Re: Draft of @summary text for HTML 5 poll Ian Hickson
• Re: Feature Strings and Fallback for SVG (was: [svg-developers] Re: Forcing browsers to render SVG in text/html context) Ian Hickson
• Re: [HTML5] DOMContentLoaded fires before CSS resources loaded? Boris Zbarsky
• "due consideration" Larry Masinter
• Feature Strings and Fallback for SVG (was: [svg-developers] Re: Forcing browsers to render SVG in text/html context) Doug Schepers
• RE: [whatwg] A New Way Forward for HTML5 John Foliot
• RE: [HTML5] DOMContentLoaded fires before CSS resources loaded? Travis Leithead
• Re: [whatwg] A New Way Forward for HTML5 Aryeh Gregor
• Re: A New Way Forward for HTML5 Sam Ruby

Thursday, 23 July 2009

• Re: Draft of @summary text for HTML 5 poll Shelley Powers
• Re: Draft of @summary text for HTML 5 poll Shelley Powers
• Re: Fwd: Draft of @summary text for HTML 5 poll Shelley Powers
• Re: Fwd: Draft of @summary text for HTML 5 poll Lachlan Hunt
• Re: [whatwg] A New Way Forward for HTML5 Peter Kasting
• Re: A New Way Forward for HTML5 Manu Sporny
• RE: ISSUE-73 (Overlap of "predefined vocabularies" with other specifications), was: Concerns about new section "predefined vocabularies" Larry Masinter
• Re: Draft of @summary text for HTML 5 poll Laura Carlson
• Re: Draft of @summary text for HTML 5 poll Maciej Stachowiak
• Re: Draft of @summary text for HTML 5 poll Laura Carlson
• Fwd: Draft of @summary text for HTML 5 poll Sam Ruby
• Re: A New Way Forward for HTML5 Sam Ruby
• Re: [whatwg] A New Way Forward for HTML5 John Drinkwater
• Re: [whatwg] A New Way Forward for HTML5 Tab Atkins Jr.
• Re: A New Way Forward for HTML5 L. David Baron
• Re: Detecting SVG-in-HTML capabilities Jeff Schiller
• Re: Detecting SVG-in-HTML capabilities Doug Schepers
• A New Way Forward for HTML5 Manu Sporny
• Re: Detecting SVG-in-HTML capabilities Jeff Schiller
• Re: Detecting SVG-in-HTML capabilities Simon Pieters
• Re: Detecting SVG-in-HTML capabilities Jeff Schiller
• Re: Detecting SVG-in-HTML capabilities Geoffrey Sneddon
• Re: PHP code only allowed in XHTML 5? Thomas Broyer
• Re: PHP code only allowed in XHTML 5? Lachlan Hunt
• Re: PHP code only allowed in XHTML 5? Thomas Broyer
• Re: ISSUE-73 (Overlap of "predefined vocabularies" with other specifications), was: Concerns about new section "predefined vocabularies" Julian Reschke
• Re: ISSUE-73 (Overlap of "predefined vocabularies" with other specifications), was: Concerns about new section "predefined vocabularies" Ian Hickson
• Re: Activation Behavior of video and audio Simon Pieters
• Activation Behavior of video and audio Doug Schepers
• Re: [HTML5] DOMContentLoaded fires before CSS resources loaded? Boris Zbarsky
• Re: [HTML5] DOMContentLoaded fires before CSS resources loaded? Boris Zbarsky
• Re: [HTML5] DOMContentLoaded fires before CSS resources loaded? Maciej Stachowiak
• [HTML5] DOMContentLoaded fires before CSS resources loaded? Travis Leithead
• Detecting SVG-in-HTML capabilities Jeff Schiller
• Re: PHP code only allowed in XHTML 5? Leif Halvard Silli
• Re: PHP code only allowed in XHTML 5? Leif Halvard Silli

Wednesday, 22 July 2009

• Re: canvas text: web fonts Robert O'Callahan
• Re: PHP code only allowed in XHTML 5? Leif Halvard Silli
• Re: PHP code only allowed in XHTML 5? Leif Halvard Silli
• Re: PHP code only allowed in XHTML 5? Thomas Broyer
• Re: PHP code only allowed in XHTML 5? Leif Halvard Silli
• Re: PHP code only allowed in XHTML 5? Leif Halvard Silli
• [Bug 7133] New: minor microdata example typo bugzilla@wiggum.w3.org
• Re: separate HTML 5 editor procedures evolving Geoffrey Sneddon
• Re: separate HTML 5 editor procedures evolving Sam Ruby
• Re: PHP code only allowed in XHTML 5? Nick Fitzsimons
• Re: Default margins for new elements Olivier GENDRIN
• Re: PHP code only allowed in XHTML 5? Olivier GENDRIN
• Re: PHP code only allowed in XHTML 5? Leif Halvard Silli
• Re: PHP code only allowed in XHTML 5? Thomas Broyer
• separate HTML 5 editor procedures evolving Shelley Powers
• Re: PHP code only allowed in XHTML 5? Leif Halvard Silli
• Re: PHP code only allowed in XHTML 5? Nick Fitzsimons
• Re: PHP code only allowed in XHTML 5? Kornel
• Re: PHP code only allowed in XHTML 5? Anne van Kesteren
• FYI: dev.w3.org/html5/spec now split into multiple pages Michael(tm) Smith
• Re: PHP code only allowed in XHTML 5? Leif Halvard Silli
• Re: PHP code only allowed in XHTML 5? Anne van Kesteren
• Re: PHP code only allowed in XHTML 5? Leif Halvard Silli
• linking other elements to a "command" Hallvord R. M. Steen
• Re: canvas text: web fonts Simon Pieters
• Re: PHP code only allowed in XHTML 5? Thomas Broyer
• @accesskey and multiple characters Hallvord R. M. Steen
• Re: PHP code only allowed in XHTML 5? Leif Halvard Silli
• Re: PHP code only allowed in XHTML 5? Leif Halvard Silli
• Re: PHP code only allowed in XHTML 5? Leif Halvard Silli
• Re: PHP code only allowed in XHTML 5? Simon Pieters
• Re: PHP code only allowed in XHTML 5? Leif Halvard Silli
• Re: PHP code only allowed in XHTML 5? Daniel Glazman
• Offer to draft HTML5 text to address WAI's accessibility technical concerns Laura Carlson
• Re: PHP code only allowed in XHTML 5? Toby A Inkster
• Re: Formal Objection to One vendor, One Veto Maciej Stachowiak
• Re: Formal Objection to One vendor, One Veto Silvia Pfeiffer
• Re: PHP code only allowed in XHTML 5? Smylers
• PHP code only allowed in XHTML 5? Leif Halvard Silli

Tuesday, 21 July 2009

• Re: Formal Objection to One vendor, One Veto David Singer
• Re: Restricting maximum upload size Alfonso Martínez de Lizarrondo
• Re: ISSUE-73 (Overlap of "predefined vocabularies" with other specifications), was: Concerns about new section "predefined vocabularies" Julian Reschke
• Re: ISSUE-73 (Overlap of "predefined vocabularies" with other specifications), was: Concerns about new section "predefined vocabularies" Ian Hickson
• Re: canvas text: web fonts Robert O'Callahan
• Re: ISSUE-73 (Overlap of "predefined vocabularies" with other specifications), was: Concerns about new section "predefined vocabularies" Julian Reschke
• Re: canvas text: web fonts Simon Pieters
• Re: ISSUE-73 (Overlap of "predefined vocabularies" with other specifications), was: Concerns about new section "predefined vocabularies" Ian Hickson
• Re: canvas text: web fonts Simon Pieters
• canvas text: line-height and getting .font Simon Pieters
• canvas text: web fonts Simon Pieters
• canvas text: ctx.font='inherit' Simon Pieters

Monday, 20 July 2009

• Re: PROPOSAL: Procedure to Promote Progress With Accessibility Issues in HTML5 Sam Ruby
• RE: PROPOSAL: Procedure to Promote Progress With Accessibility Issues in HTML5 John Foliot
• Re: PROPOSAL: Procedure to Promote Progress With Accessibility Issues in HTML5 Manu Sporny
• Re: PROPOSAL: Procedure to Promote Progress With Accessibility Issues in HTML5 Sam Ruby
• Re: PROPOSAL: Procedure to Promote Progress With Accessibility Issues in HTML5 Sam Ruby
• RE: PROPOSAL: Procedure to Promote Progress With Accessibility Issues in HTML5 John Foliot
• Re: PROPOSAL: Procedure to Promote Progress With Accessibility Issues in HTML5 Laura Carlson
• Re: PROPOSAL: Procedure to Promote Progress With Accessibility Issues in HTML5 Laura Carlson
• 4.11.6.3 Using the input element to define a command and input type=image Hallvord R. M. Steen
• Re: PROPOSAL: Procedure to Promote Progress With Accessibility Issues in HTML5 Sam Ruby
• Re: PROPOSAL: Procedure to Promote Progress With Accessibility Issues in HTML5 Joshue O Connor
• RE: [HTML5] 2.8 Character encodings Larry Masinter
• HTMLUnknownElement Geoffrey Sneddon
• Re: PROPOSAL: Procedure to Promote Progress With Accessibility Issues in HTML5 Sam Ruby
• Re: PROPOSAL: Procedure to Promote Progress With Accessibility Issues in HTML5 Ian Hickson
• Re: PROPOSAL: Procedure to Promote Progress With Accessibility Issues in HTML5 Steven Faulkner
• Re: PROPOSAL: Procedure to Promote Progress With Accessibility Issues in HTML5 Sam Ruby
• Re: PROPOSAL: Procedure to Promote Progress With Accessibility Issues in HTML5 Steven Faulkner
• RE: PROPOSAL: Procedure to Promote Progress With Accessibility Issues in HTML5 John Foliot - WATS.ca
• Re: PROPOSAL: Procedure to Promote Progress With Accessibility Issues in HTML5 Ian Hickson
• Re: PROPOSAL: Procedure to Promote Progress With Accessibility Issues in HTML5 Laura Carlson

Sunday, 19 July 2009

• Re: PROPOSAL: Procedure to Promote Progress With Accessibility Issues in HTML5 Laura Carlson
• Re: PROPOSAL: Procedure to Promote Progress With Accessibility Issues in HTML5 Ian Hickson
• Re: PROPOSAL: Procedure to Promote Progress With Accessibility Issues in HTML5 Sam Ruby
• Re: PROPOSAL: Procedure to Promote Progress With Accessibility Issues in HTML5 Laura Carlson
• Re: PROPOSAL: Procedure to Promote Progress With Accessibility Issues in HTML5 Laura Carlson
• Re: PROPOSAL: Procedure to Promote Progress With Accessibility Issues in HTML5 Sam Ruby
• Re: PROPOSAL: Procedure to Promote Progress With Accessibility Issues in HTML5 Steven Faulkner
• update on ACTION-132 Report on canvas accessibility Steven Faulkner
• RE: PROPOSAL: Procedure to Promote Progress With Accessibility Issues in HTML5 Justin James
• Re: PROPOSAL: Procedure to Promote Progress With Accessibility Issues in HTML5 Sam Ruby
• Re: PROPOSAL: Procedure to Promote Progress With Accessibility Issues in HTML5 David Poehlman
• Re: PROPOSAL: Procedure to Promote Progress With Accessibility Issues in HTML5 David Poehlman
• Re: PROPOSAL: Procedure to Promote Progress With Accessibility Issues in HTML5 Ian Hickson
• PROPOSAL: Procedure to Promote Progress With Accessibility Issues in HTML5 Laura Carlson
• Re: Date attributes on HTMLTimeElement Ian Hickson
• Editorial: obsolete attributes should be lowercase Simon Pieters
• Synonym elements (for implementors) Simon Pieters

Saturday, 18 July 2009

• Default margins for new elements Simon Pieters
• Re: comments on draft-barth-mime-sniffing Chris Double
• Re: comments on draft-barth-mime-sniffing Boris Zbarsky

Friday, 17 July 2009

• Re: comments on draft-barth-mime-sniffing Ian Hickson
• RE: Formal Objection to One vendor, One Veto Chris Wilson
• Re: Haskell and W3C specs Joe D Williams
• Re: HTML 5 parser creating multiple body elements Henri Sivonen
• Re: Haskell and W3C specs Ian Hickson
• Re: Haskell and W3C specs Joe D Williams
• Re: link/@rel=profile, was: HTML5+RDFa first Editors Draft published Leif Halvard Silli
• Re: Does anyone like microdata? Ian Hickson
• Re: Formal Objection to One vendor, One Veto Silvia Pfeiffer

Thursday, 16 July 2009

• RE: Formal Objection to One vendor, One Veto Chris Wilson
• Re: Request for advice on <canvas> accessibility Ian Hickson
• Re: Haskell and W3C specs Ian Hickson
• Re: link/@rel=profile, was: HTML5+RDFa first Editors Draft published Murray Maloney
• Re: link/@rel=profile, was: HTML5+RDFa first Editors Draft published Mark Birbeck
• Re: Avoiding table less (Div based) HTML pages from CSS dependencies. Charles McCathieNevile
• Re: link/@rel=profile, was: HTML5+RDFa first Editors Draft published Steven Pemberton
• Re: HTML 5 parser creating multiple body elements Geoffrey Sneddon
• RE: Formal Objection to One vendor, One Veto Chris Wilson
• Re: Restricting maximum upload size Charles McCathieNevile
• Re: Request for advice on <canvas> accessibility Charles McCathieNevile
• Re: HTML 5 parser creating multiple body elements Thomas Broyer
• Re: Haskell and W3C specs Dimitry Golubovsky
• HTML 5 parser creating multiple body elements Geoffrey Sneddon
• spellcheck DOM attribute sets content attributes to states, leaving case undefined Geoffrey Sneddon
• Don't reopen active formatting elements for whitespace Simon Pieters
• Re: document.write from script-inserted external script Henri Sivonen
• Re: ISSUE-73 (Overlap of "predefined vocabularies" with other specifications), was: Concerns about new section "predefined vocabularies" Jonas Sicking
• Re: ISSUE-73 (Overlap of "predefined vocabularies" with other specifications), was: Concerns about new section "predefined vocabularies" Maciej Stachowiak
• Re: ISSUE-73 (Overlap of "predefined vocabularies" with other specifications), was: Concerns about new section "predefined vocabularies" Ian Hickson
• Re: ISSUE-73 (Overlap of "predefined vocabularies" with other specifications), was: Concerns about new section "predefined vocabularies" James Graham
• Re: ISSUE-73 (Overlap of "predefined vocabularies" with other specifications), was: Concerns about new section "predefined vocabularies" Julian Reschke
• Re: ISSUE-73 (Overlap of "predefined vocabularies" with other specifications), was: Concerns about new section "predefined vocabularies" Ian Hickson
• Last Call: draft-nottingham-http-link-header (Web Linking) to Proposed Standard Julian Reschke
• Re: Proposal: @parsing="loose | strict" Boris Zbarsky
• RE: Request to include missing HTML tag interface specs in html5.idl Ian Hickson
• Re: Formal Objection to One vendor, One Veto Silvia Pfeiffer
• RE: Request to include missing HTML tag interface specs in html5.idl Travis Leithead
• Re: Image maps: <a coords=""> - a new look Leif Halvard Silli
• Image maps: <a coords=""> - a new look Leif Halvard Silli
• Re: Haskell and W3C specs Ian Hickson
• Haskell and W3C specs Dimitry Golubovsky

Wednesday, 15 July 2009

• Re: Proposal: @parsing="loose | strict" Leif Halvard Silli
• RE: Formal Objection to One vendor, One Veto Chris Wilson
• Re: Request to include missing HTML tag interface specs in html5.idl Maciej Stachowiak
• Re: Request to include missing HTML tag interface specs in html5.idl Ian Hickson
• Re: Editorial: issues with the PDF version Ian Hickson
• Re: <input type="number"> restricting user input to only valid characters Ian Hickson
• Re: Request to include missing HTML tag interface specs in html5.idl Dimitry Golubovsky
• RE: Request to include missing HTML tag interface specs in html5.idl Travis Leithead
• Re: Editorial: issues with the PDF version Simon Pieters
• Request to include missing HTML tag interface specs in html5.idl Dimitry Golubovsky
• Re: <input type="number"> restricting user input to only valid characters Michael A. Puls II
• Re: Scripts that are in noembed or noscript containers at the time of attempted run Simon Pieters
• Re: WAI-CG Consensus Recommendations on Alternative Text in HTML 5 Henri Sivonen
• Re: <input type="number"> restricting user input to only valid characters Ian Hickson
• Re: ISSUE-73 (Overlap of "predefined vocabularies" with other specifications), was: Concerns about new section "predefined vocabularies" James Graham
• [Bug 6746] case-insensitivity of other than a-z and A-Z, e.g., diacritics bugzilla@wiggum.w3.org
• Re: Editorial: maybe redundant definition on sectioning content Ian Hickson
• Re: Rendering: border on table Simon Pieters
• Re: <input type="number"> restricting user input to only valid characters Michael A. Puls II
• re: HTML5 Microdata feedback/questions Oli
• Re: document.bgColor and frameset Ian Hickson
• Re: Rendering: border on table Ian Hickson
• Re: ch/chOff should be char/charoff Ian Hickson
• Re: Formal Objection to One vendor, One Veto Silvia Pfeiffer
• Re: Advice about framesets Ian Hickson
• Re: command Label and <img alt> Ian Hickson
• Re: {agenda} HTML WG telcon 2009-07-16 David Singer
• Re: Formal Objection to One vendor, One Veto David Singer
• [Bug 7105] New: Default fallback behaviour for unsupported tags in browsers! bugzilla@wiggum.w3.org
• Re: Formal Objection to One vendor, One Veto Silvia Pfeiffer
• RE: (HTML5 Parsing) Yet another corner-case: parsing into other contexts... Ian Hickson
• Re: Formal Objection to One vendor, One Veto Shelley Powers
• {agenda} HTML WG telcon 2009-07-16 Chris Wilson

Tuesday, 14 July 2009

• RE: Formal Objection to One vendor, One Veto Chris Wilson
• Re: <input type="number"> restricting user input to only valid characters Ian Hickson
• Re: Proposal: @parsing="loose | strict" Boris Zbarsky
• Re: Proposal: @parsing="loose | strict" Dan Connolly
• Re: equals sign in unquoted attribute Simon Pieters
• Re: Proposal: @parsing="loose | strict" Leif Halvard Silli
• Re: Proposal: @parsing="loose | strict" Leif Halvard Silli
• Re: equals sign in unquoted attribute Lachlan Hunt
• Normative warnings (was: Re: ACTION-128: Draft @summary voting text in conjunction with PF) Henri Sivonen
• Re: Proposal: @parsing="loose | strict" Lachlan Hunt
• Re: postMessage: origin serialized too early Thomas Roessler
• Re: Proposal: @parsing="loose | strict" Leif Halvard Silli
• Re: Proposal: @parsing="loose | strict" Lachlan Hunt
• Re: Proposal: @parsing="loose | strict" Leif Halvard Silli
• [Bug 7103] New: Content-Language marked as non-conforming bugzilla@wiggum.w3.org
• [Bug 7102] New: Permitted obsolete doctype compare "HTML" bugzilla@wiggum.w3.org
• Re: several messages Simon Pieters
• Re: Proposal: @parsing="loose | strict" Kornel
• Re: link/@rel=profile, was: HTML5+RDFa first Editors Draft published Mark Birbeck
• Re: event.currentTarget and 'this' for listeners registered on the window object Michael A. Puls II
• Re: Proposal: @parsing="loose | strict" Julian Reschke
• Re: <input type="number"> restricting user input to only valid characters Michael A. Puls II
• Re: Proposal: @parsing="loose | strict" Maciej Stachowiak
• Re: Proposal: @parsing="loose | strict" Michael A. Puls II
• Re: Proposal: @parsing="loose | strict" Julian Reschke
• Re: Proposal: @parsing="loose | strict" Maciej Stachowiak
• Re: Proposal: @parsing="loose | strict" Boris Zbarsky
• Re: typeof document.all Ian Hickson
• Proposal: @parsing="loose | strict" Doug Schepers
• Re: document.write from script-inserted external script Henri Sivonen
• link/@rel=profile, was: HTML5+RDFa first Editors Draft published Julian Reschke
• Re: several messages Ian Hickson
• Re: typeof document.all Boris Zbarsky
• Re: event.currentTarget and 'this' for listeners registered on the window object Ian Hickson
• Re: change "scientific documents" to "basic hypertext" (detailed review of section 1. Introduction) Ian Hickson
• Re: <input type="number"> restricting user input to only valid characters Ian Hickson
• Re: typeof document.all Ian Hickson
• Re: equals sign in unquoted attribute Ian Hickson

Monday, 13 July 2009

• Re: Formal Objection to One vendor, One Veto Shelley Powers
• RE: document.write from script-inserted external script Travis Leithead
• FW: New Version Notification for draft-duerst-iri-bis-06 Larry Masinter
• Re: <audio> and <video> Support - formal objection to one vendor/one vote Joe D Williams
• Re: formal objection to one vendor/one vote Joe D Williams
• HTML5+RDFa first Editors Draft published Manu Sporny
• Re: formal objection to one vendor/one vote David Singer
• Re: formal objection to one vendor/one vote Sam Ruby
• Re: formal objection to one vendor/one vote David Singer
• Re: formal objection to one vendor/one vote Sam Ruby
• document.write from script-inserted external script Henri Sivonen
• Re: formal objection to one vendor/one vote David Singer
• Re: formal objection to one vendor/one vote Sam Ruby
• Re: <nav> Element Ian Hickson
• Re: formal objection to one vendor/one vote Steven Faulkner
• Re: Editorial: issues with the PDF version Ian Hickson
• Re: &foo= in attribute values (and why defining conformance matters) Ian Hickson
• Re: formal objection to one vendor/one vote David Singer
• Re: accesskey feedback Ian Hickson
• Re: Editorial: issues with the PDF version Simon Pieters
• Re: &foo= in attribute values (and why defining conformance matters) Simon Pieters
• Re: DOM tree accessors Ian Hickson
• Avoiding table less (Div based) HTML pages from CSS dependencies. Shivananda M.K.
• Re: formal objection to one vendor/one vote David Singer
• Re: formal objection to one vendor/one vote Rob Sayre
• Re: Editorial: issues with the PDF version Ian Hickson

Sunday, 12 July 2009

• Re: formal objection to one vendor/one vote Joe D Williams
• Re: formal objection to one vendor/one vote Benoit Piette

Saturday, 11 July 2009

• Re: formal objection to one vendor/one vote Ian Hickson
• Re: formal objection to one vendor/one vote Sam Ruby
• Re: Restricting maximum upload size Alfonso Martínez de Lizarrondo
• Re: Restricting maximum upload size John Drinkwater
• Restricting maximum upload size Alfonso Martínez de Lizarrondo
• Re: Request for advice on <canvas> accessibility Steven Faulkner
• Re: Request for advice on <canvas> accessibility Steven Faulkner
• Re: &foo= in attribute values (and why defining conformance matters) Ian Hickson

Friday, 10 July 2009

• Re: postMessage: origin serialized too early Ian Hickson
• Re: Clarification on "live NodeList" Andrew Fedoniouk
• Re: Clarification on "live NodeList" Boris Zbarsky
• Re: Clarification on "live NodeList" Andrew Fedoniouk
• Re: Auto-detect and encodings in HTML5 Ian Hickson
• RE: Request for advice on <canvas> accessibility Ian Hickson
• Re: Clarification on "live NodeList" Philip Taylor
• Re: Clarification on "live NodeList" Boris Zbarsky
• Re: Clarification on "live NodeList" Andrew Fedoniouk
• Re: another example of HTMl 5 canvas with interactive UI elements. Jonas Sicking
• Re: Scripts that are in noembed or noscript containers at the time of attempted run Jonas Sicking
• Re: another example of HTMl 5 canvas with interactive UI elements. Robin Berjon
• Re: WAI-CG Consensus Recommendations on Alternative Text in HTML 5 Jan Richards
• Re: another example of HTMl 5 canvas with interactive UI elements. Henri Sivonen
• Reasoning behind the async attribute Henri Sivonen
• Re: WAI-CG Consensus Recommendations on Alternative Text in HTML 5 Henri Sivonen
• RE: Request for advice on <canvas> accessibility Steve Faulkner
• Re: another example of HTMl 5 canvas with interactive UI elements. Robin Berjon
• Re: another example of HTMl 5 canvas with interactive UI elements. Joshue O Connor
• Re: another example of HTMl 5 canvas with interactive UI elements. Steven Faulkner
• Re: another example of HTMl 5 canvas with interactive UI elements. Lachlan Hunt
• Scripts that are in noembed or noscript containers at the time of attempted run Henri Sivonen
• Re: another example of HTMl 5 canvas with interactive UI elements. Joshue O Connor
• Re: .spellcheck = 'inherit' should work Ian Hickson
• RE: Running "Zombie" Script Elements Travis Leithead
• Re: Running "Zombie" Script Elements Ian Hickson
• Re: formal objection to one vendor/one vote (and group decision process for, e.g. ISSUE-7 video-codecs) Shelley Powers
• Re: Foster-parenting and taint Ian Hickson

Thursday, 9 July 2009

• RE: another example of HTML 5 canvas with interactive UI elements. John Foliot
• Re: Request for advice on <canvas> accessibility Ian Hickson
• Re: another example of HTMl 5 canvas with interactive UI elements. Lachlan Hunt
• Re: another example of HTMl 5 canvas with interactive UI elements. Joshue O Connor
• Re: another example of HTMl 5 canvas with interactive UI elements. Lachlan Hunt
• Re: another example of HTMl 5 canvas with interactive UI elements. Jonas Sicking
• minutes HTML weekly 9 July for review Dan Connolly
• Re: another example of HTMl 5 canvas with interactive UI elements. Steven Faulkner
• Re: another example of HTMl 5 canvas with interactive UI elements. Maciej Stachowiak
• Re: proposed audio/video codec text Rob Sayre
• Re: proposed audio/video codec text Robin Berjon
• Re: formal objection to one vendor/one vote (and group decision process for, e.g. ISSUE-7 video-codecs) Dan Connolly
• Re: PF Response: @Summary Stephen Stewart
• Re: another example of HTMl 5 canvas with interactive UI elements. Dan Connolly
• another example of HTMl 5 canvas with interactive UI elements. Steven Faulkner
• Re: Non-character NCRs treated differently from literal non-characters Henri Sivonen
• Re: ACTION-128: Draft @summary voting text in conjunction with PF Joshue O Connor
• Re: ACTION-128: Draft @summary voting text in conjunction with PF Murray Maloney

Wednesday, 8 July 2009

• Re: Codecs for <video> and <audio> Maciej Stachowiak
• Re: ACTION-128: Draft @summary voting text in conjunction with PF Maciej Stachowiak
• Re: Codecs for <video> and <audio> Nikunj R. Mehta

Thursday, 9 July 2009

• Re: Codecs for <video> and <audio> Murray Maloney

Wednesday, 8 July 2009

• Re: ACTION-128: Draft @summary voting text in conjunction with PF Ian Hickson
• Re: ACTION-128: Draft @summary voting text in conjunction with PF Maciej Stachowiak
• Re: proposed audio/video codec text Maciej Stachowiak
• RE: formal objection to one vendor/one vote John Foliot
• Re: proposed audio/video codec text Rob Sayre
• Re: proposed audio/video codec text Maciej Stachowiak
• Re: ACTION-128: Draft @summary voting text in conjunction with PF Ian Hickson
• Re: ACTION-128: Draft @summary voting text in conjunction with PF Maciej Stachowiak
• Re: proposed audio/video codec text Rob Sayre
• Re: ACTION-128: Draft @summary voting text in conjunction with PF Maciej Stachowiak
• Re: proposed audio/video codec text Maciej Stachowiak
• Re: Codecs for <video> and <audio> Maciej Stachowiak
• Re: ACTION-128: Draft @summary voting text in conjunction with PF Joshue O Connor
• Re: ACTION-128: Draft @summary voting text in conjunction with PF Sam Ruby
• Re: Codecs for <video> and <audio> James Graham
• Re: formal objection to one vendor/one vote Joe D Williams
• Re: ACTION-128: Draft @summary voting text in conjunction with PF Ian Hickson
• Re: ACTION-128: Draft @summary voting text in conjunction with PF Ian Hickson
• Re: ACTION-128: Draft @summary voting text in conjunction with PF Ian Hickson
• Re: Codecs for <video> and <audio> Nikunj R. Mehta
• Re: Codecs for <video> and <audio> Jonas Sicking
• Re: PF Response: @Summary Jim Jewett
• RE: ACTION-128: Draft @summary voting text in conjunction with PF John Foliot
• Re: proposed audio/video codec text Shelley Powers
• RE: PF Response: @Summary John Foliot
• Re: ACTION-128: Draft @summary voting text in conjunction with PF James Graham
• Re: formal objection to one vendor/one vote Shelley Powers
• Re: formal objection to one vendor/one vote Shelley Powers
• Re: PF Response: @Summary Gez Lemon
• Re: formal objection to one vendor/one vote Julian Reschke
• Re: ACTION-128: Draft @summary voting text in conjunction with PF Joshue O Connor
• Re: formal objection to one vendor/one vote David Singer
• Re: PF Response: @Summary Lachlan Hunt
• Re: proposed audio/video codec text Rob Sayre
• Re: PF Response: @Summary Janina Sajka
• Re: ACTION-128: Draft @summary voting text in conjunction with PF Lachlan Hunt
• Re: ACTION-128: Draft @summary voting text in conjunction with PF Shelley Powers
• Re: How to make complex data tables more accessible to screen-reader users Shelley Powers
• formal objection to one vendor/one vote Shelley Powers
• Re: ACTION-128: Draft @summary voting text in conjunction with PF Steven Faulkner
• Re: ACTION-128: Draft @summary voting text in conjunction with PF Sam Ruby
• Re: ACTION-128: Draft @summary voting text in conjunction with PF Sam Ruby
• Re: PF Response: @Summary Henri Sivonen
• Re: ACTION-128: Draft @summary voting text in conjunction with PF James Graham
• Re: ACTION-128: Draft @summary voting text in conjunction with PF Steven Faulkner
• Re: ACTION-128: Draft @summary voting text in conjunction with PF Julian Reschke
• Re: ACTION-128: Draft @summary voting text in conjunction with PF William Loughborough
• Re: PF Response: @Summary Joshue O Connor
• Re: Media elements may never load, may load the wrong source, etc Philip Jagenstedt
• Re: ACTION-128: Draft @summary voting text in conjunction with PF Maciej Stachowiak
• Re: ACTION-128: Draft @summary voting text in conjunction with PF Ian Hickson
• [Bug 7089] New: CDATA escapes need to close upon --\s*!> bugzilla@wiggum.w3.org
• Re: ACTION-128: Draft @summary voting text in conjunction with PF Ian Hickson
• Re: Codecs for <video> and <audio> Ian Hickson
• Re: Clarification on "live NodeList" Boris Zbarsky
• Re: ACTION-128: Draft @summary voting text in conjunction with PF Maciej Stachowiak
• Re: ACTION-128: Draft @summary voting text in conjunction with PF Henri Sivonen
• Re: ISSUE-73 (Overlap of "predefined vocabularies" with other specifications), was: Concerns about new section "predefined vocabularies" Julian Reschke
• Re: Codecs for <video> and <audio> Julian Reschke
• Re: Clarification on "live NodeList" Andrew Fedoniouk
• Re: Clarification on "live NodeList" Maciej Stachowiak
• Re: Clarification on "live NodeList" Boris Zbarsky
• Re: Clarification on "live NodeList" Andrew Fedoniouk
• Re: Clarification on "live NodeList" Jeff Schiller
• RE: How to make complex data tables more accessible to screen-reader users Justin James
• Re: Clarification on "live NodeList" Maciej Stachowiak
• Clarification on "live NodeList" Jeff Schiller
• Re: <frameset onload> Ian Hickson
• Re: canvas: globalAlpha should not throw Ian Hickson
• RE: ACTION-128: Draft @summary voting text in conjunction with PF John Foliot
• RE: ACTION-128: Draft @summary voting text in conjunction with PF John Foliot
• Re: ISSUE-73 (Overlap of "predefined vocabularies" with other specifications), was: Concerns about new section "predefined vocabularies" Ian Hickson
• Re: proposed audio/video codec text Maciej Stachowiak
• Re: Media elements may never load, may load the wrong source, etc Ian Hickson
• Re: Non-character NCRs treated differently from literal non-characters Ian Hickson
• Re: Rendering: contenteditable Ian Hickson
• Re: proposed audio/video codec text Rob Sayre
• Re: The a element (content and semantic model) Ian Hickson

Tuesday, 7 July 2009

• Re: getElementsByName should match any element Ian Hickson
• Re: proposed audio/video codec text Maciej Stachowiak
• Re: Codecs for <video> and <audio> Shelley Powers
• Re: PF Response: @Summary Sam Ruby
• Re: Codecs for <video> and <audio> Ian Hickson
• Re: PF Response: @Summary Jim Jewett
• proposed audio/video codec text Rob Sayre
• Re: PF Response: @Summary Shelley Powers
• Re: Codecs for <video> and <audio> Shelley Powers
• Re: Codecs for <video> and <audio> Ian Hickson
• Re: Codecs for <video> and <audio> Rob Sayre
• Re: PF Response: @Summary Ian Hickson
• Re: PF Response: @Summary Gez Lemon
• Re: PF Response: @Summary Janina Sajka
• Re: PF Response: @Summary Ian Hickson
• Re: PF Response: @Summary Janina Sajka
• Re: Codecs for <video> and <audio> Ian Hickson
• Re: ACTION-128: Draft @summary voting text in conjunction with PF Ian Hickson
• Re: PF Response: @Summary Ian Hickson
• Re: PF Response: @Summary David Poehlman
• Re: PF Response: @Summary Ian Hickson
• Re: PF Response: @Summary Jim Jewett
• Re: PF Response: @Summary Jim Jewett
• Re: PF Response: @Summary Joshue O Connor
• Re: Request to Strengthen the HTML5 Accessibility Design Principle Laura Carlson
• [Bug 7086] New: <a> should be </a> in section 4.5.3 of the HTML5 specification bugzilla@wiggum.w3.org
• Re: level of support for microdata (was Re: Why I don't attend the weekly teleconference) Shelley Powers
• [Fwd: [whatwg] Codecs for <audio> and <video>] Doug Schepers
• level of support for microdata (was Re: Why I don't attend the weekly teleconference) Edward O'Connor
• Re: Why I don't attend the weekly teleconference (Was: Input on the agenda) (fwd) Shelley Powers
• Re: PF Response: @Summary Janina Sajka
• Re: Codecs for <video> and <audio> Shelley Powers
• Re: PF Response: @Summary David Poehlman
• Re: PF Response: @Summary Joshue O Connor
• Re: PF Response: @Summary Henri Sivonen
• Re: Why I don't attend the weekly teleconference (Was: Input on the agenda) (fwd) Ian Hickson
• [Bug 7084] New: <ul><li>A<iul></l>B is parsed backwards-incompatibly bugzilla@wiggum.w3.org
• Re: ACTION-128: Draft @summary voting text in conjunction with PF Sam Ruby
• Re: Codecs for <video> and <audio> Robin Berjon
• Re: ACTION-128: Draft @summary voting text in conjunction with PF Joshue O Connor
• Re: <video> toggling video rendering (and muting of <video hidden>) Ian Hickson
• RE: PF Response: @Summary Schnabel, Stefan
• Re: ACTION-128: Draft @summary voting text in conjunction with PF Murray Maloney
• Re: Codecs for <video> and <audio> Ian Hickson
• Re: Codecs for <video> and <audio> Jonas Sicking
• Re: ACTION-128: Draft @summary voting text in conjunction with PF Ian Hickson
• Re: ACTION-128: Draft @summary voting text in conjunction with PF Maciej Stachowiak
• Re: Codecs for <video> and <audio> Ian Hickson
• Re: Codecs for <video> and <audio> Jonas Sicking

Monday, 6 July 2009

• Re: Codecs for <video> and <audio> Silvia Pfeiffer

Tuesday, 7 July 2009

• Re: ACTION-128: Draft @summary voting text in conjunction with PF Murray Maloney

Monday, 6 July 2009

• Re: ACTION-128: Draft @summary voting text in conjunction with PF Ian Hickson
• Re: Codecs for <video> and <audio> Ian Hickson
• Re: ACTION-128: Draft @summary voting text in conjunction with PF Maciej Stachowiak
• Re: Codecs for <video> and <audio> Silvia Pfeiffer
• Re: Codecs for <video> and <audio> Ian Hickson
• Re: Codecs for <video> and <audio> Jonas Sicking
• Re: Codecs for <video> and <audio> Håkon Wium Lie
• Re: Codecs for <video> and <audio> Ian Hickson
• Re: ACTION-128: Draft @summary voting text in conjunction with PF Shelley Powers
• Re: ACTION-128: Draft @summary voting text in conjunction with PF Shelley Powers
• Re: How to make complex data tables more accessible to screen-reader users Shelley Powers
• Re: How to make complex data tables more accessible to screen-reader users Shelley Powers
• Re: ACTION-128: Draft @summary voting text in conjunction with PF Ian Hickson
• Re: ACTION-128: Draft @summary voting text in conjunction with PF Ian Hickson
• Re: ACTION-128: Draft @summary voting text in conjunction with PF Ian Hickson
• RE: How to make complex data tables more accessible to screen-reader users Justin James
• Re: PF Response: @Summary Janina Sajka
• Re: How to make complex data tables more accessible to screen-reader users Shelley Powers
• Re: How to make complex data tables more accessible to screen-reader users Sam Ruby
• RE: How to make complex data tables more accessible to screen-reader users Justin James
• Re: PF Response: @Summary Joshue O Connor
• Re: How to make complex data tables more accessible to screen-reader users Shelley Powers
• Re: PF Response: @Summary Jim Jewett
• Re: How to make complex data tables more accessible to screen-reader users Lachlan Hunt
• Re: How to make complex data tables more accessible to screen-reader users Shelley Powers
• Re: How to make complex data tables more accessible to screen-reader users Lachlan Hunt
• Re: How to make complex data tables more accessible to screen-reader users Shelley Powers
• Re: How to make complex data tables more accessible to screen-reader users Shelley Powers
• Re: How to make complex data tables more accessible to screen-reader users Julian Reschke
• Re: How to make complex data tables more accessible to screen-reader users Lachlan Hunt
• Re: Codecs for <video> and <audio> Robin Berjon
• Re: Codecs for <video> and <audio> Håkon Wium Lie
• Re: How to make complex data tables more accessible to screen-reader users Steven Faulkner
• Re: Codecs for <video> and <audio> Jonas Sicking
• Re: How to make complex data tables more accessible to screen-reader users Sam Ruby
• Re: ACTION-128: Draft @summary voting text in conjunction with PF Joshue O Connor
• Re: ACTION-128: Draft @summary voting text in conjunction with PF Joshue O Connor
• Re: ACTION-128: Draft @summary voting text in conjunction with PF David Poehlman
• Re: PF Response: @Summary David Poehlman
• Re: How to make complex data tables more accessible to screen-reader users James Graham
• Re: How to make complex data tables more accessible to screen-reader users Ian Hickson
• Re: PF Response: @Summary Joshue O Connor
• Re: How to make complex data tables more accessible to screen-reader users Lachlan Hunt
• Re: How to make complex data tables more accessible to screen-reader users Ian Hickson
• Re: ACTION-128: Draft @summary voting text in conjunction with PF Maciej Stachowiak
• Re: How to make complex data tables more accessible to screen-reader users Sam Ruby
• ACTION-128: Draft @summary voting text in conjunction with PF Ian Hickson
• Re: How to make complex data tables more accessible to screen-reader users Ian Hickson
• Re: How to make complex data tables more accessible to screen-reader users Ian Hickson
• Re: How to make complex data tables more accessible to screen-reader users Ian Hickson
• Re: PF Response: @Summary Jim Jewett
• Re: How to make complex data tables more accessible to screen-reader users Sam Ruby
• RE: Packaging resources in HTML files Yaron Golan
• Re: How to make complex data tables more accessible to screen-reader users Maciej Stachowiak
• RE: Packaging resources in HTML files Yaron Golan
• Re: How to make complex data tables more accessible to screen-reader users Sam Ruby

Sunday, 5 July 2009

• Re: Codecs for <video> and <audio> Ian Hickson
• Re: Packaging resources in HTML files Robert O'Callahan
• Re: Codecs for <video> and <audio> Robert O'Callahan
• Re: How to make complex data tables more accessible to screen-reader users Maciej Stachowiak
• Re: How to make complex data tables more accessible to screen-reader users Sam Ruby
• RE: Packaging resources in HTML files Justin James
• Re: How to make complex data tables more accessible to screen-reader users Murray Maloney
• Re: How to make complex data tables more accessible to screen-reader users Ian Hickson

Saturday, 4 July 2009

• Packaging resources in HTML files Yaron Golan

Friday, 3 July 2009

• Can asp.net master page be a part of HTML 5? Gulshanur Rahman

Sunday, 5 July 2009

• Re: How to make complex data tables more accessible to screen-reader users Sam Ruby
• [Bug 7080] New: Grammatical error in DOM trees section bugzilla@wiggum.w3.org
• [Bug 7079] New: Inconsistency in algorithm descriptions for parsing integers bugzilla@wiggum.w3.org
• Re: How to make complex data tables more accessible to screen-reader users Shelley Powers
• Re: How to make complex data tables more accessible to screen-reader users Shelley Powers
• [Bug 7076] Client-side image maps attributes missing on the a element bugzilla@wiggum.w3.org
• [Bug 7076] Client-side image maps attributes missing on the a element bugzilla@wiggum.w3.org
• Re: How to make complex data tables more accessible to screen-reader users Lachlan Hunt
• How to make complex data tables more accessible to screen-reader users Ian Hickson
• [Bug 7076] Client-side image maps attributes missing on the a element bugzilla@wiggum.w3.org

Saturday, 4 July 2009

• Re: Codecs for <audio> and <video> Robert Sayre
• Re: Codecs for <audio> and <video> Ian Hickson
• Re: Codecs for <video> and <audio> Ian Hickson
• Re: Codecs for <video> and <audio> Sam Ruby
• Re: Codecs for <audio> and <video> Silvia Pfeiffer
• Re: Accessibility, disability, all and some Re: Request to Strengthen the HTML5 Accessibility Design Principle Charles McCathieNevile
• Re: Codecs for <video> and <audio> Maciej Stachowiak
• Re: Codecs for <video> and <audio> Sam Ruby
• Microsoft web video Kristof Zelechovski
• Re: Shifting gears for a second (was RE: Codecs for <video> and <audio>) Matthew Ratzloff
• Captions (was Re: Shifting gears for a second (was RE: Codecs for <video> and <audio>)) Silvia Pfeiffer
• Re: ssh key (Was: Why I don't attend the weekly teleconference (Was: Input on the agenda)) Robert Sayre
• Re: Shifting gears for a second (was RE: Codecs for <video> and <audio>) Maciej Stachowiak
• Re: Shifting gears for a second (was RE: Codecs for <video> and <audio>) Matthew Ratzloff

Friday, 3 July 2009

• Re: ssh key (Was: Why I don't attend the weekly teleconference (Was: Input on the agenda)) Shelley Powers
• Re: [Bug 7075] New: The embed element should be deprecated Joe D Williams
• Re: Codecs for <video> and <audio> Doug Schepers
• Re: ssh key (Was: Why I don't attend the weekly teleconference (Was: Input on the agenda)) Rob Sayre
• Re: [Bug 7075] New: The embed element should be deprecated Joe D Williams
• [Bug 7076] New: Client-side image maps attributes missing on the a element bugzilla@wiggum.w3.org
• Re: Codecs for <video> and <audio> Rob Sayre
• Re: Codecs for <video> and <audio> Shelley Powers
• Re: Codecs for <video> and <audio> David Singer
• Re: Codecs for <video> and <audio> David Singer
• Re: ssh key (Was: Why I don't attend the weekly teleconference (Was: Input on the agenda)) Shelley Powers
• Re: Nothing is really hidden Lee Kowalkowski
• Re: Shifting gears for a second (was RE: Codecs for <video> and <audio>) Silvia Pfeiffer
• Re: Codecs for <video> and <audio> Ian Hickson
• Re: Shifting gears for a second (was RE: Codecs for <video> and <audio>) Maciej Stachowiak
• Re: Codecs for <video> and <audio> Sam Ruby
• Re: Shifting gears for a second (was RE: Codecs for <video> and <audio>) Ian Hickson
• [Bug 7075] New: The embed element should be deprecated bugzilla@wiggum.w3.org
• Re: Shifting gears for a second (was RE: Codecs for <video> and <audio>) Chris Double
• Re: Nothing is really hidden Lee Kowalkowski
• Re: Shifting gears for a second (was RE: Codecs for <video> and <audio>) Silvia Pfeiffer
• Re: Codecs for <video> and <audio> Ian Hickson
• Re: Codecs for <video> and <audio> Philip Jägenstedt
• Re: Codecs for <video> and <audio> Henri Sivonen
• Re: Codecs for <video> and <audio> Robert O'Callahan
• Re: Shifting gears for a second (was RE: Codecs for <video> and <audio>) David Singer
• Re: Codecs for <video> and <audio> Ian Hickson
• Re: Codecs for <video> and <audio> Doug Schepers
• Re: Shifting gears for a second (was RE: Codecs for <video> and <audio>) Ian Hickson
• Date attributes on HTMLTimeElement Cameron McCormack
• Re: Codecs for <video> and <audio> Ian Hickson
• Re: Shifting gears for a second (was RE: Codecs for <video> and <audio>) Maciej Stachowiak
• Re: Codecs for <video> and <audio> Ian Hickson
• Re: Codecs for <video> and <audio> Ian Hickson
• Re: Codecs for <video> and <audio> Robert O'Callahan
• Re: Codecs for <video> and <audio> Jonas Sicking
• Re: Codecs for <video> and <audio> Silvia Pfeiffer
• Re: Codecs for <video> and <audio> Rob Sayre
• Re: Shifting gears for a second (was RE: Codecs for <video> and <audio>) Silvia Pfeiffer
• Re: Codecs for <video> and <audio> Maciej Stachowiak
• Re: Shifting gears for a second (was RE: Codecs for <video> and <audio>) Maciej Stachowiak
• Re: Codecs for <video> and <audio> Jonas Sicking
• Shifting gears for a second (was RE: Codecs for <video> and <audio>) John Foliot
• Re: Codecs for <video> and <audio> Maciej Stachowiak
• Re: Codecs for <video> and <audio> Silvia Pfeiffer
• Re: Codecs for <video> and <audio> Chris Double
• Re: Codecs for <video> and <audio> Rob Sayre
• Re: Codecs for <video> and <audio> Rob Sayre
• Re: Codecs for <video> and <audio> Maciej Stachowiak
• Re: Codecs for <video> and <audio> Doug Schepers
• Re: Codecs for <video> and <audio> Silvia Pfeiffer
• Re: Codecs for <video> and <audio> Doug Schepers
• Re: Codecs for <video> and <audio> Maciej Stachowiak
• Re: Codecs for <video> and <audio> Rob Sayre
• Re: Codecs for <video> and <audio> Maciej Stachowiak
• Re: Codecs for <video> and <audio> Robert O'Callahan
• Re: Codecs for <video> and <audio> Joe D Williams
• Re: Codecs for <video> and <audio> Sam Ruby
• Re: Codecs for <video> and <audio> Jonas Sicking
• Re: Codecs for <video> and <audio> Doug Schepers
• Re: Codecs for <video> and <audio> Sam Ruby
• Re: Codecs for <video> and <audio> Silvia Pfeiffer
• Re: Codecs for <video> and <audio> Ian Hickson
• Re: Codecs for <video> and <audio> Rob Sayre

Thursday, 2 July 2009

• Re: Codecs for <video> and <audio> Maciej Stachowiak
• Re: Codecs for <video> and <audio> Rob Sayre
• Re: Codecs for <video> and <audio> Robert O'Callahan
• Re: Codecs for <video> and <audio> Doug Schepers
• Re: Codecs for <video> and <audio> Maciej Stachowiak
• Re: Codecs for <video> and <audio> Doug Schepers
• Re: Codecs for <video> and <audio> Maciej Stachowiak
• Re: Codecs for <video> and <audio> Rob Sayre
• Re: Codecs for <video> and <audio> Doug Schepers
• Re: Codecs for <video> and <audio> Ian Hickson
• Re: Codecs for <video> and <audio> Jonas Sicking
• Re: Codecs for <video> and <audio> Maciej Stachowiak
• Re: Codecs for <video> and <audio> Doug Schepers
• Re: Codecs for <video> and <audio> Doug Schepers
• Re: Nothing is really hidden Shelley Powers
• Re: Safe ways of implementing limits on buffer sizes in the parser Ian Hickson
• RE: Nothing is really hidden Justin James
• Re: Nothing is really hidden Shelley Powers
• Re: Nothing is really hidden Jonas Sicking
• Re: consensus (was: Codecs for <video> and <audio>) Michael A. Puls II
• Re: Nothing is really hidden David Singer
• Re: Nothing is really hidden Shelley Powers
• Re: Nothing is really hidden Shelley Powers
• Re: Nothing is really hidden Shelley Powers
• ssh key (Was: Why I don't attend the weekly teleconference (Was: Input on the agenda)) Rob Sayre
• Re: Nothing is really hidden David Singer
• Re: Safe ways of implementing limits on buffer sizes in the parser Henri Sivonen
• Re: HTML 4.01 Strict table attributes and downplayed errors Ian Hickson
• Re: consensus (was: Codecs for <video> and <audio>) Silvia Pfeiffer
• Re: consensus (was: Codecs for <video> and <audio>) Joe D Williams
• Re: Issues of @summary and use of data for "decisions" Steve Axthelm
• Re: Safe ways of implementing limits on buffer sizes in the parser Ian Hickson
• Re: Merge NETWORK_NO_SOURCE and NETWORK_EMPTY Ian Hickson
• AT and "hidden" data, was: Why I don't attend the weekly teleconference (Was: Input on the agenda) Julian Reschke
• Re: Parsing: "<" inside tags Ian Hickson
• Re: <section><hgroup><h1><h2> styling Ian Hickson
• Re: Accesskey issues Ian Hickson
• RE: Why I don't attend the weekly teleconference (Was: Input on the agenda) Murray Maloney
• Re: Nothing is really hidden Steve Axthelm

Wednesday, 1 July 2009

• Re: consensus (was: Codecs for <video> and <audio>) Michael A. Puls II
• consensus (was: Codecs for <video> and <audio>) Rob Sayre
• Re: Nothing is really hidden Jonas Sicking
• Re: Codecs for <video> and <audio> Rob Sayre
• Re: Denoting privacy-sensitive requests (was: Re: Do we need to rename the Origin header?) Bil Corry
• Re: Nothing is really hidden Shelley Powers
• Re: Denoting privacy-sensitive requests (was: Re: Do we need to rename the Origin header?) Jonas Sicking
• Re: Nothing is really hidden Jonas Sicking
• Re: Nothing is really hidden Shelley Powers
• [Bug 6606] generic 3rd-party <mark>, Smart Tags, and Activities prevention bugzilla@wiggum.w3.org
• [Bug 6774] <mark> element: restrict insertion by other servers bugzilla@wiggum.w3.org
• Re: Nothing is really hidden Jonas Sicking
• Re: Codecs for <video> and <audio> Rob Sayre
• Re: Nothing is really hidden Shelley Powers
• Re: Nothing is really hidden Shelley Powers
• Re: Nothing is really hidden David Singer
• Re: Nothing is really hidden Shelley Powers
• Re: Nothing is really hidden Shelley Powers
• Re: Nothing is really hidden John C. Vernaleo
• Nothing is really hidden Shelley Powers
• Re: Example of Good Summary (Was: Issues of @summary and use of data for "decisions") Ben Millard
• Re: Why I don't attend the weekly teleconference (Was: Input on the agenda) Lachlan Hunt
• Re: [webstorage] IndexGetter Methods Should Not Throw Exception Ian Hickson
• Re: Firing media events early for throttled downloads Maciej Stachowiak
• Re: Codecs for <video> and <audio> Joe D Williams
• Re: Footnotes and sectioning roots. <figure> and <table> Ian Hickson
• RE: Firing media events early for throttled downloads Ian Hickson
• Re: R2866 : better talk about "CSS display" instead of "CSS tables" Ian Hickson
• Re: Why I don't attend the weekly teleconference (Was: Input on the agenda) Murray Maloney
• Re: comments on draft-barth-mime-sniffing Boris Zbarsky

Last message date: Friday, 31 July 2009 23:48:23 UTC