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

Thursday, 31 July 2008

• Re: Deciding in public (Was: SVGWG SVG-in-HTML proposal) Sam Ruby
• Re: Deciding in public (Was: SVGWG SVG-in-HTML proposal) Ian Hickson
• Re: Deciding in public (Was: SVGWG SVG-in-HTML proposal) Sam Ruby
• Re: Translation control in HTML5 Ian Hickson
• Re: Translation control in HTML5 Jirka Kosek
• Re: Translation control in HTML5 Ian Hickson
• Re: Deciding in public (Was: SVGWG SVG-in-HTML proposal) Ian Hickson
• Re: Translation control in HTML5 Jirka Kosek
• RE: Translation control in HTML5 Justin James
• RE: Translation control in HTML5 Chris Wilson
• Re: Translation control in HTML5 Simon Pieters
• Re: Translation control in HTML5 Simon Pieters
• RE: Translation control in HTML5 Chris Wilson
• RE: Translation control in HTML5 Chris Wilson
• Re: Translation control in HTML5 Jirka Kosek
• Re: Deciding in public (Was: SVGWG SVG-in-HTML proposal) Julian Reschke
• Re: Translation control in HTML5 Jirka Kosek
• Re: Translation control in HTML5 Julian Reschke
• Re: Deciding in public (Was: SVGWG SVG-in-HTML proposal) Ian Hickson
• Re: HTMLCollection item() vs. namedItem() with [] syntax (detailed review of the DOM) Garrett Smith
• Re: Deciding in public (Was: SVGWG SVG-in-HTML proposal) Julian Reschke
• Re: Translation control in HTML5 Simon Pieters
• Re: Translation control in HTML5 Kornel Lesinski
• RE: Translation control in HTML5 Ian Hickson
• Re: Deciding in public (Was: SVGWG SVG-in-HTML proposal) Ian Hickson
• RE: Translation control in HTML5 Chris Wilson
• Re: Translation control in HTML5 Ian Hickson
• Translation control in HTML5 Chris Wilson
• Re: Deciding in public (Was: SVGWG SVG-in-HTML proposal) Sam Ruby
• Re: linking work on processing WAI-ARIA markup in HTML Al Gilman
• Re: linking work on processing WAI-ARIA markup in HTML Dan Connolly
• Re: Liaison with CSS WG to provide a mechanism for expressing the style of document semantics Robert J Burns
• Re: Liaison with CSS WG to provide a mechanism for expressing the style of document semantics Robert J Burns
• RE: Liaison with CSS WG to provide a mechanism for expressing the style of document semantics Pierre Saslawsky
• Re: Liaison with CSS WG to provide a mechanism for expressing the style of document semantics Philip TAYLOR (Ret'd)
• Re: Liaison with CSS WG to provide a mechanism for expressing the style of document semantics Daniel Glazman
• Re: Liaison with CSS WG to provide a mechanism for expressing the style of document semantics Philip TAYLOR (Ret'd)
• Re: changes in HTML5 draft regarding XHTML1 Roland Merrick
• Deciding in public (Was: SVGWG SVG-in-HTML proposal) Ian Hickson
• Re: SVG is not MathML Doug Schepers
• Re: changes in HTML5 draft regarding XHTML1 Michael(tm) Smith
• October target for HTML5 WD with HTML forms integration Michael(tm) Smith
• targeting August for next working draft of HTML5 Michael(tm) Smith
• Re: SVG is not MathML Boris Zbarsky
• SVG is not MathML (was: SVGWG SVG-in-HTML proposal (ISSUE-41, ISSUE-37)) Doug Schepers
• RE: SVGWG SVG-in-HTML proposal (Was: ISSUE-41: Decentralized extensibility) Justin James
• Re: Liaison with CSS WG to provide a mechanism for expressing the style of document semantics Daniel Glazman
• Re: FYI: Firefox 3.1 Will Support Ogg (ISSUE-7 video-codecs) Michael A. Puls II
• Re: The header element's textual content Ian Hickson

Wednesday, 30 July 2008

• Re: FYI: Firefox 3.1 Will Support Ogg (ISSUE-7 video-codecs) Sam Kuper
• Re: SVGWG SVG-in-HTML proposal (Was: ISSUE-41: Decentralized extensibility) Ian Hickson
• Re: img issue: should we restrict the URI Christian Schmidt
• Re: SVGWG SVG-in-HTML proposal (Was: ISSUE-41: Decentralized extensibility) Sam Ruby
• FYI: Firefox 3.1 Will Support Ogg (ISSUE-7 video-codecs) Dan Connolly
• Re: SVGWG SVG-in-HTML proposal (Was: ISSUE-41: Decentralized extensibility) Ian Hickson
• RE: SVGWG SVG-in-HTML proposal (Was: ISSUE-41: Decentralized extensibility) Ian Hickson
• RE: SVGWG SVG-in-HTML proposal (Was: ISSUE-41: Decentralized extensibility) Justin James
• Re: SVGWG SVG-in-HTML proposal (Was: ISSUE-41: Decentralized extensibility) Jeff Schiller
• Re: SVGWG SVG-in-HTML proposal (Was: ISSUE-41: Decentralized extensibility) Ian Hickson
• Re: SVGWG SVG-in-HTML proposal (ISSUE-41, ISSUE-37) Philip Taylor
• Re: img issue: should we restrict the URI Simon Pieters
• Re: SVGWG SVG-in-HTML proposal (Was: ISSUE-41: Decentralized extensibility) Sam Ruby
• Re: img issue: should we restrict the URI Christian Schmidt
• Re: SVGWG SVG-in-HTML proposal (ISSUE-41, ISSUE-37) Henri Sivonen
• Re: SVGWG SVG-in-HTML proposal (ISSUE-41, ISSUE-37) Henri Sivonen
• Re: SVGWG SVG-in-HTML proposal (ISSUE-41, ISSUE-37) Henri Sivonen
• Re: img issue: should we restrict the URI Ian Hickson
• Re: SVGWG SVG-in-HTML proposal (Was: ISSUE-41: Decentralized extensibility) Ian Hickson
• Re: SVGWG SVG-in-HTML proposal (Was: ISSUE-41: Decentralized extensibility) Ian Hickson
• Re: SVGWG SVG-in-HTML proposal (Was: ISSUE-41: Decentralized extensibility) Julian Reschke
• RE: Downloading of images by UA Justin James
• Re: SVGWG SVG-in-HTML proposal (Was: ISSUE-41: Decentralized extensibility) Jeff Schiller
• RE: img issue: should we restrict the URI Justin James
• Re: SVGWG SVG-in-HTML proposal (Was: ISSUE-41: Decentralized extensibility) Jeff Schiller
• Re: img issue: should we restrict the URI Jeff Schiller
• Re: SVGWG SVG-in-HTML proposal (Was: ISSUE-41: Decentralized extensibility) Doug Schepers
• Re: img issue: should we restrict the URI Ian Hickson
• Re: img issue: should we restrict the URI Ian Hickson
• Re: Image intrinsic aspect ratio and replaced element box aspect ratio Ian Hickson
• Re: Downloading of images by UA Ian Hickson
• Re: HTMLImageElement.width / height (detailed review of Semantics) Ian Hickson
• Re: <canvas> JPEG quality Ian Hickson
• Re: SVGWG SVG-in-HTML proposal (Was: ISSUE-41: Decentralized extensibility) Ian Hickson
• Re: SVGWG SVG-in-HTML proposal (Was: ISSUE-41: Decentralized extensibility) Ian Hickson
• Re: SVGWG SVG-in-HTML proposal is also ISSUE-37 (Was: ISSUE-41: Decentralized extensibility) Charles McCathieNevile
• Re: SVGWG SVG-in-HTML proposal (Was: ISSUE-41: Decentralized extensibility) Charles McCathieNevile

Tuesday, 29 July 2008

• Re: SVGWG SVG-in-HTML proposal (Was: ISSUE-41: Decentralized extensibility) Sam Ruby
• Re: <canvas> JPEG quality Boris Zbarsky
• [Bug 5909] New: Need a solution for replaceable properties bugzilla@wiggum.w3.org
• Re: SVGWG SVG-in-HTML proposal (Was: ISSUE-41: Decentralized extensibility) Ian Hickson
• Re: SVGWG SVG-in-HTML proposal (Was: ISSUE-41: Decentralized extensibility) Sam Ruby
• Re: SVGWG SVG-in-HTML proposal (Was: ISSUE-41: Decentralized extensibility) Henri Sivonen
• Re: SVGWG SVG-in-HTML proposal (Was: ISSUE-41: Decentralized extensibility) Henri Sivonen
• Re: SVGWG SVG-in-HTML proposal (Was: ISSUE-41: Decentralized extensibility) Sam Ruby
• Re: Fundamental assumptions (Was: SVGWG SVG-in-HTML proposal) Philip TAYLOR (Ret'd)
• Re: Fundamental assumptions (Was: SVGWG SVG-in-HTML proposal) Ian Hickson
• Re: Fundamental assumptions (Was: SVGWG SVG-in-HTML proposal) Philip TAYLOR (Ret'd)
• Re: SVGWG SVG-in-HTML proposal (Was: ISSUE-41: Decentralized extensibility) Ian Hickson
• Re: SVGWG SVG-in-HTML proposal (Was: ISSUE-41: Decentralized extensibility) Henri Sivonen
• Re: SVGWG SVG-in-HTML proposal (Was: ISSUE-41: Decentralized extensibility) Sam Ruby
• Fundamental assumptions (Was: SVGWG SVG-in-HTML proposal) Ian Hickson
• Re: SVGWG SVG-in-HTML proposal (Was: ISSUE-41: Decentralized extensibility) Philip TAYLOR (Ret'd)
• Re: SVGWG SVG-in-HTML proposal (Was: ISSUE-41: Decentralized extensibility) Ian Hickson
• Re: SVGWG SVG-in-HTML proposal (Was: ISSUE-41: Decentralized extensibility) Julian Reschke
• Re: SVGWG SVG-in-HTML proposal (Was: ISSUE-41: Decentralized extensibility) Henri Sivonen

Monday, 28 July 2008

• Re: Detailed review of 3.18.2. The datagrid element Ian Hickson
• Re: SVGWG SVG-in-HTML proposal (Was: ISSUE-41: Decentralized extensibility) Erik Dahlström
• RE: Liaison with CSS WG to provide a mechanism for expressing the style of document semantics Justin James
• Re: Liaison with CSS WG to provide a mechanism for expressing the style of document semantics Jens Meiert
• Re: document.body (detailed review of the DOM) Simon Pieters

Saturday, 26 July 2008

• WHATWG IRC discussion about GRDDL and head/@profile (ISSUE-55) Julian Reschke
• Re: <canvas> JPEG quality Ian Hickson
• Re: HTMLCollection item() vs. namedItem() with [] syntax (detailed review of the DOM) Garrett Smith
• Re: HTMLCollection item() vs. namedItem() with [] syntax (detailed review of the DOM) Cameron McCormack
• Re: <canvas> JPEG quality Boris Zbarsky
• Re: HTMLCollection item() vs. namedItem() with [] syntax (detailed review of the DOM) Garrett Smith

Friday, 25 July 2008

• Re: "The html element" (detailed review of the DOM) Ian Hickson
• Re: document.body (detailed review of the DOM) Ian Hickson
• [Bug 5899] New: Allow uppercase "CHARSET=" in legacy encoding decl bugzilla@wiggum.w3.org
• [Bug 5898] New: Don't convert attributes to lowercase for localName/nodeName bugzilla@wiggum.w3.org
• [Bug 5897] New: Make &ohm; and &angst; expand to their NFC equivalents bugzilla@wiggum.w3.org
• Re: Order of nodes from getElementsByClassName Ian Hickson
• Re: Case-insensitive comparison (part of my detailed review of tokenization) Ian Hickson
• Re: Workers Ian Hickson
• Re: Workers Jonas Sicking

Thursday, 24 July 2008

• RE: Request for PFWG WAI review of @summary for tabular data Chris Wilson
• Re: <object> content-type sniffing (detailed review of Semantics) Ian Hickson
• Re: What <object> represents in different views (detailed review of Semantics) Ian Hickson
• Re: <object> content-type sniffing (detailed review of Semantics) Ian Hickson
• Re: Removing the data attribute on <object> (detailed review of Semantics) Ian Hickson
• SVGWG SVG-in-HTML proposal (Was: ISSUE-41: Decentralized extensibility) Ian Hickson
• Re: linking work on processing WAI-ARIA markup in HTML Ian Hickson
• Re: linking work on processing WAI-ARIA markup in HTML Richard Schwerdtfeger
• Re: linking work on processing WAI-ARIA markup in HTML Al Gilman
• Re: ISSUE-41: Decentralized extensibility Erik Dahlström
• Re: ISSUE-37: RE: SVG in HTML proposal Erik Dahlström
• Re: Request for PFWG WAI review of @summary for tabular data Al Gilman
• Re: Doctype on text/html Pages (Was: [author-guide] Character Entity References Chart) Philip TAYLOR (Ret'd)
• Re: linking work on processing WAI-ARIA markup in HTML Sam Kuper
• Re: Doctype on text/html Pages (Was: [author-guide] Character Entity References Chart) Patrick Garies
• Re: linking work on processing WAI-ARIA markup in HTML James Graham
• Re: [whatwg] Handling of HTTP response codes for <embed>, was: <embed> feedback Ian Hickson
• Handling of HTTP response codes for <embed>, was: [whatwg] <embed> feedback Julian Reschke
• [Bug 5895] New: Require attributes on <embed> and data-* attributes to be lowercase bugzilla@wiggum.w3.org
• Re: On ISSUE-41: Decentralized extensibility Julian Reschke
• Re: ISSUE-37: RE: SVG in HTML proposal Cameron McCormack

Wednesday, 23 July 2008

• Re: ISSUE-37: RE: SVG in HTML proposal Jeff Schiller
• RE: ISSUE-37: RE: SVG in HTML proposal Chris Wilson
• Re: ISSUE-37: RE: SVG in HTML proposal Jeff Schiller
• Re: ***DHSPAM*** Re: linking work on processing WAI-ARIA markup in HTML Ian Hickson
• RE: Request for PFWG WAI review of @summary for tabular data Chris Wilson
• ISSUE-37: RE: SVG in HTML proposal Chris Wilson
• RE: On ISSUE-41: Decentralized extensibility Chris Wilson
• Re: linking work on processing WAI-ARIA markup in HTML Richard Schwerdtfeger
• Re: linking work on processing WAI-ARIA markup in HTML Ian Hickson
• Re: Doctype on text/html Pages (Was: [author-guide] Character Entity References Chart) Thomas Broyer
• Re: Doctype on text/html Pages (Was: [author-guide] Character Entity References Chart) Smylers
• Re: Doctype on text/html Pages (Was: [author-guide] Character Entity References Chart) Thomas Broyer
• Re: Doctype on text/html Pages (Was: [author-guide] Character Entity References Chart) Julian Reschke
• Re: Doctype on text/html Pages (Was: [author-guide] Character Entity References Chart) Robert J Burns
• linking work on processing WAI-ARIA markup in HTML Al Gilman
• Re: Doctype on text/html Pages (Was: [author-guide] Character Entity References Chart) Julian Reschke
• Re: Doctype on text/html Pages (Was: [author-guide] Character Entity References Chart) Robert J Burns
• Re: Doctype on text/html Pages (Was: [author-guide] Character Entity References Chart) Philip Taylor (Webmaster)
• Re: Doctype on text/html Pages (Was: [author-guide] Character Entity References Chart) Robert J Burns
• Re: Doctype on text/html Pages (Was: [author-guide] Character Entity References Chart) Henri Sivonen
• Proposal: Worker Threads and Synchronous DB API mikko.honkala@nokia.com
• Re: Doctype on text/html Pages (Was: [author-guide] Character Entity References Chart) Julian Reschke
• Re: Doctype on text/html Pages (Was: [author-guide] Character Entity References Chart) Michael A. Puls II

Tuesday, 22 July 2008

• Re: Doctype on text/html Pages (Was: [author-guide] Character Entity References Chart) Robert J Burns
• Re: Doctype on text/html Pages (Was: [author-guide] Character Entity References Chart) Julian Reschke
• Re: Doctype on text/html Pages (Was: [author-guide] Character Entity References Chart) Robert J Burns
• Re: Doctype on text/html Pages (Was: [author-guide] Character Entity References Chart) Julian Reschke
• Re: Doctype on text/html Pages (Was: [author-guide] Character Entity References Chart) Robert J Burns
• Re: Doctype on text/html Pages (Was: [author-guide] Character Entity References Chart) Smylers
• Re: Unsupported transport-layer encodings Alexey Proskuryakov
• Re: Charset usage data Alexey Proskuryakov
• Re: [author-guide] Character Entity References Chart Robert J Burns
• Re: [author-guide] Character Entity References Chart Jirka Kosek
• Re: [author-guide] Character Entity References Chart Henri Sivonen
• Re: [author-guide] Character Entity References Chart Henri Sivonen
• Re: [author-guide] Character Entity References Chart Robert J Burns
• Re: [author-guide] Character Entity References Chart Jirka Kosek
• Re: [author-guide] Character Entity References Chart Henri Sivonen
• Re: [author-guide] Character Entity References Chart Jirka Kosek
• Re: [author-guide] Character Entity References Chart Henri Sivonen
• Re: Workers Andrew Fedoniouk
• Re: [author-guide] Character Entity References Chart Robert J Burns
• Re: ISSUE-41: Decentralized extensibility Ian Hickson
• RE: Workers Justin James
• RE: Workers Justin James
• Re: ISSUE-41: Decentralized extensibility Doug Schepers
• Re: [author-guide] Character Entity References Chart Lachlan Hunt
• Re: [author-guide] Character Entity References Chart Karl Dubost

Monday, 21 July 2008

• Re: [author-guide] Character Entity References Chart Geoffrey Sneddon
• Re: ISSUE-41: Decentralized extensibility Ian Hickson
• Re: ISSUE-41: Decentralized extensibility Doug Schepers
• Re: Workers Andrew Fedoniouk
• RE: On ISSUE-41: Decentralized extensibility Chris Wilson
• RE: Workers Justin James
• [Bug 5883] New: data: URLs bugzilla@wiggum.w3.org
• Re: On ISSUE-41: Decentralized extensibility Smylers
• Re: [author-guide] Character Entity References Chart Robert J Burns
• Re: [author-guide] Character Entity References Chart Lachlan Hunt
• Re: SVG in HTML proposal Henri Sivonen
• Re: [author-guide] Character Entity References Chart Robert J Burns
• Re: [author-guide] Character Entity References Chart Olivier GENDRIN
• Re: [author-guide] Character Entity References Chart Lachlan Hunt
• Re: On ISSUE-41: Decentralized extensibility Thomas Broyer

Sunday, 20 July 2008

• Re: [author-guide] Character Entity References Chart Dean Edridge
• Re: [author-guide] Character Entity References Chart Dean Edridge

Monday, 21 July 2008

• RE: On ISSUE-41: Decentralized extensibility Chris Wilson
• Re: Workers Ian Hickson

Sunday, 20 July 2008

• Re: Workers Andrew Fedoniouk
• Re: Workers Andrew Fedoniouk
• Re: Workers Ian Hickson
• Re: Workers James Graham
• Re: Workers Andrew Fedoniouk
• Re: [author-guide] Character Entity References Chart Julian Reschke
• Re: [author-guide] Character Entity References Chart Geoffrey Sneddon
• Re: [author-guide] Character Entity References Chart Karl Dubost
• Re: [author-guide] Character Entity References Chart Julian Reschke
• Re: [author-guide] Character Entity References Chart Julian Reschke
• Re: [author-guide] Character Entity References Chart Lachlan Hunt
• Re: [author-guide] Character Entity References Chart Julian Reschke
• Re: [author-guide] Character Entity References Chart Charles McCathieNevile
• Re: Workers Ian Hickson
• Re: Workers Andrew Fedoniouk
• RE: Workers Ian Hickson
• Re: Workers Ian Hickson
• RE: Workers Justin James
• Re: Workers Andrew Fedoniouk
• Re: Workers Ian Hickson
• Re: Workers Andrew Fedoniouk
• Re: Workers Ian Hickson

Saturday, 19 July 2008

• Re: Workers Andrew Fedoniouk
• [author-guide] Character Entity References Chart Lachlan Hunt
• Re: Workers Ian Hickson
• Re: Workers Andrew Fedoniouk

Friday, 18 July 2008

• [Bug 5881] New: Make tokeniser data states headers visible in table of contents bugzilla@wiggum.w3.org
• Re: Workers Ian Hickson
• RE: Workers Ian Hickson
• Re: Workers Andrew Fedoniouk
• RE: Workers Justin James
• Re: Workers Ian Hickson
• Re: On ISSUE-41: Decentralized extensibility Julian Reschke
• Re: SVG in HTML proposal Andrew Sidwell

Thursday, 17 July 2008

• Re: On ISSUE-41: Decentralized extensibility Robert J Burns
• Re: Fwd: New Version Notification for draft-nottingham-http-link-header-02 Jonathan Rees
• Re: SVG in HTML proposal Doug Schepers
• ISSUE-57 (Joshue): @headers [HTML 5 spec] HTML Issue Tracking Issue Tracker
• Re: SVG in HTML proposal Erik Dahlström
• Re: SVG in HTML proposal Dan Connolly
• Re: SVG in HTML proposal Toby A Inkster
• Re: On ISSUE-41: Decentralized extensibility Peter Krantz
• Re: On ISSUE-41: Decentralized extensibility Philip TAYLOR (Ret'd)
• Re: On ISSUE-41: Decentralized extensibility Thomas Broyer
• On ISSUE-41: Decentralized extensibility Chris Wilson

Wednesday, 16 July 2008

• RE: example with source code -- several responses Dailey, David P.
• Re: example with source code Thomas Broyer
• Re: example with source code Frank Palinkas
• Re: example with source code Ben 'Cerbera' Millard

Tuesday, 15 July 2008

• Re: SVG in HTML proposal Jeff Schiller
• Re: SVG in HTML proposal Robin Berjon
• Re: SVG in HTML proposal Robin Berjon
• Re: example with source code Lee Kowalkowski
• Re: SVG in HTML proposal Erik Dahlström
• Re: SVG in HTML proposal Doug Schepers

Monday, 14 July 2008

• Re: SVG in HTML proposal Robin Berjon

Tuesday, 15 July 2008

• Re: example with source code Ian Hickson
• Re: SVG in HTML proposal Jeff Schiller
• RE: SVG in HTML proposal Dailey, David P.

Monday, 14 July 2008

• Re: example with source code Anne van Kesteren
• [Bug 5866] New: SVG in HTML bugzilla@wiggum.w3.org
• Re: SVG in HTML proposal Andrew Sidwell
• SVG in HTML proposal Erik Dahlström
• example with source code Dailey, David P.

Sunday, 13 July 2008

• [Bug 5863] New: Tokeniser: "Bogus comment" state unclear bugzilla@wiggum.w3.org

Saturday, 12 July 2008

• Re: [imps] content type sniffing - stream length Ian Hickson
• Re: [imps] content type sniffing - unknown type Ian Hickson
• [Bug 5859] New: Spec doesn't handle unknown schemes bugzilla@wiggum.w3.org
• content type sniffing - stream length Ryan King
• content type sniffing - unknown type Ryan King

Friday, 11 July 2008

• [Bug 5858] New: Case marked as fragment when it can occur at other times bugzilla@wiggum.w3.org
• [Bug 5856] New: height/width DOM attributes in combination with display:none bugzilla@wiggum.w3.org

Thursday, 10 July 2008

• Re: HTMLCollection item() vs. namedItem() with [] syntax (detailed review of the DOM) Garrett Smith
• [Bug 5852] New: Incorporate Entity Reference Table into Authoring Guide bugzilla@wiggum.w3.org
• Re: Workers Maciej Stachowiak
• Re: HTMLCollection item() vs. namedItem() with [] syntax (detailed review of the DOM) Cameron McCormack
• [Bug 5851] New: Consider adding .toArray() on NodeList and HTMLCollection bugzilla@wiggum.w3.org
• [Bug 5850] New: JS global object bugzilla@wiggum.w3.org
• Re: HTMLCollection item() vs. namedItem() with [] syntax (detailed review of the DOM) Ian Hickson
• RE: Workers Justin James
• Re: Workers Andrew Fedoniouk
• Workers Ian Hickson

Wednesday, 9 July 2008

• [Bug 5848] New: Write the "fetching" section bugzilla@wiggum.w3.org
• Web sockets: typo Anne van Kesteren
• [Bug 5846] New: Accessing Object Parameters from an Embedded SVG bugzilla@wiggum.w3.org
• Re: Cross-posting etiquette Ian Hickson
• Re: Cross-posting etiquette Charles McCathieNevile
• Re: Error handling for SVG and MathML in HTML Charles McCathieNevile

Tuesday, 8 July 2008

• Re: ProgressEvent and unreachable networkState LOADED in HTMLMediaElement Ian Hickson
• Re: the "HTML URL" issue, was: Why Microsoft's authoritative=true won't work and is a bad idea Roy T. Fielding
• RE: Why Microsoft's authoritative=true won't work and is a bad idea Chris Wilson
• Re: any error-free web pages at all? [was: Why Microsoft's authoritative=true won't work and is a bad idea] T.V Raman
• Re: the "HTML URL" issue Anne van Kesteren
• Re: the "HTML URL" issue, was: Why Microsoft's authoritative=true won't work and is a bad idea Stefan Eissing
• RE: the "HTML URL" issue, was: Why Microsoft's authoritative=true won't work and is a bad idea Justin James
• Re: URI/IRI vs HTML-URL, was: Why Microsoft's authoritative=true won't work and is a bad idea Robert J Burns
• Re: the "HTML URL" issue, was: Why Microsoft's authoritative=true won't work and is a bad idea Stefan Eissing
• Re: URI/IRI vs HTML-URL, was: Why Microsoft's authoritative=true won't work and is a bad idea Julian Reschke
• Re: URI/IRI vs HTML-URL, was: Why Microsoft's authoritative=true won't work and is a bad idea Martin Duerst
• Re: websocket HTTP response parsing Julian Reschke
• Re: Why Microsoft's authoritative=true won't work and is a bad idea Julian Reschke
• the "HTML URL" issue, was: Why Microsoft's authoritative=true won't work and is a bad idea Julian Reschke
• Re: Why Microsoft's authoritative=true won't work and is a bad idea Karl Dubost

Monday, 7 July 2008

• Re: Why Microsoft's authoritative=true won't work and is a bad idea Henrik Nordstrom
• RE: Why Microsoft's authoritative=true won't work and is a bad idea Henrik Nordstrom
• Re: Why Microsoft's authoritative=true won't work and is a bad idea Boris Zbarsky
• Re: any error-free web pages at all? [was: Why Microsoft's authoritative=true won't work and is a bad idea] Philip TAYLOR (Ret'd)
• RE: Why Microsoft's authoritative=true won't work and is a bad idea Justin James
• Re: Why Microsoft's authoritative=true won't work and is a bad idea Henrik Nordstrom
• RE: Why Microsoft's authoritative=true won't work and is a bad idea Henrik Nordstrom
• any error-free web pages at all? [was: Why Microsoft's authoritative=true won't work and is a bad idea] Dan Connolly
• Re: Why Microsoft's authoritative=true won't work and is a bad idea Ian Hickson
• [Bug 5839] New: Work on Worker Threads bugzilla@wiggum.w3.org
• Re: websocket HTTP response parsing Ian Hickson
• Re: websocket HTTP response parsing Julian Reschke
• Re: websocket HTTP response parsing Ian Hickson
• Re: Why Microsoft's authoritative=true won't work and is a bad idea Boris Zbarsky
• Re: Why Microsoft's authoritative=true won't work and is a bad idea Philip Taylor
• Re: Why Microsoft's authoritative=true won't work and is a bad idea Dave Singer
• Re: Why Microsoft's authoritative=true won't work and is a bad idea Julian Reschke
• Re: Why Microsoft's authoritative=true won't work and is a bad idea Dave Singer
• Re: Why Microsoft's authoritative=true won't work and is a bad idea Julian Reschke
• Re: Why Microsoft's authoritative=true won't work and is a bad idea Dave Singer
• URI/IRI vs HTML-URL, was: Why Microsoft's authoritative=true won't work and is a bad idea Julian Reschke
• RE: Why Microsoft's authoritative=true won't work and is a bad idea Justin James
• Re: Why Microsoft's authoritative=true won't work and is a bad idea Henrik Nordstrom
• Re: websocket HTTP response parsing Julian Reschke
• Re: Why Microsoft's authoritative=true won't work and is a bad idea Robert J Burns
• Re: websocket HTTP response parsing Ian Hickson
• Re: websocket HTTP response parsing Julian Reschke
• Re: Why Microsoft's authoritative=true won't work and is a bad idea Ian Hickson
• Re: websocket HTTP response parsing Ian Hickson
• Re: Why Microsoft's authoritative=true won't work and is a bad idea Julian Reschke
• Re: websocket HTTP response parsing Julian Reschke
• Re: Why Microsoft's authoritative=true won't work and is a bad idea Sam Ruby

Sunday, 6 July 2008

• [Bug 5837] New: Rename CDATA block state to CDATA section state bugzilla@wiggum.w3.org
• Re: Why Microsoft's authoritative=true won't work and is a bad idea Ian Hickson
• Re: websocket HTTP response parsing Ian Hickson
• [Bug 5836] New: Syntax section allows <ins><p></ins> bugzilla@wiggum.w3.org
• Re: Why Microsoft's authoritative=true won't work and is a bad idea Sam Ruby
• Re: Why Microsoft's authoritative=true won't work and is a bad idea Geoffrey Sneddon
• Re: Why Microsoft's authoritative=true won't work and is a bad idea Leif Halvard Silli
• Re: Why Microsoft's authoritative=true won't work and is a bad idea Julian Reschke
• Re: Why Microsoft's authoritative=true won't work and is a bad idea Julian Reschke
• Re: Why Microsoft's authoritative=true won't work and is a bad idea Julian Reschke
• Re: websocket HTTP response parsing Julian Reschke
• Re: websocket HTTP response parsing Ian Hickson
• Re: websocket HTTP response parsing Julian Reschke
• Re: websocket HTTP response parsing Ian Hickson
• Re: Why Microsoft's authoritative=true won't work and is a bad idea Ian Hickson
• Re: Microsoft's "I mean it" content-type parameter Alfonso Martínez de Lizarrondo
• Re: Why Microsoft's authoritative=true won't work and is a bad idea Sam Ruby
• Re: Why Microsoft's authoritative=true won't work and is a bad idea Ian Hickson
• RE: Microsoft's "I mean it" content-type parameter Eric Lawrence

Saturday, 5 July 2008

• Re: Why Microsoft's authoritative=true won't work and is a bad idea Sam Ruby
• Re: Why Microsoft's authoritative=true won't work and is a bad idea Ian Hickson
• Re: Why Microsoft's authoritative=true won't work and is a bad idea Sam Ruby
• Re: Why Microsoft's authoritative=true won't work and is a bad idea Ian Hickson
• Re: Why Microsoft's authoritative=true won't work and is a bad idea Boris Zbarsky
• Re: Why Microsoft's authoritative=true won't work and is a bad idea Sam Ruby
• [Bug 5835] New: no apparent mechanism for applying a caption to a fieldset bugzilla@wiggum.w3.org
• Re: Why Microsoft's authoritative=true won't work and is a bad idea Julian Reschke
• Why Microsoft's authoritative=true won't work and is a bad idea Ian Hickson

Friday, 4 July 2008

• Re: ISSUE-54 (html5-doctype-vs-xslt): XSLT 1.0 can not generate HTML5 documents [HTML 5 spec] Jirka Kosek
• [Bug 5834] New: provide normative advice on area element text alternative bugzilla@wiggum.w3.org
• Re: Microsoft's "I mean it" content-type parameter Dave Singer
• Re: Microsoft's "I mean it" content-type parameter James Graham
• Re: Microsoft's "I mean it" content-type parameter Sam Ruby
• Re: Namespace dispatching in XHTML, XML Jamie Lokier
• Re: Microsoft's "I mean it" content-type parameter Jamie Lokier

Thursday, 3 July 2008

• Re: Microsoft's "I mean it" content-type parameter Jamie Lokier
• Re: Microsoft's "I mean it" content-type parameter Jamie Lokier
• Re: Microsoft's "I mean it" content-type parameter Jamie Lokier

Friday, 4 July 2008

• RE: Microsoft's "I mean it" content-type parameter Justin James
• Re: New Version Notification for draft-nottingham-http-link-header-02 Philip TAYLOR (Ret'd)
• Re: Microsoft's "I mean it" content-type parameter Michael A. Puls II
• Re: Microsoft's "I mean it" content-type parameter Patrick Garies
• RE: [whatwg] The <iframe> element and sandboxing ideas Kristof Zelechovski
• Re: Microsoft's "I mean it" content-type parameter Boris Zbarsky
• Re: Microsoft's "I mean it" content-type parameter Julian Reschke
• Re: Microsoft's "I mean it" content-type parameter Adam Barth
• Re: Microsoft's "I mean it" content-type parameter Julian Reschke
• Re: Microsoft's "I mean it" content-type parameter Adam Barth
• Re: Microsoft's "I mean it" content-type parameter Karl Dubost
• Re: Microsoft's "I mean it" content-type parameter Adam Barth
• [Bug 5833] New: Work on ClientInformation bugzilla@wiggum.w3.org
• Re: Microsoft's "I mean it" content-type parameter William A. Rowe, Jr.
• RE: Microsoft's "I mean it" content-type parameter Justin James
• Re: Microsoft's "I mean it" content-type parameter William A. Rowe, Jr.
• RE: Microsoft's "I mean it" content-type parameter Justin James
• Re: Microsoft's "I mean it" content-type parameter Karl Dubost
• Formal survey: Web Forms Features; respond by July 10 Michael(tm) Smith

Thursday, 3 July 2008

• Namespace dispatching in XHTML, XML Mark Baker
• Re: Microsoft's "I mean it" content-type parameter Henrik Nordstrom
• Re: Microsoft's "I mean it" content-type parameter Lachlan Hunt
• Re: Microsoft's "I mean it" content-type parameter L. David Baron
• Re: Microsoft's "I mean it" content-type parameter Ian Hickson
• Re: New Version Notification for draft-nottingham-http-link-header-02 Leif Halvard Silli
• Re: Microsoft's "I mean it" content-type parameter John Kemp
• Re: New Version Notification for draft-nottingham-http-link-header-02 Henri Sivonen
• RE: Microsoft's "I mean it" content-type parameter Sam Ruby
• Re: Microsoft's "I mean it" content-type parameter William A. Rowe, Jr.
• Re: Microsoft's "I mean it" content-type parameter William A. Rowe, Jr.
• Re: Microsoft's "I mean it" content-type parameter Roy T. Fielding
• Re: Microsoft's "I mean it" content-type parameter Julian Reschke
• Re: [whatwg] The <iframe> element and sandboxing ideas Collin Jackson
• Re: who owns link relations, was: New Version Notification for draft-nottingham-http-link-header-02 Mark Baker
• RE: who owns link relations, was: New Version Notification for draft-nottingham-http-link-header-02 Justin James
• who owns link relations, was: New Version Notification for draft-nottingham-http-link-header-02 Julian Reschke
• Re: Microsoft's "I mean it" content-type parameter Julian Reschke
• Re: New Version Notification for draft-nottingham-http-link-header-02 Anne van Kesteren
• Re: websocket HTTP response parsing Julian Reschke
• Re: Microsoft's "I mean it" content-type parameter Dave Singer
• Re: websocket HTTP response parsing Ian Hickson
• Re: Microsoft's "I mean it" content-type parameter Julian Reschke
• RE: websocket HTTP response parsing Justin James
• Re: Microsoft's "I mean it" content-type parameter Dave Singer
• RE: Microsoft's "I mean it" content-type parameter Justin James
• RE: Microsoft's "I mean it" content-type parameter Daniel Stenberg
• RE: Microsoft's "I mean it" content-type parameter Justin James
• Re: New Version Notification for draft-nottingham-http-link-header-02 Sam Ruby
• notations of link relation names, was: New Version Notification for draft-nottingham-http-link-header-02 Julian Reschke
• Re: New Version Notification for draft-nottingham-http-link-header-02 Mark Baker
• Re: New Version Notification for draft-nottingham-http-link-header-02 Julian Reschke
• Re: Microsoft's "I mean it" content-type parameter Julian Reschke
• Re: New Version Notification for draft-nottingham-http-link-header-02 Julian Reschke
• Re: New Version Notification for draft-nottingham-http-link-header-02 Anne van Kesteren
• Re: New Version Notification for draft-nottingham-http-link-header-02 Mark Nottingham
• Re: Fwd: New Version Notification for draft-nottingham-http-link-header-02 Anne van Kesteren
• Re: Fwd: New Version Notification for draft-nottingham-http-link-header-02 Phil Archer
• Re: websocket HTTP response parsing Julian Reschke
• Re: websocket HTTP response parsing Ian Hickson
• websocket HTTP response parsing Julian Reschke
• [Bug 5831] New: mark up constructors in IDL bugzilla@wiggum.w3.org
• [Bug 5830] New: Work on video bugzilla@wiggum.w3.org
• RE: [whatwg] The <iframe> element and sandboxing ideas Kristof Zelechovski
• Re: Microsoft's "I mean it" content-type parameter Julian Reschke
• Re: Microsoft's "I mean it" content-type parameter William A. Rowe, Jr.
• Fwd: New Version Notification for draft-nottingham-http-link-header-02 Mark Nottingham

Wednesday, 2 July 2008

• Re: Microsoft's "I mean it" content-type parameter Julian Reschke
• Microsoft's "I mean it" content-type parameter Julian Reschke
• Re: [whatwg] The <iframe> element and sandboxing ideas Mike Ter Louw

Last message date: Thursday, 31 July 2008 23:56:46 UTC