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

Tuesday, 30 September 2008

• Re: conformance checker for HTML+ARIA? Felix Sasaki
• Re: FYI PFWG F2F topics of potential interest Ben Millard
• minor tweak to FYI PFWG F2F topics of potential interest Al Gilman
• RE: [forms] control_element.value getter/setter newline normalization Justin James
• Re: SVG Semantics Re: SVG and MathML in text/html Henri Sivonen
• FYI PFWG F2F topics of potential interest Al Gilman
• Re: conformance checker for HTML+ARIA? Henri Sivonen
• W3C Workshop on Security for Access to Device APIs - London, December 10-11 Dominique Hazael-Massieux
• Re: @headers Wiki page Laura Carlson
• [Bug 6127] New: Deal with origin details in WebSocket and postMessage feedback bugzilla@wiggum.w3.org
• [forms] control_element.value getter/setter newline normalization Michael A. Puls II
• [forms] Detailed review of the DOMControlValueChanged and 'input' events Michael A. Puls II
• Re: SVG Semantics Re: SVG and MathML in text/html Maciej Stachowiak
• Re: SVG Semantics Re: SVG and MathML in text/html Maciej Stachowiak

Monday, 29 September 2008

• Re: SVG Semantics Re: SVG and MathML in text/html Charles McCathieNevile
• Re: SVG Semantics Re: SVG and MathML in text/html Charles McCathieNevile
• Re: Question about origin serialization Boris Zbarsky
• Re: Question about origin serialization Maciej Stachowiak
• Re: Question about origin serialization Boris Zbarsky
• Re: Question about origin serialization Boris Zbarsky

Sunday, 28 September 2008

• Re: SVG Semantics Re: SVG and MathML in text/html Maciej Stachowiak
• Re: SVG Semantics Re: SVG and MathML in text/html James Graham
• RE: SVG Semantics Re: SVG and MathML in text/html Dailey, David P.
• Re: SVG Semantics Re: SVG and MathML in text/html Charles McCathieNevile
• Re: Dirac 1.0.0 released. Comments? Charles McCathieNevile

Saturday, 27 September 2008

• Re: Question about origin serialization Anne van Kesteren
• Re: Question about origin serialization Adam Barth
• Re: Question about origin serialization Boris Zbarsky
• Re: Question about origin serialization Ian Hickson
• Re: Question about origin serialization Boris Zbarsky
• Re: Question about origin serialization Ian Hickson

Friday, 26 September 2008

• Re: Question about origin serialization Boris Zbarsky
• Re: Question about origin serialization Ian Hickson
• Re: @headers Wiki page James Craig
• Question about origin serialization Boris Zbarsky
• Re: dir=rtl and table header algorithm (was: Re: function and impacts) Gez Lemon
• dir=rtl and table header algorithm (was: Re: function and impacts) Simon Pieters
• Re: function and impacts (was: @scope and @headers reform) Gez Lemon
• @headers Wiki page Laura Carlson
• Re: function and impacts (was: @scope and @headers reform) Ben Millard
• Re: function and impacts (was: @scope and @headers reform) Ben Millard
• Re: function and impacts (was: @scope and @headers reform) Simon Pieters
• Re: function and impacts (was: @scope and @headers reform) Ben Millard
• Re: function and impacts (was: @scope and @headers reform) Gez Lemon

Thursday, 25 September 2008

• Re: contrived data table example Laura Carlson
• Re: contrived data table example Gez Lemon
• Re: contrived data table example Gez Lemon
• Re: contrived data table example Henri Sivonen
• re: contrived data table example Steven Faulkner
• Re: function and impacts (was: @scope and @headers reform) James Graham
• Re: function and impacts (was: @scope and @headers reform) James Graham
• Re: function and impacts (was: @scope and @headers reform) Gez Lemon
• Re: function and impacts (was: @scope and @headers reform) James Graham
• Re: function and impacts (was: @scope and @headers reform) James Graham
• Re: function and impacts (was: @scope and @headers reform) Laura Carlson
• Re: <style scoped> and semi-transparent content models Henri Sivonen
• Re: function and impacts (was: @scope and @headers reform) Gez Lemon
• Re: function and impacts (was: @scope and @headers reform) Gez Lemon
• Re: function and impacts (was: @scope and @headers reform) Henri Sivonen
• Re: function and impacts (was: @scope and @headers reform) Joshue O Connor
• Re: function and impacts (was: @scope and @headers reform) Steven Faulkner
• Re: function and impacts (was: @scope and @headers reform) Henri Sivonen
• Re: function and impacts (was: @scope and @headers reform) Henri Sivonen
• Re: function and impacts (was: @scope and @headers reform) Steven Faulkner
• Re: function and impacts (was: @scope and @headers reform) Henri Sivonen
• Re: function and impacts (was: @scope and @headers reform) Joshue O Connor

Wednesday, 24 September 2008

• Re: function and impacts Julian Reschke
• Re: function and impacts (was: @scope and @headers reform) Geoffrey Sneddon
• Re: function and impacts (was: @scope and @headers reform) Laura Carlson
• Re: function and impacts (was: @scope and @headers reform) Laura Carlson
• Re: function and impacts (was: @scope and @headers reform) Steven Faulkner
• Re: function and impacts (was: @scope and @headers reform) Henri Sivonen
• Re: Dirac 1.0.0 released. Comments? Thomas Davies
• Re: function and impacts (was: @scope and @headers reform) Leif Halvard Silli
• Re: function and impacts (was: @scope and @headers reform) Leif Halvard Silli

Tuesday, 23 September 2008

• Re: function and impacts (was: @scope and @headers reform) Laura Carlson
• Re: function and impacts (was: @scope and @headers reform) Leif Halvard Silli
• Re: function and impacts (was: @scope and @headers reform) James Craig
• Do we need axis or headers='a-TD-cell' ? Leif Halvard Silli
• Re: Is "breaking the Web" with HTML 5 a non issue? Dr. Olaf Hoffmann
• Re: function and impacts (was: @scope and @headers reform) Leif Halvard Silli
• Re: function and impacts (was: @scope and @headers reform) Leif Halvard Silli
• Re: Is "breaking the Web" with HTML 5 a non issue? Julian Reschke
• Re: Is "breaking the Web" with HTML 5 a non issue? Geoffrey Sneddon
• Re: function and impacts (was: @scope and @headers reform) Joshue O Connor
• Re: function and impacts (was: @scope and @headers reform) Leif Halvard Silli
• Re: Is "breaking the Web" with HTML 5 a non issue? Laura Carlson
• Re: function and impacts (was: @scope and @headers reform) Henri Sivonen
• Re: function and impacts (was: @scope and @headers reform) Laura Carlson
• Re: function and impacts (was: @scope and @headers reform) Leif Halvard Silli
• Re: function and impacts (was: @scope and @headers reform) Gez Lemon
• Re: function and impacts (was: @scope and @headers reform) Laura Carlson
• Re: function and impacts (was: @scope and @headers reform) Ben Millard
• Request for PFWG WAI review of multimedia accessibility requirements <audio> <video> Laura Carlson
• Re: function and impacts (was: @scope and @headers reform) Joshue O Connor
• RE: Is "breaking the Web" with HTML 5 a non issue? Justin James
• Re: function and impacts (was: @scope and @headers reform) James Craig
• Re: Is "breaking the Web" with HTML 5 a non issue? Leif Halvard Silli
• Re: Is "breaking the Web" with HTML 5 a non issue? Leif Halvard Silli

Monday, 22 September 2008

• Re: Is "breaking the Web" with HTML 5 a non issue? Sam Kuper
• Re: Is "breaking the Web" with HTML 5 a non issue? Dan Connolly
• Re: Is "breaking the Web" with HTML 5 a non issue? Dan Connolly
• RE: Is "breaking the Web" with HTML 5 a non issue? Justin James
• Re: Is "breaking the Web" with HTML 5 a non issue? L. David Baron
• Re: Is "breaking the Web" with HTML 5 a non issue? Boris Zbarsky
• Re: Is "breaking the Web" with HTML 5 a non issue? Boris Zbarsky
• Re: Is "breaking the Web" with HTML 5 a non issue? Sam Kuper
• Re: Is "breaking the Web" with HTML 5 a non issue? Sam Kuper
• RE: Is "breaking the Web" with HTML 5 a non issue? Justin James
• Re: Is "breaking the Web" with HTML 5 a non issue? Andrew Sidwell
• RE: Is "breaking the Web" with HTML 5 a non issue? Justin James
• RE: Is "breaking the Web" with HTML 5 a non issue? Justin James
• Re: State transitions for media elements Philip Jägenstedt
• Re: Is "breaking the Web" with HTML 5 a non issue? Andrew Sidwell
• Is "breaking the Web" with HTML 5 a non issue? Justin James
• [Bug 6104] New: <video> and <audio> should prevent cross-origin media loads bugzilla@wiggum.w3.org
• [Bug 6103] New: video section editorial issues bugzilla@wiggum.w3.org

Sunday, 21 September 2008

• [Bug 6102] New: Please do not break applet element in HTML 5 bugzilla@wiggum.w3.org

Saturday, 20 September 2008

• [Bug 6101] New: media elements - ready states - events should be async bugzilla@wiggum.w3.org

Friday, 19 September 2008

• [Bug 6100] New: Process MessagePort feedback bugzilla@wiggum.w3.org
• [Bug 6099] New: Process notification feedback bugzilla@wiggum.w3.org
• [Bug 6098] New: input type=foo as an element-level section bugzilla@wiggum.w3.org
• [Bug 6097] New: <body background> is a URL attribute? bugzilla@wiggum.w3.org
• Re: No tabbed browsing in HTML 5? Boris Zbarsky
• Re: No tabbed browsing in HTML 5? Boris Zbarsky
• RE: No tabbed browsing in HTML 5? N-at-Work
• Re: No tabbed browsing in HTML 5? Anne van Kesteren
• Re: No tabbed browsing in HTML 5? Hallvord R. M. Steen
• Re: No tabbed browsing in HTML 5? Leif Halvard Silli
• Re: No tabbed browsing in HTML 5? Leif Halvard Silli
• Re: Dirac 1.0.0 released. Comments? Dave Singer
• State transitions for media elements Dave Singer
• Buffered bytes for media elements Dave Singer
• Pause on exit from Cue Ranges Dave Singer
• Re: No tabbed browsing in HTML 5? Boris Zbarsky

Thursday, 18 September 2008

• Re: No tabbed browsing in HTML 5? Leif Halvard Silli
• Re: No tabbed browsing in HTML 5? Philip Taylor
• Re: No tabbed browsing in HTML 5? Lachlan Hunt
• RE: No tabbed browsing in HTML 5? Justin James
• Re: No tabbed browsing in HTML 5? hallvord@opera.com
• Re: No tabbed browsing in HTML 5? Leif Halvard Silli
• RE: No tabbed browsing in HTML 5? Justin James
• RE: No tabbed browsing in HTML 5? stephane.deschamps@orange-ftgroup.com
• Re: No tabbed browsing in HTML 5? Justin Anthony Knapp
• Re: No tabbed browsing in HTML 5? John C. Vernaleo
• No tabbed browsing in HTML 5? N-at-Work
• Dirac 1.0.0 released. Comments? Matthew Raymond

Tuesday, 16 September 2008

• RE: @headers issue resolved - allowing a td to be referenced by a header to be in the HTMl5 spec. Chris Wilson
• Re: @headers issue resolved - allowing a td to be referenced by a header to be in the HTMl5 spec. Maciej Stachowiak
• Re: @headers issue resolved - allowing a td to be referenced by a header to be in the HTMl5 spec. Maciej Stachowiak
• willValidate and image controls Anne van Kesteren

Sunday, 14 September 2008

• Re: HTML5 non-accessibility? Robert J Burns
• function and impacts (was: @scope and @headers reform) Al Gilman
• RE: HTML5 non-accessibility? Justin James
• Re: HTML5 non-accessibility? Laura Carlson

Saturday, 13 September 2008

• HTML5 non-accessibility? Brian Long
• HTMLOptionElement constructor Anne van Kesteren
• 4.3 Source fallback Jim Jewett

Friday, 12 September 2008

• [Bug 6057] New: in the audio portion of the spec, at the end of 4.7.8.0 it mentions "If the src argument is present..." but the example given calls it the argument 'url' bugzilla@wiggum.w3.org
• RE: acceptable fallbacks [was: Re: Is longdesc a good solution? ...] John Foliot
• Accessibility for the Media Elements in HTML5[1][2] Robert J Burns
• Re: acceptable fallbacks [was: Re: Is longdesc a good solution? ...] Dave Singer
• RE: Privacy implications of automatic alternative selection (Re: Acessibility of <audio> and <video>) Dailey, David P.
• Re: Privacy implications of automatic alternative selection (Re: Acessibility of <audio> and <video>) Joseph Scheuhammer
• Re: Privacy implications of automatic alternative selection (Re: Acessibility of <audio> and <video>) William Loughborough
• RE: Privacy implications of automatic alternative selection (Re: Acessibility of <audio> and <video>) Justin James
• Re: Privacy implications of automatic alternative selection (Re: Acessibility of <audio> and <video>) Al Gilman
• Re: acceptable fallbacks [was: Re: Is longdesc a good solution? ...] Charles McCathieNevile
• Re: acceptable fallbacks [was: Re: Is longdesc a good solution? ...] Henri Sivonen
• Re: Privacy implications of automatic alternative selection (Re: Acessibility of <audio> and <video>) Lachlan Hunt
• Re: acceptable fallbacks [was: Re: Is longdesc a good solution? ...] Robert J Burns
• Re: Privacy implications of automatic alternative selection (Re: Acessibility of <audio> and <video>) Henri Sivonen
• Re: Privacy implications of automatic alternative selection (Re: Acessibility of <audio> and <video>) Henri Sivonen
• RE: Privacy implications of automatic alternative selection (Re: Acessibility of <audio> and <video>) Schnabel, Stefan
• Status of Link header Mark Nottingham
• RE: Privacy implications of automatic alternative selection (Re: Acessibility of <audio> and <video>) Justin James
• RE: Privacy implications of automatic alternative selection (Re: Acessibility of <audio> and <video>) Dailey, David P.
• RE: acceptable fallbacks [was: Re: Is longdesc a good solution? ...] Dave Singer

Thursday, 11 September 2008

• Re: Privacy implications of automatic alternative selection (Re: Acessibility of <audio> and <video>) Charles McCathieNevile
• Re: Privacy implications of automatic alternative selection (Re: Acessibility of <audio> and <video>) Dave Singer
• Re: Privacy implications of automatic alternative selection (Re: Acessibility of <audio> and <video>) Dave Singer
• Re: Privacy implications of automatic alternative selection (Re: Acessibility of <audio> and <video>) T.V Raman
• Re: Multimedia Accessibility <Audio> <Video> Wiki Page Laura Carlson
• Re: Multimedia Accessibility <Audio> <Video> Wiki Page Lachlan Hunt
• RE: Multimedia Accessibility <Audio> <Video> Wiki Page Sean Hayes
• Re: Privacy implications of automatic alternative selection (Re: Acessibility of <audio> and <video>) Jan Richards
• Multimedia Accessibility <Audio> <Video> Wiki Page Laura Carlson
• Re: Privacy implications of automatic alternative selection (Re: Acessibility of <audio> and <video>) Philip TAYLOR
• Privacy implications of automatic alternative selection (Re: Acessibility of <audio> and <video>) T.V Raman
• Privacy implications of automatic alternative selection (Re: Acessibility of <audio> and <video>) Henri Sivonen
• Re: acceptable fallbacks [was: Re: Is longdesc a good solution? ...] Henri Sivonen
• RE: longdesc in the wild [was: Re: Is longdesc a good solution? ...] John Foliot
• Re: Draft agenda, Oct. 23-24 face-to-face meeting Michael(tm) Smith
• Re: acceptable fallbacks [was: Re: Is longdesc a good solution? ...] Jim Jewett

Wednesday, 10 September 2008

• Regarding Transcriptions/Captions (was RE: acceptable fallbacks [was: Re: Is longdesc a good solution? ...]) John Foliot
• Re: acceptable fallbacks [was: Re: Is longdesc a good solution? ...] David Poehlman
• Re: acceptable fallbacks [was: Re: Is longdesc a good solution? ...] David Poehlman
• RE: Is longdesc a good solution? (was: Acessibility of <audio> and <video>) John Foliot
• Re: Citing multiple <blockquote> elements in HTML5 Sam Kuper
• Citing multiple <blockquote> elements in HTML5 Sam Kuper
• Re: Draft agenda, Oct. 23-24 face-to-face meeting Ben Millard
• Re: Acessibility of <audio> and <video> Lachlan Hunt
• Why the curly braces are not solving a real problem [was: Re: Mandatory and Important] Al Gilman
• RE: acceptable fallbacks [was: Re: Is longdesc a good solution? ...] Justin James
• Overemphasis on screen readers? Justin James
• RE: acceptable fallbacks [was: Re: Is longdesc a good solution? ...] Justin James
• Re: acceptable fallbacks [was: Re: Is longdesc a good solution? ...] Laura Carlson
• Re: acceptable fallbacks [was: Re: Is longdesc a good solution? ...] Henri Sivonen
• RE: acceptable fallbacks [was: Re: Is longdesc a good solution? ...] Justin James
• Re: acceptable fallbacks [was: Re: Is longdesc a good solution? ...] David Poehlman
• Re: What namespace features popular SVG tools really emit (ISSUE-37) Robin Berjon
• Draft agenda, Oct. 23-24 face-to-face meeting Michael(tm) Smith
• Re: Is longdesc a good solution? (was: Acessibility of <audio> and <video>) Henri Sivonen
• Re: acceptable fallbacks [was: Re: Is longdesc a good solution? ...] Henri Sivonen
• Re: Acessibility of <audio> and <video> Henri Sivonen
• Re: Is longdesc a good solution? (was: Acessibility of <audio> and <video>) David Poehlman
• Re: Is longdesc a good solution? (was: Acessibility of <audio> and <video>) Leif Halvard Silli
• [Bug 6052] New: Should propagate uncaught exceptions from workers to their owner bugzilla@wiggum.w3.org

Tuesday, 9 September 2008

• Re: Acessibility of <audio> and <video> Dave Singer
• Re: Acessibility of <audio> and <video> Leif Halvard Silli
• Re: Acessibility of <audio> and <video> Dave Singer
• Re: Acessibility of <audio> and <video> Dave Singer
• Re: Acessibility of <audio> and <video> Dave Singer
• Re: acceptable fallbacks [was: Re: Is longdesc a good solution? ...] Leif Halvard Silli
• longdesc in the wild [was: Re: Is longdesc a good solution? ...] Jim Jewett
• Re: Is longdesc a good solution? (was: Acessibility of <audio> and <video>) Matt Morgan-May
• acceptable fallbacks [was: Re: Is longdesc a good solution? ...] Jim Jewett
• Re: Is longdesc a good solution? (was: Acessibility of <audio> and <video>) Philip TAYLOR (Ret'd)
• RE: Is longdesc a good solution? (was: Acessibility of <audio> and <video>) Justin James
• Re: Is longdesc a good solution? (was: Acessibility of <audio> and <video>) Robert J Burns
• Re: Is longdesc a good solution? (was: Acessibility of <audio> and <video>) Philip TAYLOR (Ret'd)
• Re: Is longdesc a good solution? (was: Acessibility of <audio> and <video>) David Poehlman
• Re: Is longdesc a good solution? (was: Acessibility of <audio> and <video>) Leif Halvard Silli
• Re: Is longdesc a good solution? (was: Acessibility of <audio> and <video>) David Poehlman
• Re: Is longdesc a good solution? (was: Acessibility of <audio> and <video>) Leif Halvard Silli
• Re: Is longdesc a good solution? (was: Acessibility of <audio> and <video>) Leif Halvard Silli
• Re: Is CHOICE a good solution? (was RE: Is longdesc a good solution? (was: Acessibility of <audio> and <video>)) Ben Boyle
• Re: Is longdesc a good solution? (was: Acessibility of <audio> and <video>) David Poehlman
• Re: Is longdesc a good solution? (was: Acessibility of <audio> and <video>) Henri Sivonen

Monday, 8 September 2008

• Re: Is longdesc a good solution? (was: Acessibility of <audio> and <video>) Matt Morgan-May
• RE: Is CHOICE a good solution? (was RE: Is longdesc a good solution? (was: Acessibility of <audio> and <video>)) John Foliot
• Re: longdesc="" in HTML5 Steven Faulkner
• Re: longdesc="" in HTML5 Ian Hickson
• Re: Is CHOICE a good solution? (was RE: Is longdesc a good solution? (was: Acessibility of <audio> and <video>)) James Craig
• Minor clarrification : Is CHOICE a good solution? (was RE: Is longdesc a good solution? (was: Acessibility of <audio> and <video>)) John Foliot
• Is CHOICE a good solution? (was RE: Is longdesc a good solution? (was: Acessibility of <audio> and <video>)) John Foliot
• Long fallback. A problem description. Leif Halvard Silli
• Re: Is longdesc a good solution? (was: Acessibility of <audio> and <video>) Robert J Burns
• Re: Is longdesc a good solution? (was: Acessibility of <audio> and <video>) Robert J Burns
• Re: Is longdesc a good solution? (was: Acessibility of <audio> and <video>) Robert J Burns
• RE: Is longdesc a good solution? (was: Acessibility of <audio> and <video>) Justin James
• Re: longdesc="" in HTML5 Robert J Burns
• Re: Is longdesc a good solution? (was: Acessibility of <audio> and <video>) David Poehlman
• Re: Is longdesc a good solution? (was: Acessibility of <audio> and <video>) David Poehlman
• Re: Is longdesc a good solution? (was: Acessibility of <audio> and <video>) David Poehlman
• [Bug 6038] New: "noframes", "script", "style", "title" in 'after head' mode pop prematurely bugzilla@wiggum.w3.org
• [Bug 6037] New: Elaborate on Web compat characteristics of task queue interaction bugzilla@wiggum.w3.org
• Re: Is longdesc a good solution? (was: Acessibility of <audio> and <video>) Lachlan Hunt
• Re: Is longdesc a good solution? (was: Acessibility of <audio> and <video>) Henri Sivonen
• Re: profile attribute and conformance [was: Comparing conformance requirements against real-world docs] Toby A Inkster
• Re: longdesc="" in HTML5 Joshue O Connor
• Re: Is longdesc a good solution? (was: Acessibility of <audio> and <video>) Henri Sivonen
• Re: Is longdesc a good solution? (was: Acessibility of <audio> and <video>) Leif Halvard Silli
• Re: Is longdesc a good solution? (was: Acessibility of <audio> and <video>) Leif Halvard Silli
• Re: Is longdesc a good solution? (was: Acessibility of <audio> and <video>) James Craig
• RE: Is longdesc a good solution? (was: Acessibility of <audio> and <video>) John Foliot
• Re: Is longdesc a good solution? (was: Acessibility of <audio> and <video>) James Craig
• Re: Is longdesc a good solution? (was: Acessibility of <audio> and <video>) Leif Halvard Silli

Sunday, 7 September 2008

• Re: Is longdesc a good solution? (was: Acessibility of <audio> and <video>) Lachlan Hunt
• Formal Request for Re-Instation of @longdesc into the HTML 5 specification (was RE: How to add/reinstate dropped accessibly features in HTML5 (was Re: longdesc="" in HTML5)) John Foliot
• Re: longdesc="" in HTML5 Ian Hickson
• Re: Is longdesc a good solution? (was: Acessibility of <audio> and <video>) Lachlan Hunt
• Re: Is longdesc a good solution? (was: Acessibility of <audio> and <video>) Leif Halvard Silli
• RE: Is longdesc a good solution? (was: Acessibility of <audio> and <video>) John Foliot
• Re: Is longdesc a good solution? (was: Acessibility of <audio> and <video>) Leif Halvard Silli
• [Bug 6036] New: HTMLCollection.namedItem() should look for non-HTML elements bugzilla@wiggum.w3.org
• Re: Acessibility of <audio> and <video> Henri Sivonen
• Re: profile attribute and conformance [was: Comparing conformance requirements against real-world docs] Henri Sivonen
• Re: Is longdesc a good solution? (was: Acessibility of <audio> and <video>) Henri Sivonen
• Re: Is longdesc a good solution? (was: Acessibility of <audio> and <video>) Henri Sivonen
• Re: Is longdesc a good solution? (was: Acessibility of <audio> and <video>) David Poehlman
• Re: Is longdesc a good solution? (was: Acessibility of <audio> and <video>) Henri Sivonen
• How to add/reinstate dropped accessibly features in HTML5 (was Re: longdesc="" in HTML5) Laura Carlson
• Re: longdesc="" in HTML5 Joshue O Connor
• longdesc="" in HTML5 Ian Hickson
• [Bug 6035] New: Process appcache feedback bugzilla@wiggum.w3.org
• [Bug 6034] New: Process <video> feedback bugzilla@wiggum.w3.org
• [Bug 6033] New: Forms section bugzilla@wiggum.w3.org
• [Bug 6032] New: Serializing a doctype with invalid public id bugzilla@wiggum.w3.org
• Re: Is longdesc a good solution? (was: Acessibility of <audio> and <video>) James Craig
• RE: Is longdesc a good solution? Justin James

Saturday, 6 September 2008

• RE: Is longdesc a good solution? (was: Acessibility of <audio> and <video>) John Foliot
• RE: @longdesc - starting over (was RE: Acessibility of <audio> and <video>) John Foliot
• Re: Is longdesc a good solution? Laura Carlson
• Re: @longdesc - starting over (was RE: Acessibility of <audio> and <video>) David Poehlman
• Re: Is longdesc a good solution? Steven Faulkner
• Re: @longdesc - starting over (was RE: Acessibility of <audio> and <video>) Philip TAYLOR
• Re: @longdesc - starting over (was RE: Acessibility of <audio> and <video>) Lachlan Hunt
• Re: Is longdesc a good solution? Geoffrey Sneddon
• @longdesc - starting over (was RE: Acessibility of <audio> and <video>) John Foliot
• RE: Is longdesc a good solution? Justin James
• Re: Is longdesc a good solution? David Poehlman
• Re: Is longdesc a good solution? David Poehlman
• Re: Is longdesc a good solution? David Poehlman
• Re: Is longdesc a good solution? Laura Carlson
• Re: Is longdesc a good solution? Joshue O Connor
• Re: Is longdesc a good solution? Steven Faulkner
• Re: Is longdesc a good solution? Lachlan Hunt
• Re: Is longdesc a good solution? Joshue O Connor
• Re: Is longdesc a good solution? Laura Carlson
• Re: Is longdesc a good solution? Steven Faulkner
• Re: Is longdesc a good solution? Steven Faulkner
• Re: Is longdesc a good solution? Lachlan Hunt
• Re: Is longdesc a good solution? Steven Faulkner
• Re: Is longdesc a good solution? Lachlan Hunt
• Re: Is longdesc a good solution? Steven Faulkner
• Re: Is longdesc a good solution? Lachlan Hunt
• RE: ISSUE-54 (html5-doctype-vs-xslt): XSLT 1.0 can not generate HTML5 documents [HTML 5 spec] Justin James
• Re: Is longdesc a good solution? (was: Acessibility of <audio> and <video>) Leif Halvard Silli
• Re: Is longdesc a good solution? (was: Acessibility of <audio> and <video>) James Craig
• Re: Is longdesc a good solution? David Poehlman
• Re: Acessibility of <audio> and <video> Leif Halvard Silli

Friday, 5 September 2008

• Re: Acessibility of <audio> and <video> James Craig
• Re: Is longdesc a good solution? Leif Halvard Silli
• Re: Acessibility of <audio> and <video> Eric Carlson
• Re: Is longdesc a good solution? Lachlan Hunt
• RE: Is longdesc a good solution? (was: Acessibility of <audio> and <video>) Justin James
• RE: ISSUE-54 (html5-doctype-vs-xslt): XSLT 1.0 can not generate HTML5 documents [HTML 5 spec] Justin James
• Re: Is longdesc a good solution? (was: Acessibility of <audio> and <video>) James Craig
• Re: ISSUE-54 (html5-doctype-vs-xslt): XSLT 1.0 can not generate HTML5 documents [HTML 5 spec] Simon Pieters
• Re: ISSUE-54 (html5-doctype-vs-xslt): XSLT 1.0 can not generate HTML5 documents [HTML 5 spec] Boris Zbarsky
• RE: ISSUE-54 (html5-doctype-vs-xslt): XSLT 1.0 can not generate HTML5 documents [HTML 5 spec] Justin James
• RE: Is longdesc a good solution? John Foliot
• Re: profile attribute and conformance (copy-and-paste details) Dan Connolly
• Re: Is longdesc a good solution? Lachlan Hunt
• Re: Is longdesc a good solution? Leif Halvard Silli
• Re: Acessibility of <audio> and <video> Lachlan Hunt
• Re: Acessibility of <audio> and <video> David Poehlman
• Re: Acessibility of <audio> and <video> Leif Halvard Silli
• Re: Acessibility of <audio> and <video> David Poehlman
• Re: @headers issue resolved - allowing a td to be referenced by a header to be in the HTMl5 spec. Laura Carlson
• Re: Is longdesc a good solution? Lachlan Hunt
• Re: ISSUE-54 (html5-doctype-vs-xslt): XSLT 1.0 can not generate HTML5 documents [HTML 5 spec] Anne van Kesteren
• Re: profile attribute and conformance [was: Comparing conformance requirements against real-world docs] Toby A Inkster
• Re: @headers issue resolved - allowing a td to be referenced by a header to be in the HTMl5 spec. Gez Lemon
• Re: ISSUE-54 (html5-doctype-vs-xslt): XSLT 1.0 can not generate HTML5 documents [HTML 5 spec] Jonas Sicking
• Fwd: @headers issue resolved - allowing a td to be referenced by a header to be in the HTMl5 spec. Laura Carlson
• Re: ISSUE-54 (html5-doctype-vs-xslt): XSLT 1.0 can not generate HTML5 documents [HTML 5 spec] Jirka Kosek
• Re: Acessibility of <audio> and <video> Henri Sivonen
• Re: profile attribute and conformance [was: Comparing conformance requirements against real-world docs] Henri Sivonen
• RE: Is longdesc a good solution? (was: Acessibility of <audio> and <video>) John Foliot
• Re: @headers issue resolved - allowing a td to be referenced by a header to be in the HTMl5 spec. Ben Millard

Thursday, 4 September 2008

• Re: Is longdesc a good solution? (was: Acessibility of <audio> and <video>) Lachlan Hunt
• Re: Acessibility of <audio> and <video> Leif Halvard Silli
• Re: Acessibility of <audio> and <video> David Poehlman
• Re: Acessibility of <audio> and <video> Lachlan Hunt
• Re: Limitations of IE8 type-sniffing opt-out Philip Taylor
• Re: Acessibility of <audio> and <video> David Poehlman
• Re: Acessibility of <audio> and <video> Lachlan Hunt
• Re: Acessibility of <audio> and <video> David Poehlman
• Re: Acessibility of <audio> and <video> Lachlan Hunt
• Re: Acessibility of <audio> and <video> Eric Carlson
• RE: Acessibility of <audio> and <video> John Foliot
• Re: fragid navigation and pct-encoded Anne van Kesteren
• Re: Acessibility of <audio> and <video> Cindy Sue Causey
• Re: Acessibility of <audio> and <video> Benjamin Hawkes-Lewis
• Re: ISSUE-54 (html5-doctype-vs-xslt): XSLT 1.0 can not generate HTML5 documents [HTML 5 spec] Leif Halvard Silli
• Re: profile attribute and conformance [was: Comparing conformance requirements against real-world docs] Ryan King
• Re: new XSLT output methods, was: several messages Julian Reschke
• Re: new XSLT output methods, was: several messages Boris Zbarsky
• Re: several messages Leif Halvard Silli
• Re: profile attribute and conformance [was: Comparing conformance requirements against real-world docs] Henri Sivonen
• Re: new XSLT output methods, was: several messages Julian Reschke
• Re: ISSUE-54 (html5-doctype-vs-xslt): XSLT 1.0 can not generate HTML5 documents [HTML 5 spec] Julian Reschke
• Re: fragid navigation and pct-encoded Thomas Broyer
• Re: new XSLT output methods, was: several messages Boris Zbarsky
• Re: new XSLT output methods, was: several messages Boris Zbarsky
• Re: ISSUE-54 (html5-doctype-vs-xslt): XSLT 1.0 can not generate HTML5 documents [HTML 5 spec] Michael(tm) Smith
• fragid navigation and pct-encoded Anne van Kesteren
• profile attribute and conformance [was: Comparing conformance requirements against real-world docs] Michael(tm) Smith
• Re: new XSLT output methods, was: several messages Michael(tm) Smith
• Re: Acessibility of <audio> and <video> Lachlan Hunt
• Re: Acessibility of <audio> and <video> David Poehlman
• Re: Acessibility of <audio> and <video> Henri Sivonen
• Re: Acessibility of <audio> and <video> Ben Boyle
• Re: What namespace features popular SVG tools really emit (ISSUE-37) Henri Sivonen
• Re: new XSLT output methods, was: several messages Julian Reschke
• Re: new XSLT output methods, was: several messages Thomas Broyer
• Re: What namespace features popular SVG tools really emit (ISSUE-37) Henri Sivonen
• Re: Acessibility of <audio> and <video> Henri Sivonen
• new XSLT output methods, was: several messages Julian Reschke
• Re: several messages Michael(tm) Smith
• Re: What namespace features popular SVG tools really emit (ISSUE-37) Manuel Strehl
• Re: Comparing conformance requirements against real-world docs Henri Sivonen
• Re: Comparing conformance requirements against real-world docs Henri Sivonen
• RE: Acessibility of <audio> and <video> Justin James

Wednesday, 3 September 2008

• Re: Acessibility of <audio> and <video> Dave Singer
• RE: @headers issue resolved - allowing a td to be referenced by a header to be in the HTMl5 spec. Chris Wilson
• Re: @headers issue resolved - allowing a td to be referenced by a header to be in the HTMl5 spec. Ben Millard
• Re: Comparing conformance requirements against real-world docs Dan Connolly
• RE: @headers issue resolved - allowing a td to be referenced by a header to be in the HTMl5 spec. Chris Wilson
• Re: What namespace features popular SVG tools really emit (ISSUE-37) Julian Reschke
• Re: What namespace features popular SVG tools really emit (ISSUE-37) Anne van Kesteren
• Re: What namespace features popular SVG tools really emit (ISSUE-37) Anne van Kesteren
• Re: What namespace features popular SVG tools really emit (ISSUE-37) Julian Reschke
• Re: What namespace features popular SVG tools really emit (ISSUE-37) Jeff Schiller
• Re: What namespace features popular SVG tools really emit (ISSUE-37) Ian Hickson
• Re: Quirks mode vs. standards mode Boris Zbarsky
• RE: What namespace features popular SVG tools really emit (ISSUE-37) Dailey, David P.
• Re: What namespace features popular SVG tools really emit (ISSUE-37) Anne van Kesteren
• RE: What namespace features popular SVG tools really emit (ISSUE-37) Dailey, David P.
• Quirks mode vs. standards mode (was: Re: ISSUE-54 (html5-doctype-vs-xslt): ...) Simon Pieters
• RE: ISSUE-54 (html5-doctype-vs-xslt): XSLT 1.0 can not generate HTML5 documents [HTML 5 spec] Justin James
• Re: ISSUE-54 (html5-doctype-vs-xslt): XSLT 1.0 can not generate HTML5 documents [HTML 5 spec] Boris Zbarsky
• Re: ISSUE-54 (html5-doctype-vs-xslt): XSLT 1.0 can not generate HTML5 documents [HTML 5 spec] Boris Zbarsky
• 2 new posts: Research Assistant/ Research Fellow in Semantic Web/Ontology and Recommender Systems for Live Sciences: Closing Date: 12 September 2008 Patty Kostkova
• RE: several messages Justin James
• Re: new XSLT output methods, was: several messages Jirka Kosek
• new XSLT output methods, was: several messages Julian Reschke
• Re: several messages Jirka Kosek
• Re: What namespace features popular SVG tools really emit (ISSUE-37) Henri Sivonen
• Re: several messages Lachlan Hunt
• Re: What namespace features popular SVG tools really emit (ISSUE-37) Erik Dahlström
• new XSLT output methods, was: several messages Julian Reschke
• Re: several messages Jirka Kosek
• Re: several messages Jirka Kosek
• Re: several messages Anne van Kesteren
• Re: several messages Jirka Kosek
• Re: several messages Julian Reschke
• Re: Limitations of IE8 type-sniffing opt-out Julian Reschke
• Limitations of IE8 type-sniffing opt-out Philip Taylor
• Re: several messages Thomas Broyer
• Re: several messages Julian Reschke
• Re: several messages Lachlan Hunt
• Re: ISSUE-54 (html5-doctype-vs-xslt): XSLT 1.0 can not generate HTML5 documents [HTML 5 spec] Lachlan Hunt
• Re: ISSUE-54 (html5-doctype-vs-xslt): XSLT 1.0 can not generate HTML5 documents [HTML 5 spec] Simon Pieters
• Re: several messages Ian Hickson
• Re: several messages Ben Millard
• Re: ISSUE-54 (html5-doctype-vs-xslt): XSLT 1.0 can not generate HTML5 documents [HTML 5 spec] Boris Zbarsky
• Re: ISSUE-54 (html5-doctype-vs-xslt): XSLT 1.0 can not generate HTML5 documents [HTML 5 spec] Karl Dubost
• Re: several messages Ian Hickson
• Re: several messages Leif Halvard Silli
• Re: ISSUE-54 (html5-doctype-vs-xslt): XSLT 1.0 can not generate HTML5 documents [HTML 5 spec] Ian Hickson
• Re: several messages Ian Hickson
• Re: several messages Leif Halvard Silli
• Re: ISSUE-54 (html5-doctype-vs-xslt): XSLT 1.0 can not generate HTML5 documents [HTML 5 spec] Boris Zbarsky
• Re: ISSUE-54 (html5-doctype-vs-xslt): XSLT 1.0 can not generate HTML5 documents [HTML 5 spec] Karl Dubost
• Re: Acessibility of <audio> and <video> Leif Halvard Silli
• Re: Acessibility of <audio> and <video> Lachlan Hunt
• Re: several messages Leif Halvard Silli

Tuesday, 2 September 2008

• Re: several messages Ian Hickson
• Re: Acessibility of <audio> and <video> Smylers
• Re: several messages Jirka Kosek
• the "special" doctype (ISSUE-54), was: several messages Julian Reschke
• 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] Ian Hickson
• Re: several messages Ian Hickson
• Re: Acessibility of <audio> and <video> Leif Halvard Silli
• 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] Dean Edridge
• Re: Acessibility of <audio> and <video> Leif Halvard Silli
• Re: Acessibility of <audio> and <video> Smylers
• Re: For information : Google to release web browser Sam Kuper
• Re: Accessibility of <audio> and <video> Henri Sivonen
• RE: For information : Google to release web browser Justin James
• RE: Accessibility of <audio> and <video> Justin James
• Re: table headers - clear description of problem Steven Faulkner
• Re: Accessibility of <audio> and <video> Lachlan Hunt
• Re: table headers - clear description of problem Joshue O Connor
• Re: Accessibility of <audio> and <video> Matthew Raymond
• RE: table headers - clear description of problem stephane.deschamps@orange-ftgroup.com
• Re: ISSUE-54 (html5-doctype-vs-xslt): XSLT 1.0 can not generate HTML5 documents [HTML 5 spec] Julian Reschke
• Re: Acessibility of <audio> and <video> Lachlan Hunt
• Re: several messages Jirka Kosek
• Re: several messages Julian Reschke
• Re: several messages Ian Hickson
• For information : Google to release web browser Philip TAYLOR
• Re: Unsupported transport-layer encodings Alexey Proskuryakov
• Re: Unsupported transport-layer encodings Anne van Kesteren
• Re: Acessibility of <audio> and <video> Robert J Burns
• Re: Unsupported transport-layer encodings Alexey Proskuryakov
• Re: Unsupported transport-layer encodings Ian Hickson
• Re: HTML 5 draft copyright? Ian Hickson
• Re: Unsupported transport-layer encodings Alexey Proskuryakov
• Re: Unsupported transport-layer encodings Ian Hickson
• RE: Acessibility of <audio> and <video> Justin James
• Re: Are new void elements really a good idea? Patrick Garies
• HTML 5 draft copyright? Justin James

Monday, 1 September 2008

• Re: Acessibility of <audio> and <video> Leif Halvard Silli
• Re: Acessibility of <audio> and <video> Lachlan Hunt
• Re: Acessibility of <audio> and <video> Leif Halvard Silli
• Re: Looking for more editors Justin Anthony Knapp
• Re: Are new void elements really a good idea? Leif Halvard Silli
• RE: Acessibility of <audio> and <video> Justin James
• Re: About video & audio elements Nicolas LE GALL
• Re: Acessibility of <audio> and <video> Philip TAYLOR
• Re: Acessibility of <audio> and <video> Lachlan Hunt
• Re: About video & audio elements Lachlan Hunt
• Re: About video & audio elements Maurice
• Re: About video & audio elements Lachlan Hunt
• RE: Looking for more editors Justin James
• Re: Acessibility of <audio> and <video> Sam Kuper
• Re: Acessibility of <audio> and <video> Maurice
• Re: Acessibility of <audio> and <video> Maurice
• Re: Editor skills and funding (was: Looking for more editors and Editors) Charles McCathieNevile
• Editor skills and funding (was: Looking for more editors and Editors) Laura Carlson
• Re: Unsupported transport-layer encodings Ian Hickson
• Re: Looking for more editors Julian Reschke
• Re: Are new void elements really a good idea? Lachlan Hunt
• Re: Looking for more editors Philip TAYLOR
• Looking for more editors Ian Hickson
• Re: Are new void elements really a good idea? Anne van Kesteren

Sunday, 31 August 2008

• Re: Are new void elements really a good idea? Sam Ruby

Monday, 1 September 2008

• Re: Are new void elements really a good idea? Leif Halvard Silli
• align justify? Re: Comparing conformance requirements against real-world docs Karl Dubost

Last message date: Tuesday, 30 September 2008 23:58:34 UTC