Tuesday, 31 July 2007
- Re: Reality Check: Bi-polar Accessibility Disorder (BAD)
- Re: Formal Recorded Complaint
- Re: Lack of AT implementors participation (was Comments on IRC log)
- Re: Lack of AT implementors participation (was Comments on IRC log)
- Re: Formal Recorded Complaint
- Re: ID Characters (was: Re: 3.4. Global attributes)
- Re: Lack of AT implementors participation (was Comments on IRC log)
- Re: Lack of AT implementors participation (was Comments on IRC log)
- Re: ID Characters (was: Re: 3.4. Global attributes)
- Reality Check: Bi-polar Accessibility Disorder (BAD)
- Re: 3.12.8 dfn automatic cross-referencing
- ID Characters (was: Re: 3.4. Global attributes)
- Re: Formal Recorded Complaint
- including sufficient authoring norms in the draft
- Re: 3.5.2. Focus
- Re: Formal Recorded Complaint
- Re: HTML 5 proposal - OBJECT elements, environment discovery and alternative content
- Re: ToolTips: bug or feature?
- Re: <table presentation="pie">
- HTML 5 proposal - OBJECT elements, environment discovery and alternative content
- Re: ToolTips: bug or feature?
- Re: Formal Recorded Complaint
- Re: conflation of issues or convergence of interests?
- Re: 3.12.8 dfn automatic cross-referencing
- Re: Use Cases for The <canvas> Element
- 3.12.8 dfn automatic cross-referencing
- Re: ToolTips: bug or feature?
- Re: ToolTips: bug or feature?
- Re: Use Cases for The <canvas> Element
- Re: Marking up links to alternative versions of content (was: Re: conflation of issues or convergence of interests?)
- <table presentation="pie"> (was: Re: <table chart="pie">)
- Re[2]: <table presentation="pie"> (was: Re: <table chart="pie">)
- Re[2]: popularization of Unicode (was: Re[4]: guessing character encoding (was HTML WG))
- Re: Patterns for explicit associations Re: conflation of issues or convergence of interests?
- Namespace declarations in application/xhtml+xml (Re: 3.6. The root element)
- Re: 3.4. Global attributes
- RE: Accesskey - spec proposal
- Re: CR and LF in the input stream / as NCRs (detailed review of parsing algorithm)
- Re: conflation of issues or convergence of interests?
- Re: 3.6. The root element
- Re: 3.6. The root element
- Re: 3.6. The root element
- 3.5.2. Focus
- Re: The title Attribute (Was: conflation of issues or convergence of interests?)
- Re: 3.6. The root element
- Re: 3.6. The root element
- Re: 3.6. The root element
- Re: lang and xml:lang Re: 3.4. Global attributes
- Re: lang and xml:lang Re: 3.4. Global attributes
- Re: 3.6. The root element
- Re: ToolTips: bug or feature?
- Re: 3.4. Global attributes
- Downloading of images by UA
- Re: lang and xml:lang Re: 3.4. Global attributes
- Re: ToolTips: bug or feature?
- Re: ToolTips: bug or feature?
- Re: ToolTips: bug or feature?
- Re: The title Attribute (Was: conflation of issues or convergence of interests?)
- Re: authoring @lang (was 3.6. The root element)
- Re: authoring @lang (was 3.6. The root element)
- Re: authoring @lang (was 3.6. The root element)
- Re: Lack of AT implementors participation (was Comments on IRC log)
- Re: Marking up links to alternative versions of content (was: Re: conflation of issues or convergence of interests?)
- Re: Lack of AT implementors participation (was Comments on IRC log)
- Re: conflation of issues or convergence of interests?
- Re: Lack of AT implementors participation (was Comments on IRC log)
- Re: Marking up links to alternative versions of content
- Re: ToolTips: bug or feature?
- Re: conflation of issues or convergence of interests?
- Re: Formal Recorded Complaint
- Patterns for explicit associations Re: conflation of issues or convergence of interests?
- Re: authoring @lang (was 3.6. The root element)
- Re: addition or subtrraction? [was Re: dropping longdesc attribute]
- Re: authoring @lang (was 3.6. The root element)
- lang and xml:lang Re: 3.4. Global attributes
- Re: authoring @lang (was 3.6. The root element)
- Re: conflation of issues or convergence of interests?
- Re: Use Cases for The <canvas> Element
- Re: conflation of issues or convergence of interests?
- Re: 3.4. Global attributes
- Re: Formal Recorded Complaint
- Re: Use Cases for The <canvas> Element
- Re: Marking up links to alternative versions of content (was: Re: conflation of issues or convergence of interests?)
- Re: Lack of AT implementors participation (was Comments on IRC log)
- Re: CR and LF in the input stream / as NCRs (detailed review of parsing algorithm)
- Re: ToolTips: bug or feature?
- Re: ToolTips: bug or feature?
- Re: Use Cases for The <canvas> Element
- CR and LF in the input stream / as NCRs (detailed review of parsing algorithm)
- RE: Formal Recorded Complaint
- Re: Formal Recorded Complaint
Monday, 30 July 2007
- html5 nitpicks
- Re: Formal Recorded Complaint
- Re: Use Cases for The <canvas> Element
- Re: Formal Recorded Complaint
- Re: Formal Recorded Complaint
- Re: Use Cases for The <canvas> Element
- Being respectful in HTML WG
- Re: ToolTips: bug or feature?
- Re: ToolTips: bug or feature?
- Re: Formal Recorded Complaint
- Re: ToolTips: bug or feature?
- Re: Use Cases for The <canvas> Element
- Re: ToolTips: bug or feature?
- Re: Formal Recorded Complaint
- Re: Formal Recorded Complaint
- Re: Use Cases for The <canvas> Element
- Re: ToolTips: bug or feature?
- Re: Formal Recorded Complaint
- Re: Formal Recorded Complaint
- RE: Formal Recorded Complaint
- Re: Formal Recorded Complaint
- Re: Formal Recorded Complaint
- Re: Use Cases for The <canvas> Element
- Re: Formal Recorded Complaint
- Re: Formal Recorded Complaint
- Re: Use Cases for The <canvas> Element
- Re: Formal Recorded Complaint
- Re: ToolTips: bug or feature?
- Re: Formal Recorded Complaint
- Re: 3.6. The root element
- 3.14.x Medias
- Re: Formal Recorded Complaint
- Re: ToolTips: bug or feature?
- Re: ToolTips: bug or feature?
- Re: Use Cases for The <canvas> Element
- Re: ToolTips: bug or feature?
- Element-specific attributes
- 3.7. Document metadata
- Re: <table chart="pie">
- Re: ToolTips: bug or feature?
- Re: 3.6. The root element
- Re: 3.6. The root element
- Re: 3.6. The root element
- Re: 3.6. The root element
- Re: 3.6. The root element
- Re: conflation of issues or convergence of interests?
- Re: 3.6. The root element
- Re: 3.6. The root element
- 3.6. The root element
- Re: 3.4. Global attributes
- Re: ToolTips: bug or feature?
- 3.4. Global attributes
- Re: Use Cases for The <canvas> Element
- Re: 3.2. Common microsyntaxes
- Re: 3.2. Common microsyntaxes
- <figure><object> content model (detailed review of Semantics)
- Re: <table chart="pie">
- Marking up links to alternative versions of content (was: Re: conflation of issues or convergence of interests?)
- Re: ToolTips: bug or feature?
- Re: ToolTips: bug or feature?
- Re: conflation of issues or convergence of interests?
- Re: ToolTips: bug or feature?
- Re: unifying alternate content across embedded content element types
- Re: Lack of AT implementors participation (was Comments on IRC log)
- Re: unifying alternate content across embedded content element types
- Re: <table chart="pie">
- Re: Lack of AT implementors participation (was Comments on IRC log)
- Re: ToolTips: bug or feature?
- Re: Use Cases for The <canvas> Element
- Re: Use Cases for The <canvas> Element
- Re: conflation of issues or convergence of interests?
- Re: Use Cases for The <canvas> Element
- Re: Lack of AT implementors participation (was Comments on IRC log)
- Re: ToolTips: bug or feature?
- Re: conflation of issues or convergence of interests?
- Re: Use Cases for The <canvas> Element
- Re: conflation of issues or convergence of interests?
- Re: conflation of issues or convergence of interests?
- Re: conflation of issues or convergence of interests?
- Re: conflation of issues or convergence of interests?
Sunday, 29 July 2007
- Re: Lack of AT implementors participation (was Comments on IRC log)
- Re: ToolTips: bug or feature?
- Re: Use Cases for The <canvas> Element
- Re: Use Cases for The <canvas> Element
- Re: ToolTips: bug or feature?
- Re: Use Cases for The <canvas> Element
- Re: ToolTips: bug or feature?
- Re: Use Cases for The <canvas> Element
- Re: ToolTips: bug or feature?
- Re: Use Cases for The <canvas> Element
- Re: 3.1. Introduction (Semantics and structure of HTML elements)
- Re: Use Cases for The <canvas> Element
- Re: conflation of issues or convergence of interests?
- Use Cases for The <canvas> Element
- RE: conflation of issues or convergence of interests?
- ToolTips: bug or feature?
- Re: 3.2. Common microsyntaxes
- Re: Title and Alt Attributes (was: Re: conflation of issues or convergence of interests?)
- 3.3. Documents and document fragments
- 3.2. Common microsyntaxes
- 3.1. Introduction (Semantics and structure of HTML elements)
- Re: conflation of issues or convergence of interests?
- Re: conflation of issues or convergence of interests?
- RE: conflation of issues or convergence of interests?
- Re: conflation of issues or convergence of interests?
- Re: conflation of issues or convergence of interests?
- Re: conflation of issues or convergence of interests?
- Re: conflation of issues or convergence of interests?
- Re: conflation of issues or convergence of interests?
- Re: conflation of issues or convergence of interests?
- Re: conflation of issues or convergence of interests?
- Re: conflation of issues or convergence of interests?
- Re: conflation of issues or convergence of interests?
- Re: conflation of issues or convergence of interests?
Saturday, 28 July 2007
- Re: conflation of issues or convergence of interests?
- Re: conflation of issues or convergence of interests?
- Re: conflation of issues or convergence of interests?
- Re: conflation of issues or convergence of interests?
- Tokeniser meta-implementation
- Re: conflation of issues or convergence of interests?
- Re: conflation of issues or convergence of interests?
- Re: conflation of issues or convergence of interests?
- Re: conflation of issues or convergence of interests?
- Re: conflation of issues or convergence of interests?
- Re: unifying alternate content across embedded content element types
- Re: conflation of issues or convergence of interests?
- Re: conflation of issues or convergence of interests?
- Re: conflation of issues or convergence of interests?
- Re: conflation of issues or convergence of interests?
- Re: conflation of issues or convergence of interests?
- Re: conflation of issues or convergence of interests?
- Re: conflation of issues or convergence of interests?
- Re: conflation of issues or convergence of interests?
- Re: conflation of issues or convergence of interests?
- Re: conflation of issues or convergence of interests?
- Re: conflation of issues or convergence of interests?
- Re: conflation of issues or convergence of interests?
- Re: conflation of issues or convergence of interests?
- Re: conflation of issues or convergence of interests?
- Re: unifying alternate content across embedded content element types
- Re: conflation of issues or convergence of interests?
- Re: <table chart="pie">
- Re: <object data type> when type is unsupported (detailed review of Semantics)
- Re: <table chart="pie">
Friday, 27 July 2007
- Re: Comments on IRC log
- Re: Lack of AT implementors participation (was Comments on IRC log)
- Re: <object data type> when type is unsupported (detailed review of Semantics)
Thursday, 26 July 2007
Friday, 27 July 2007
- <object data type> when type is unsupported (detailed review of Semantics)
- Re: conflation of issues or convergence of interests?
- conflation of issues or convergence of interests?
- Re: Comments on IRC log
- Re: <input type="rgb" value="110 120 130">
- Re: <input type="percent" value="40">
- <input type="rgb" value="110 120 130">
- <table chart="pie">
- Re[2]: <pages> <page>...<page> </pages>
- popularization of Unicode (was: Re[4]: guessing character encoding (was HTML WG))
- Re[2]: <meta name=register>, Browser as passive tool
- <input type="percent" value="40">
- Re: (code, sample output and keyboard/device input <code>, <samp>, <kybd>) part of my review of 3.12 Phrase elements
- Re [3]: auto-submit form TABLE
- Re: User Testing elements of HTML 5 spec
- Re: Comments on IRC log
- Re: unifying alternate content across embedded content element types
- Re: unifying alternate content across embedded content element types
- Re: Comments on IRC log
- Re: unifying alternate content across embedded content element types (was Comments on IRC log)
- Re: unifying alternate content across embedded content element types
- Re: unifying alternate content across embedded content element types (was Comments on IRC log)
- Re: unifying alternate content across embedded content element types (was Comments on IRC log)
- Re: Comments on IRC log
Thursday, 26 July 2007
- Re: Comments on IRC log
- Detailed review of Section 1. Introduction.
- Re: (phrase extensions and bidirectional text orverride <span> and <bdo>) part of my review of 3.12 Phrase elements
- Re: (marks, definitions, terms, abbreviations, and variables <m>, <dfn>, <abbr>, <term>) part of my review of 3.12 Phrase elements
- Re: Comments on IRC log
- Formal Recorded Complaint
- Re: (phrase extensions and bidirectional text orverride <span> and <bdo>) part of my review of 3.12 Phrase elements
- Re: (marks, definitions, terms, abbreviations, and variables <m>, <dfn>, <abbr>, <term>) part of my review of 3.12 Phrase elements
- Comments on IRC log
- Re: "Canonical" HTML5 and XHTML5 output
- Re: tabindex=bogus (detailed review of Semantics)
- Re: tabindex=bogus (detailed review of Semantics)
- Re: tabindex=bogus (detailed review of Semantics)
- tabindex=bogus (detailed review of Semantics)
- Editorial: event handler attributes
- Re: "Canonical" HTML5 and XHTML5 output
- Re: "Canonical" HTML5 and XHTML5 output
Wednesday, 25 July 2007
- Are Web Applications Still a Vague Subject ?
- Re: [Whatwg] Are Web Applications Still a Vague Subject ?
- " in data when getting .innerHTML (detailed review of Serialising HTML fragments)
- <p><table> parsing (detailed review of parsing algorithm)
- Re: document.title (detailed review of the DOM)
- "The html element" (detailed review of the DOM)
- Re: "Canonical" HTML5 and XHTML5 output
Tuesday, 24 July 2007
- Re: "Canonical" HTML5 and XHTML5 output
- Re: "Canonical" HTML5 and XHTML5 output
- Re: [html5] Multiple IDs for an element?
- Re: [html5] Multiple IDs for an element?
- Re: [html5] Multiple IDs for an element?
- [html5] Multiple IDs for an element?
- "Canonical" HTML5 and XHTML5 output
- Microformats and cowpaths
- Re: Ambiguous ampersands (detailed review of Writing HTML documents)
- Re: (code, sample output and keyboard/device input <code>, <samp>, <kybd>) part of my review of 3.12 Phrase elements
- Re: Why HTML should be taught as HTML without pretending it is XML
- Re: (code, sample output and keyboard/device input <code>, <samp>, <kybd>) part of my review of 3.12 Phrase elements
- Re: (code, sample output and keyboard/device input <code>, <samp>, <kybd>) part of my review of 3.12 Phrase elements
- Re: Why HTML should be taught as HTML without pretending it is XML
- Re: Why HTML should be taught as HTML without pretending it is XML
- Re: unifying alternate content across embedded content element types
Monday, 23 July 2007
- Re: Why HTML should be taught as HTML without pretending it is XML
- Re: Why HTML should be taught as HTML without pretending it is XML
- Re: Why HTML should be taught as HTML without pretending it is XML
- Re: Why HTML should be taught as HTML without pretending it is XML
- Re: Why HTML should be taught as HTML without pretending it is XML
- Re: Why HTML should be taught as HTML without pretending it is XML
- Re: Why HTML should be taught as HTML without pretending it is XML
- Re: Why HTML should be taught as HTML without pretending it is XML
- Re: [html5] "HTML 5 differences from HTML 4" feedback
- Stray less-than signs (detailed review of parsing algorithm)
- Re: Why HTML should be taught as HTML without pretending it is XML
- Ambiguous ampersands (detailed review of Writing HTML documents)
- Re: Why HTML should be taught as HTML without pretending it is XML
- Re: Why HTML should be taught as HTML without pretending it is XML
- Re: unifying alternate content across embedded content element types
- Re: Why HTML should be taught as HTML without pretending it is XML
- Re: Why HTML should be taught as HTML without pretending it is XML
- Re: Why HTML should be taught as HTML without pretending it is XML
- Re: Why HTML should be taught as HTML without pretending it is XML
- Re: Why HTML should be taught as HTML without pretending it is XML
- Re: Why HTML should be taught as HTML without pretending it is XML
- Re: Why HTML should be taught as HTML without pretending it is XML
- (marks, definitions, terms, abbreviations, and variables <m>, <dfn>, <abbr>, <term>) part of my review of 3.12 Phrase elements
- Re: Why HTML should be taught as HTML without pretending it is XML
- Re: Why HTML should be taught as HTML without pretending it is XML
- Re: Why HTML should be taught as HTML without pretending it is XML
- Re: [html5] "HTML 5 differences from HTML 4" feedback
- Re: administrative: search letters via e-mail
- Re: <meta name=register>, Browser as passive tool
Friday, 20 July 2007
- Re: administrative: search letters via e-mail
- <meta name=register>, Browser as passive tool (was: Presentation by XML)
- Re: guessing character encoding (was HTML WG)
- Re[2]: guessing character encoding (was HTML WG)
Sunday, 22 July 2007
- Seeing the HTML5 parse tree (was: Re: handling fallback content for still images)
- Re: [html5] "HTML 5 differences from HTML 4" feedback
- (Time, Meter, Progress, DATA <time>, <meter>, <progress>, <data>, etc.) part of my review of 3.12 Phrase elements
- Re: Why HTML should be taught as HTML without pretending it is XML
- Re: Why HTML should be taught as HTML without pretending it is XML
Saturday, 21 July 2007
- Re: (code, sample output and keyboard/device input <code>, <samp>, <kybd>) part of my review of 3.12 Phrase elements
- Re: (code, sample output and keyboard/device input <code>, <samp>, <kybd>) part of my review of 3.12 Phrase elements
- Re: Why HTML should be taught as HTML without pretending it is XML
- Re: Why HTML should be taught as HTML without pretending it is XML
Friday, 20 July 2007
Saturday, 21 July 2007
- Re: (code, sample output and keyboard/device input <code>, <samp>, <kybd>) part of my review of 3.12 Phrase elements
- Re: (code, sample output and keyboard/device input <code>, <samp>, <kybd>) part of my review of 3.12 Phrase elements
Friday, 20 July 2007
- Re: Why HTML should be taught as HTML without pretending it is XML
- (phrase extensions and bidirectional text orverride <span> and <bdo>) part of my review of 3.12 Phrase elements
- Re: (code, sample output and keyboard/device input <code>, <samp>, <kybd>) part of my review of 3.12 Phrase elements
- Re: (code, sample output and keyboard/device input <code>, <samp>, <kybd>) part of my review of 3.12 Phrase elements
- Re: (code, sample output and keyboard/device input <code>, <samp>, <kybd>) part of my review of 3.12 Phrase elements
- Re: (code, sample output and keyboard/device input <code>, <samp>, <kybd>) part of my review of 3.12 Phrase elements
- Re: (code, sample output and keyboard/device input <code>, <samp>, <kybd>) part of my review of 3.12 Phrase elements
- Re: (code, sample output and keyboard/device input <code>, <samp>, <kybd>) part of my review of 3.12 Phrase elements
- On the question of compatibility
- Re: (code, sample output and keyboard/device input <code>, <samp>, <kybd>) part of my review of 3.12 Phrase elements
- Re: [html5] "draggable" attribute renaming?
- Re: (code, sample output and keyboard/device input <code>, <samp>, <kybd>) part of my review of 3.12 Phrase elements
- Re: Opening thoughts on WAI-ARIA in HTML5
- (bold, italics <b> <i>) part of my review of 3.12 Phrase elements
- (subscript, superscript: <sub> and <sup>) part of my review of 3.12 Phrase elements
- Re: part of my review of 3.12 Phrase elements (importance <strong> element)
- Re: part of my review of 3.12 Phrase elements (importance <strong> element)
- Re: (marks, definitions, terms, abbreviations, and variables <m>, <dfn>, <abbr>, <term>) part of my review of 3.12 Phrase elements
- Re: (marks, definitions, terms, abbreviations, and variables <m>, <dfn>, <abbr>, <term>) part of my review of 3.12 Phrase elements
- Re: (marks, definitions, terms, abbreviations, and variables <m>, <dfn>, <abbr>, <term>) part of my review of 3.12 Phrase elements
- Re: (marks, definitions, terms, abbreviations, and variables <m>, <dfn>, <abbr>, <term>) part of my review of 3.12 Phrase elements
- Re: (marks, definitions, terms, abbreviations, and variables <m>, <dfn>, <abbr>, <term>) part of my review of 3.12 Phrase elements
- Re: handling fallback content for still images
- Re: (marks, definitions, terms, abbreviations, and variables <m>, <dfn>, <abbr>, <term>) part of my review of 3.12 Phrase elements
- (code, sample output and keyboard/device input <code>, <samp>, <kybd>) part of my review of 3.12 Phrase elements
- Re: part of my review of 3.12 Phrase elements (importance <strong> element)
- Re: part of my review of 3.12 Phrase elements (importance <strong> element)
- Re: (marks, definitions, terms, abbreviations, and variables <m>, <dfn>, <abbr>, <term>) part of my review of 3.12 Phrase elements
- (marks, definitions, terms, abbreviations, and variables <m>, <dfn>, <abbr>, <term>) part of my review of 3.12 Phrase elements
- Re: Opening thoughts on WAI-ARIA in HTML5
- Re: Opening thoughts on WAI-ARIA in HTML5
- Re: Opening thoughts on WAI-ARIA in HTML5
- (quotations <q> and <quote>)(and <blockquote> and HTMLQuoteElement) Re: part of my review of 3.12 Phrase elements
Thursday, 19 July 2007
- Re: Opening thoughts on WAI-ARIA in HTML5
- Re: part of my review of 3.12 Phrase elements (importance <strong> element)
- Re: Why HTML should be taught as HTML without pretending it is XML
- Re: part of my review of 3.12 Phrase elements (quotations <q> and <quote>)(and <blockquote> and HTMLQuoteElement)
- Re: Why HTML should be taught as HTML without pretending it is XML
- Re: Why HTML should be taught as HTML without pretending it is XML
- Re: Opening thoughts on WAI-ARIA in HTML5
- reframe contentious 'principles'
- minutes: HTML WG teleconference 19 July (for review)
- any issues with "The XMLHttpRequest Object" 18 June draft?
- Re: part of my review of 3.12 Phrase elements (quotations <q> and <quote>)(and <blockquote> and HTMLQuoteElement)
- Re: part of my review of 3.12 Phrase elements (importance <strong> element)
- Re: part of my review of 3.12 Phrase elements (<small> small element)
- part of my review of 3.12 Phrase elements (importance <strong> element)
- part of my review of 3.12 Phrase elements (<em> emphasis element)
- part of my review of 3.12 Phrase elements (citations <cite> element)
- part of my review of 3.12 Phrase elements (quotations <q> and <quote>)(and <blockquote> and HTMLQuoteElement)
- part of my review of 3.12 Phrase elements (<a> anchor element)
- Re: Wiki page for style attribute
- Re: <pages> <page>...<page> </pages>
- Re[2]: auto-submit form TABLE
- administrative: search letters via e-mail
- Presentation by XML
- Re: Opening thoughts on WAI-ARIA in HTML5
- UA wiki page
- Re: default role values for HTML elements and built-in accessibility
- default role values for HTML elements and built-in accessibility
- Re: extracting semantics Re: Namespace
Wednesday, 18 July 2007
- Opening thoughts on WAI-ARIA in HTML5
- Re: unifying alternate content across embedded content element types
- Re: unifying alternate content across embedded content element types
- agenda: HTML WG teleconference 19 July
- Re: minutes: HTML WG 12 July for review
- minutes: HTML WG 12 July for review
- Re: 3.11 Lists Review Comments (ol/@start, li/@value)
- Re: guessing character encoding (was HTML WG)
- Re: extracting semantics Re: Namespace
- Structuralism or non-presentationalism principle (was: Re: extracting semantics)
- Re: HTMLImageElement.width / height (detailed review of Semantics)
- Re[4]: unite two space: attributes and properties
- <pages> <page>...<page> </pages>
- Re: auto-submit form TABLE
- Re[3]: unite two space: attributes and properties
- <sub> and control symbol (was Re: guessing character encoding (was HTML WG))
- Re: Two ways of development
- Re: guessing character encoding (was HTML WG)
- Re: extracting semantics Re: Namespace
- HTMLTableCellElement.colSpan and rowSpan (detailed review of Semantics)
- Re: extracting semantics Re: Namespace
- Re: extracting semantics Re: Namespace
- Re: extracting semantics Re: Namespace
- Re: extracting semantics Re: Namespace
- Re: Why HTML should be taught as HTML without pretending it is XML
- Re: Why HTML should be taught as HTML without pretending it is XML
- Re: Namespace
- Re: Why HTML should be taught as HTML without pretending it is XML
- Re: Namespace
- Character encoding errors (detailed review of parsing algorithm)
- Re: extracting semantics Re: Namespace
- Re: Namespace
- Re: Why HTML should be taught as HTML without pretending it is XML
- Re: Why HTML should be taught as HTML without pretending it is XML
- Re: 3.11 Lists Review Comments (ol/@start, li/@value)
- Re: Small print is not a good idea Re: Namespace
- Re: Small print is not a good idea Re: Namespace
- Re: extracting semantics Re: Namespace
- Re: Namespace
- Re: Namespace
- Re: Subdocument fragments in a compound document (part of detailed review of documents and document framegents)
- Re: Why HTML should be taught as HTML without pretending it is XML
- Small print is not a good idea Re: Namespace
- extracting semantics Re: Namespace
- Re: Namespace
- Re: 3.11 Lists Review Comments (ol/@start, li/@value)
- Re: unifying alternate content across embedded content element types
- Re: 3.11 Lists Review Comments (ol/@start, li/@value)
- Re: 3.11 Lists Review Comments (ol/@start, li/@value)
- Re: Namespace
Tuesday, 17 July 2007
- Re: Researching HTML usage in existing content
- Re: Namespace
- Re: Namespace
- Re: 3.11 Lists Review Comments (ol/@start, li/@value)
- Re: 3.15 Tabular Data Review
- Re: Why legend has been preferred to caption for figures (was: 3.15 Tabular Data Review)
- Why legend has been preferred to caption for figures (was: 3.15 Tabular Data Review)
- Re: 3.11 Lists Review Comments (ol/@start, li/@value)
- Re: 3.15 Tabular Data Review
- Re: boolean attributes case-sensitivity (detailed review of Semantics)
- Re: unifying alternate content across embedded content element types
- Re: 3.11 Lists Review Comments (ol/@start, li/@value)
- boolean attributes case-sensitivity (detailed review of Semantics)
- Re: unifying alternate content across embedded content element types
- RFC 2396 v. RFC 3986 v. RFC 3987 (general comment, part of detailed review of spec)
- Re: 3.15 Tabular Data Review
- Re: unifying alternate content across embedded content element types
- accessibility exercise and design principles (Re: unifying alternate content...)
- accessibility exercise and design principles (Re: unifying alternate content...)
- accessibility exercise and design principles (Re: unifying alternate content...)
- Re: 3.1 Introduction (Draft), review of
- Re: 3.15 Tabular Data Review
- Re: 3.1 Introduction (Draft), review of
- Re: Namespace
- Re: 3.11 Lists Review Comments (ol/@start, li/@value)
- Re: 3.11 Lists Review Comments
- Re: 3.11 Lists Review Comments (ol/@start, li/@value)
- Re: unifying alternate content across embedded content element types
- Subdocument fragments in a compound document (part of detailed review of documents and document framegents)
- Re: DOMTokenList.add() when the underlying string is empty (detailed review of the DOM)
- Re: Why HTML should be taught as HTML without pretending it is XML
- DOMTokenList.add() when the underlying string is empty (detailed review of the DOM)
- Re: Why HTML should be taught as HTML without pretending it is XML
- Re: 3.1 Introduction (Draft), review of
- Why HTML should be taught as HTML without pretending it is XML
- Re: 3.15 Tabular Data Review
- Re: 3.1 Introduction (Draft), review of
- Re: Improving alt (was handling fallback content for still images)
- Re: 3.1 Introduction (Draft), review of
- Re: Namespace
- Re: 3.1 Introduction (Draft), review of
- Re: 3.1 Introduction (Draft), review of
- Re: 3.1 Introduction (Draft), review of
- Re: unifying alternate content across embedded content element types
- Re: Namespace
- Re: unifying alternate content across embedded content element types
- Re: unifying alternate content across embedded content element types
- Re: Namespace
- Re: unifying alternate content across embedded content element types
- Re: unifying alternate content across embedded content element types
- Re: 3.1 Introduction (Draft), review of
- Re: 3.1 Introduction (Draft), review of
- Re: Improving alt (was handling fallback content for still images)
- Re: 3.1 Introduction (Draft), review of
Monday, 16 July 2007
- Re: @ping attribute wiki page.
- 3.11 Lists Review Comments
- Re: 3.1 Introduction (Draft)
- Re: 3.15 Tabular Data Review
- Re: 3.1 Introduction (Draft)
- Re: @ping attribute wiki page.
- Re: the style attribute
- Reflecting attributes: HTMLElement (detailed review of the DOM)
- Re: 3.1 Introduction (Draft)
- Re: Reflecting attributes: float, DOMTimeStamp (detailed review of the DOM)
- Re: Validity & Must Not/Should Not/May Not
- Reflecting attributes: boolean (detailed review of the DOM)
- Reflecting attributes: float, DOMTimeStamp (detailed review of the DOM)
- Two ways of development
- auto-submit form TABLE
- Re[2]: unite two space: attributes and properties
- Re: 3.15 Tabular Data Review
- Re: handling fallback content for still images
- Re: 3.1 Introduction (Draft)
- Re: 3.1 Introduction (Draft)
- Entities in RCDATA with escape flag (detailed review of parsing algorithm)
- Re: Namespace
- Re: Detecting support for a given HTML5 feature through JS
- Re: [whatwg] Web forms 2, input type suggestions
- Re: unifying alternate content across embedded content element types
- 3.11 Lists Review Comments
- 3.15 Tabular Data Review
- Re: Dates in HTML 5
- Re: Detecting support for a given HTML5 feature through JS
- Re: Detecting support for a given HTML5 feature through JS
- 3.11 Lists Review Comments
- Re: unifying alternate content across embedded content element types
- Re: Compatibility with XHTML2
- Re: Compatibility with XHTML2
- Re: unifying alternate content across embedded content element types
- Re: unifying alternate content across embedded content element types
- Re: Compatibility with XHTML2
Sunday, 15 July 2007
- Re: Validity & Must Not/Should Not/May Not
- Re: handling fallback content for still images
- Re: Validity & Must Not/Should Not/May Not
- Namespace
- Re: handling fallback content for still images
- Re: Compatibility with XHTML2
- Re: Validity & Must Not/Should Not/May Not
- Re: Detecting support for a given HTML5 feature through JS
- Compatibility with XHTML2
- Re: Validity & Must Not/Should Not/May Not
- Re: handling fallback content for still images
- Re: Validity & Must Not/Should Not/May Not
- Re: handling fallback content for still images
- HTMLImageElement.width / height (detailed review of Semantics)
- Re: handling fallback content for still images
- Re: Improving alt (was handling fallback content for still images)
- Researching HTML usage in existing content (was: Re: unifying alternate content across embedded content element types)
- Validity & Must Not/Should Not/May Not
- Re: Improving alt (was handling fallback content for still images)
- Detecting support for a given HTML5 feature through JS (was: Re: HTML Extensibility Through Script)
- Re: 3.1 Introduction (Draft)
- 3.1 Introduction (Draft)
- HTMLTableColElement.span being limited to only positive non-zero numbers (detailed review of Semantics)
- Re: unifying alternate content across embedded content element types
- Re: HTML Extensibility Through Script
- Re: unifying alternate content across embedded content element types
- Re: Lack Of Definition Of A Valid Ratio (part of detailed review of common microsyntaxes)
- <col> as child of <table> (detailed review of Semantics)
- Re: Lack Of Definition Of A Valid Ratio (part of detailed review of common microsyntaxes)
- Re: Using XSLT to output the HTML 5 DOCTYPE
- Re: @ping attribute wiki page.
- Re: unifying alternate content across embedded content element types
- Re: unifying alternate content across embedded content element types
- HoTMetaL doctypes should trigger quirks mode (detailed review of parsing algorithm)
- Re: <li value=bogus> (detailed review of Semantics)
- Re: <li value=bogus> (detailed review of Semantics)
- Re: unifying alternate content across embedded content element types
- longdesc semantics and optional content Re: unifying alternate ...
- Re: unifying alternate content across embedded content element types
- Re: Improving alt (was handling fallback content for still images)
- Re: unifying alternate content across embedded content element types
- Re: unifying alternate content across embedded content element types
- Re: HTML Extensibility Through Script
- Re: unifying alternate content across embedded content element types
- Re: Improving alt (was handling fallback content for still images)
- Re: unifying alternate content across embedded content element types
- Re: unifying alternate content across embedded content element types
- Re: unifying alternate content across embedded content element types
- Re: unifying alternate content across embedded content element types
- Re: unifying alternate content across embedded content element types
- Re: unifying alternate content across embedded content element types
- Re: unifying alternate content across embedded content element types
- Re: unifying alternate content across embedded content element types
- Re: unifying alternate content across embedded content element types
Saturday, 14 July 2007
- Re: Please, check subjects... and maintain threading...
- Re: [whatwg] Web forms 2, input type suggestions
- Re: Please, check subjects... and maintain threading...
- Re: Lack Of Definition Of A Valid Ratio (part of detailed review of common microsyntaxes)
- Re: unifying alternate content across embedded content element types
- Please, check subjects...
- <li value=bogus> (detailed review of Semantics)
- Re: equivalent content must not be an either/or proposition
- Re: Improving alt (was handling fallback content for still images)
- Re: stopping discussions on serializations and contributing constructively
- Re: @ping attribute wiki page.
- Re: handling fallback content for still images
- Re: Lack Of Definition Of A Valid Ratio (part of detailed review of common microsyntaxes)
- Re: unifying alternate content across embedded content element types
Friday, 13 July 2007
- Re: Improving alt (was handling fallback content for still images)
- Re: Lack Of Definition Of A Valid Ratio (part of detailed review of common microsyntaxes)
- Re: @ping attribute wiki page.
- Re: stopping discussions on serializations and contributing constructively
- Re: Lack Of Definition Of A Valid Ratio (part of detailed review of common microsyntaxes)
- Re: handling fallback content for still images
Saturday, 14 July 2007
- Re: unifying alternate content across embedded content element types
- Re: unifying alternate content across embedded content element types
- Re: unifying alternate content across embedded content element types
- Re: in body "select" not associated with the form pointer (detailed review of parsing algorithm)
- Re: equivalent content must not be an either/or proposition
- Re: unifying alternate content across embedded content element types
- Re: unifying alternate content across embedded content element types
- Re: html5 syntax - why not use xml syntax?
- Re: unifying alternate content across embedded content element types
- equivalent content must not be an either/or proposition
Friday, 13 July 2007
- Re: unifying alternate content across embedded content element types
- Re: unifying alternate content across embedded content element types
- Re: guessing character encoding (was HTML WG)
- Re: HTML Extensibility Through Script
- Re: guessing character encoding (was HTML WG)
- Re: unifying alternate content across embedded content element types
- Re: guessing character encoding (was HTML WG)
- Re: Using XSLT to output the HTML 5 DOCTYPE
- Re: Using XSLT to output the HTML 5 DOCTYPE
- Using XSLT to output the HTML 5 DOCTYPE
- Enumerated attributes limited to only known values (detailed review of Semantics)
- Re: guessing character encoding (was HTML WG)
- Re: fallback for css-file
- Re: fallback for css-file (was Re[2]: Improving alt (was handling fallback content for still images))
- Re: unifying alternate content across embedded content element types
- Two cases for end tag "br" in "in body" (detailed review of parsing algorithm)
- Re[2]: alignment of <input>-s and their pseudo-elements (was: Re: Improving alt (was handling fallback content for still images))
- Re: HTML WG
- fallback for css-file (was Re[2]: Improving alt (was handling fallback content for still images))
- Presentation by XML
- [html5] "HTML 5 differences from HTML 4" feedback
- [html5] "draggable" attribute renaming?
- Re: document.body (detailed review of the DOM)
- document.body (detailed review of the DOM)
Thursday, 12 July 2007
- Re: HTML Extensibility Through Script
- minutes: HTML WG teleconference Thu 12 July (for review)
- Re: SURVEY: Release "HTML 5 differences from HTML 4" as a W3C Working Draft? formal decision
- Re: Accessibility Advice on HTML 5 Design Principles
- Implementation + Test Cases Available For Numbers Subsection of Common Microsyntaxes
- List Of Integers repeats itself (part of detailed review of common microsyntaxes)
- Re: Accessibility Advice on HTML 5 Design Principles
- Re: HTML Extensibility Through Script
- Re: stopping discussions on serializations and contributing constructively
- Accessibility Advice on HTML 5 Design Principles
- Ratios is Stylistically Different To Other Number Algorithms (part of detailed review of common microsyntaxes)
- Re: stopping discussions on serializations and contributing constructively
Wednesday, 11 July 2007
- stopping discussions on serializations and contributing constructively
- Re: [W3C docs] We should teach by example.
- Re: review of "The root element" subsection
- Re: Lack Of Definition Of A Valid Ratio (part of detailed review of common microsyntaxes)
- Lack Of Finished Check In Comma/Space State (part of detailed review of common microsyntaxes)
- Should Lists Of Integers Allow Other Whitespace Characters? (part of detailed review of common microsyntaxes)
- More Odd Results From List Of Numbers (part of detailed review of common microsyntaxes)
- agenda: HTML WG teleconference Thu 12 July
- List Of Numbers Produces Incorrect Output (part of detailed review of common microsyntaxes)
- Re: Improving alt (was handling fallback content for still images)
- Re: [W3C docs] We should teach by example.
- Re: Lack Of Definition Of A Valid Ratio (part of detailed review of common microsyntaxes)
- Re: [W3C docs] We should teach by example.
- Re: [W3C docs] We should teach by example.
- Re: SURVEY: Release "HTML 5 differences from HTML 4" as a W3C Working Draft? formal decision
- Re: Lack Of Definition Of A Valid Ratio (part of detailed review of common microsyntaxes)
- Re: [W3C docs] We should teach by example.
- Re: [W3C docs] We should teach by example.
- Re: [W3C docs] We should teach by example.
- Re: Ratios Do Not Return Errors (part of detailed review of common microsyntaxes)
- Re: Lack Of Definition Of A Valid Ratio (part of detailed review of common microsyntaxes)
- alignment of <input>-s and their pseudo-elements (was: Re: Improving alt (was handling fallback content for still images))
- unite two space: attributes and properties
- Re: unify ancient attributes
- small consultation
- Re: Improving alt (was handling fallback content for still images)
- <formdata sa= >
- Re: Lack Of Definition Of A Valid Ratio (part of detailed review of common microsyntaxes)
- Re: Lack Of Definition Of A Valid Ratio (part of detailed review of common microsyntaxes)
- Re: Lack Of Definition Of A Valid Ratio (part of detailed review of common microsyntaxes)
- Re: Ratios Do Not Return Errors (part of detailed review of common microsyntaxes)
- Re: Lack Of Definition Of A Valid Ratio (part of detailed review of common microsyntaxes)
- [Ann] A limping development version of an HTML5 parser in Java
- document.title (detailed review of the DOM)
- Re: HTML Extensibility Through Script
- Re: HTML Extensibility Through Script
- Re: HTML Extensibility Through Script
- Re: HTML Extensibility Through Script
- Re: numerals for microformats
- numerals for microformats
- Re: HTML Extensibility Through Script
- Re: review of "The root element" subsection
Tuesday, 10 July 2007
- Re: review of "The root element" subsection
- Re: HTML Extensibility Through Script
- Re: review of "The root element" subsection (considering html/@charset)
- Re: review of "The root element" subsection
- Re: HTML Extensibility Through Script
- Re: HTML Extensibility Through Script
- Re: HTML Extensibility Through Script
- Re: HTML Extensibility Through Script
- Re: Foster parenting characters (detailed review of parsing algorithm)
- Foster parenting characters (detailed review of parsing algorithm)
- Re: review of "The root element" subsection (considering html/@charset)
- Re: HTML Extensibility Through Script
- Re: HTML Extensibility Through Script
- Ratios algorithm continues beyond data (part of detailed review of common microsyntaxes)
- HTML Extensibility Through Script
- Re: Lack Of Definition Of A Valid Ratio (part of detailed review of common microsyntaxes)
- Ratios Do Not Return Errors (part of detailed review of common microsyntaxes)
- Lack Of Definition Of A Valid Ratio (part of detailed review of common microsyntaxes)
- Re: review of "The root element" subsection
- Re: [Parsing] When/how flagged as being HTML
- Re: handling fallback content for still images
- Re: review of "The root element" subsection
- Re: review of "The root element" subsection
- Re: review of "The root element" subsection
- RE: [Parsing] When/how flagged as being HTML
- insert vs. append (detailed review of parsing algorithm)
- Re: [Parsing] When/how flagged as being HTML
- Re: handling fallback content for still images
- [Parsing] When/how flagged as being HTML
Monday, 9 July 2007
- let's keep metadata profiles (head/@profile) in HTML for use in GRDDL etc.
- Re: handling fallback content for still images
- Re: edge issues with DOM, text/html, and xml serializations [was Re: handling fallback content for still images]
- Re: edge issues with DOM, text/html, and xml serializations [was Re: handling fallback content for still images]
- Re: wiki aims for community voice/NPOV [was: review of "The root element" subsection]
- Re: wiki aims for community voice/NPOV [was: review of "The root element" subsection]
- Re: Wiki Section for Draft Reviews
- Re: edge issues with DOM, text/html, and xml serializations [was Re: handling fallback content for still images]
- Re: edge issues with DOM, text/html, and xml serializations [was Re: handling fallback content for still images]
- wiki aims for community voice/NPOV [was: review of "The root element" subsection]
- type parameter of Document.open() (detailed review of the DOM)
- Re: edge issues with DOM, text/html, and xml serializations [was Re: handling fallback content for still images]
- Re: HTMLCollection item() vs. namedItem() with [] syntax (detailed review of the DOM)
- Re: handling fallback content for still images
- Re: handling fallback content for still images
- Re: HTMLCollection item() vs. namedItem() with [] syntax (detailed review of the DOM)
- Re: edge issues with DOM, text/html, and xml serializations [was Re: handling fallback content for still images]
- Re: handling fallback content for still images
- Re: edge issues with DOM, text/html, and xml serializations [was Re: handling fallback content for still images]
- Re: HTMLCollection item() vs. namedItem() with [] syntax (detailed review of the DOM)
- Re: edge issues with DOM, text/html, and xml serializations [was Re: handling fallback content for still images]
- Re: review of "The root element" subsection
- Re: handling fallback content for still images
- Re: handling fallback content for still images
- Re: HTMLCollection item() vs. namedItem() with [] syntax (detailed review of the DOM)
- Re: HTMLCollection item() vs. namedItem() with [] syntax (detailed review of the DOM)
- Re: handling fallback content for still images
- Re: HTMLCollection item() vs. namedItem() with [] syntax (detailed review of the DOM)
- Re: handling fallback content for still images
- Re: handling fallback content for still images
- edge issues with DOM, text/html, and xml serializations [was Re: handling fallback content for still images]
- Re: handling fallback content for still images
- HTMLCollection item() vs. namedItem() with [] syntax (detailed review of the DOM)
- Wiki Section for Draft Reviews
- Re: handling fallback content for still images
- Re: review of "The root element" subsection
- RE: DI element
- Re: handling fallback content for still images
- Re: handling fallback content for still images
- Re: handling fallback content for still images
- review of "The root element" subsection
- Re: handling fallback content for still images
- Re: handling fallback content for still images
- Re: handling fallback content for still images
- Re: handling fallback content for still images
- Re: handling fallback content for still images
- Re: handling fallback content for still images
- Re: handling fallback content for still images
- Re: handling fallback content for still images
- Re: handling fallback content for still images
- Re: handling fallback content for still images
- Re: object element interoperability Re: handling fallback content for still images
- Re: On the color of the bikeshed, belling the cat, opportunity cost and marginalism
- Re: handling fallback content for still images
- Re: handling fallback content for still images
- Re: html5 syntax - why not use xml syntax?
- Re: care with empty/template wiki topics [was: some thoughts on ...]
- Re: Detailed review of section "Namespaces"
- Re: handling fallback content for still images
- Re: handling fallback content for still images
- Re: handling fallback content for still images
- Re: handling fallback content for still images
Sunday, 8 July 2007
- Re: Improving alt (was handling fallback content for still images)
- Re: handling fallback content for still images
- On the color of the bikeshed, belling the cat, opportunity cost and marginalism
- Re: Improving alt (was handling fallback content for still images)
- Re: html5 syntax - why not use xml syntax?
- Re: Accesskey - spec proposal
- Re: DI element
- Re: SURVEY: Release "HTML 5 differences from HTML 4" as a W3 Working Draft? formal decision
- Re: Implementing Accesskey - some techniques
- Re: Improving alt (was handling fallback content for still images)
- Re: html5 syntax - why not use xml syntax?
- Re: Improving alt (was handling fallback content for still images)
Saturday, 7 July 2007
- Re: [W3C docs] We should teach by example.
- Re: [W3C docs] We should teach by example.
- Re: html5 syntax - why not use xml syntax?
- Editorial Issues 1 (part of detailed review of common microsyntaxes)
- Re: html5 syntax - why not use xml syntax?
- Re: [W3C docs] We should teach by example.
- Re: [W3C docs] We should teach by example.
- Re: [W3C docs] We should teach by example.
- Re: html5 syntax - why not use xml syntax?
- Re: [W3C docs] We should teach by example.
- Re: html5 syntax - why not use xml syntax?
- Re: html5 syntax - why not use xml syntax?
- Re: html5 syntax - why not use xml syntax?
- Re: html5 syntax - why not use xml syntax?
- Re: Improving alt (was handling fallback content for still images)
- Re: html5 syntax - why not use xml syntax?
- Re: html5 syntax - why not use xml syntax?
- Re: html5 syntax - why not use xml syntax?
- Re: html5 syntax - why not use xml syntax?
- Re: html5 syntax - why not use xml syntax?
- Re: html5 syntax - why not use xml syntax?
- Re: html5 syntax - why not use xml syntax?
- Re: html5 syntax - why not use xml syntax?
- Re: Improving alt (was handling fallback content for still images)
- Re: handling fallback content for still images
- Re: handling fallback content for still images
Friday, 6 July 2007
- Re: [W3C docs] We should teach by example.
- Re: handling fallback content for still images
- Re: handling fallback content for still images
- Re: Proposal: accessibility revision for the img element...
- Re: handling fallback content for still images
- Re: [W3C docs] We should teach by example.
- Re: [W3C docs] We should teach by example.
- unifying alternate content across embedded content element types
- Re: Proposal: accessibility revision for the img element...
- Re: [W3C docs] We should teach by example.
- Re: Proposal: accessibility revision for the img element...
- Re: [W3C docs] We should teach by example.
- Re: [W3C docs] We should teach by example.
- Re: [W3C docs] We should teach by example.
- Re: [W3C docs] We should teach by example.
- Re: Improving alt (was handling fallback content for still images)
- Re: [W3C docs] We should teach by example.
- If in one sentence qualifying another sentence when resetting the insertion mode (detailed review of parsing algorithm)
- Re: [W3C docs] We should teach by example.
- Re: [W3C docs] We should teach by example.
- Re: [W3C docs] We should teach by example.
- Re: Proposal: accessibility revision for the img element...
- Re: [W3C docs] We should teach by example.
- Re: [W3C docs] We should teach by example.
- Re: [W3C docs] We should teach by example.
- Re: [W3C docs] We should teach by example.
- Re: [W3C docs] We should teach by example.
- Re: handling fallback content for still images
- Re: [W3C docs] We should teach by example.
- Re: html5 syntax - why not use xml syntax?
- Re: handling fallback content for still images
- Re: {off topic} [was:[W3C docs] We should teach by example.]
- Re: html5 syntax - why not use xml syntax?
- Re: {off topic} [was:[W3C docs] We should teach by example.]
- Re: {off topic} [was:[W3C docs] We should teach by example.]
- Re: html5 syntax - why not use xml syntax?
- html5 syntax - why not use xml syntax?
- {off topic} [was:[W3C docs] We should teach by example.]
- Re: [W3C docs] We should teach by example.
- Re: <code type="...">
- Re: [W3C docs] We should teach by example.
- Re: Proposal: accessibility revision for the img element...
- <legend> = <caption>
Thursday, 5 July 2007
Thursday, 28 June 2007
Friday, 6 July 2007
- Re: Table-related element on the implied end tag list (detailed review of parsing algorithm)
- Re: Generating implied end tags upon </table> "in table" (detailed review of parsing algorithm)
- Re: care with empty/template wiki topics [was: some thoughts on ...]
- Re: Proposal: accessibility revision for the img element...
- Re: handling fallback content for still images
- Re: handling fallback content for still images
- Re: handling fallback content for still images
- Re: Proposal: accessibility revision for the img element...
- Re: Proposal: accessibility revision for the img element...
- Re: Proposal: accessibility revision for the img element...
- Re: handling fallback content for still images
- Re: Proposal: accessibility revision for the img element...
- Re: handling fallback content for still images
- Generating implied end tags upon </table> "in table" (detailed review of parsing algorithm)
- Re: handling fallback content for still images
- Detailed review of section "Namespaces"
- Re: the market hasn't spoken - it hasn't bothered to listened [was Re: fear of "invisible metadata"]
- Re: [W3C docs] We should teach by example.
- "table" in table scope (detailed review of parsing algorithm)
- Re: can an img be a link within figure?
- [W3C docs] We should teach by example.
- Re: care with empty/template wiki topics [was: some thoughts on ...]
- Re: can an img be a link within figure?
Thursday, 5 July 2007
- Re: handling fallback content for still images
- Re: handling fallback content for still images
- Re: handling fallback content for still images
- Re: handling fallback content for still images
- Re: handling fallback content for still images
- Re: handling fallback content for still images
- Re: SURVEY: Release "HTML 5 differences from HTML 4" as a W3C Working Draft? formal decision
- Re: Improving alt (was handling fallback content for still images)
- notice of HTML WG teleconference Thu 12 July 1700Z
- Re: can an img be a link within figure?
- Re: Some data about the usage of style="", <style> and <link rel="stylesheet">
- Re: care with empty/template wiki topics [was: some thoughts on ...]
- Re: Some data about the usage of style="", <style> and <link rel="stylesheet">
- Some data about the usage of style="", <style> and <link rel="stylesheet">
- Re: can an img be a link within figure?
- Re: Wiki page for style attribute
- Re: Improving alt (was handling fallback content for still images)
- Re: handling fallback content for still images
- Re: care with empty/template wiki topics [was: some thoughts on ...]
- Re: care with empty/template wiki topics [was: some thoughts on ...]
- Re: handling fallback content for still images
- Re: care with empty/template wiki topics [was: some thoughts on ...]
- Re: handling fallback content for still images
- Re: care with empty/template wiki topics [was: some thoughts on ...]
- Re: care with empty/template wiki topics [was: some thoughts on ...]
- Re: handling fallback content for still images
- Re: SURVEY: Release "HTML 5 differences from HTML 4" as a W3C Working Draft? formal decision
- Re: handling fallback content for still images
- Re: care with empty/template wiki topics [was: some thoughts on ...]
- Re: handling fallback content for still images
- Re: care with empty/template wiki topics [was: some thoughts on ...]
- Re: handling fallback content for still images
- Re: SURVEY: Release "HTML 5 differences from HTML 4" as a W3C Working Draft? formal decision
- Re: SURVEY: Release "HTML 5 differences from HTML 4" as a W3C Working Draft? formal decision
- Re: handling fallback content for still images
- Re: handling fallback content for still images
- care with empty/template wiki topics [was: some thoughts on ...]
- Re: SURVEY: Release "HTML 5 differences from HTML 4" as a W3C Working Draft? formal decision
- Re: handling fallback content for still images
- Re: handling fallback content for still images
- Re: SURVEY: Release "HTML 5 differences from HTML 4" as a W3C Working Draft? formal decision
- Re: object element interoperability Re: handling fallback content for still images
- Re: handling fallback content for still images
- Re: unify ancient attributes
- Re: handling fallback content for still images
- Re: handling fallback content for still images
- Re: handling fallback content for still images
- Re: handling fallback content for still images
- Re: handling fallback content for still images
- Re: handling fallback content for still images
- RE: Neutrality in "HTML 5 differences from HTML 4"
- Re: handling fallback content for still images
- Re: handling fallback content for still images
- Re: handling fallback content for still images
- Re: Off topic: form elements
- @ping attribute wiki page.
- Re: unify ancient attributes
- Re: handling fallback content for still images
- Re: can an img be a link within figure?
- Re: handling fallback content for still images
- Re: handling fallback content for still images
- can an img be a link within figure?
- Re: handling fallback content for still images
- Re: handling fallback content for still images
- Re: handling fallback content for still images
- Re: handling fallback content for still images
- Re: handling fallback content for still images
- Re: handling fallback content for still images
- Re: handling fallback content for still images
- Re: handling fallback content for still images
- Re: handling fallback content for still images
- Re: handling fallback content for still images
- Re: handling fallback content for still images
- Re: handling fallback content for still images
- Non-sensical catch-all handling of end tags in "in body" (detailed review of parsing algorithm)
- Re: handling fallback content for still images
- Re: handling fallback content for still images
- Re: handling fallback content for still images
- Re: handling fallback content for still images
- Re: handling fallback content for still images
- Re: handling fallback content for still images
- Re: Wiki page for style attribute
- Useless implied end tags upon </p> (detailed review of parsing algorithm)
- Re: Scope, implied end tags, another scope check (detailed review of parsing algorithm)
- Re: unify ancient attributes
- Re: handling fallback content for still images
- Table-related element on the implied end tag list (detailed review of parsing algorithm)
- Re: Scope, implied end tags, another scope check (detailed review of parsing algorithm)
- Just popping when generating implied end tags (detailed review of parsing algorithm)
- Re: handling fallback content for still images
- Re: Scope, implied end tags, another scope check (detailed review of parsing algorithm)
Thursday, 28 June 2007
Thursday, 5 July 2007
- Re: handling fallback content for still images
- Scope, implied end tags, another scope check (detailed review of parsing algorithm)
- Re: handling fallback content for still images
- Re: handling fallback content for still images
- Re: Accesskey - spec proposal
Wednesday, 4 July 2007
- Re: Accesskey - spec proposal
- Re: Accesskey - spec proposal
- Re: Accesskey - spec proposal
- Re: Accesskey - spec proposal
- Popping until no element with the token name in scope (detailed review of parsing algorithm)
- Re: What happens if ... we drop @style (was: Re: Wiki page for style attribute)
- Re: Un-subscribe from public-html without leaving HTMLWG?
- Re: Accesskey - spec proposal
- Re: Off topic: form elements
- Re: Un-subscribe from public-html without leaving HTMLWG?
- Re: Accesskey - spec proposal
- Re: Accesskey - spec proposal
- Off topic: form elements
- Re: Accesskey - spec proposal
- Re: What happens if ... we drop @style
- Re: Accesskey - spec proposal
- Re: What happens if ... we drop @style
- Re: Accesskey - spec proposal
- What happens if ... we drop @style (was: Re: Wiki page for style attribute)
- Re: Accesskey - spec proposal
- Re: accessibility of video element
- Re: accessibility of video element
- Re: Un-subscribe from public-html without leaving HTMLWG?
- Re: handling fallback content for still images
- Re: Accesskey - Whats it for?
- Re: accessibility of video element
- Re: DI element
- Re: handling fallback content for still images
- Re: accessibility of video element
- Gathering Rationales (Wiki page)
- Re: More on <CAPTION> element etc
- Inserting frameset (detailed review of parsing algorithm)
- Re: DI element [Re: html 5 and accessibility issue]
- Re: Neutrality in "HTML 5 differences from HTML 4"
- Re: Accesskey - spec proposal
- Re: Accesskey - spec proposal
- Re: DI element
- Re: CSS syntax inside scoped style, was: Wiki page for style attribute
- Re: Neutrality in "HTML 5 differences from HTML 4"
- Re: Un-subscribe from public-html without leaving HTMLWG?
- Re: Un-subscribe from public-html without leaving HTMLWG?
- Re: Un-subscribe from public-html without leaving HTMLWG?
- object element interoperability Re: handling fallback content for still images
- Re: Un-subscribe from public-html without leaving HTMLWG?
- Re: Accesskey - spec proposal
- Re: Accesskey - spec proposal
- Re: handling fallback content for still images
- Re: handling fallback content for still images
Tuesday, 3 July 2007
- Re: Accesskey - spec proposal
- Re: handling fallback content for still images
- Re: Neutrality in "HTML 5 differences from HTML 4"
- Re: handling fallback content for still images
- Re: DI element [Re: html 5 and accessibility issue]
- Re: DI element
- Re: DI element [Re: html 5 and accessibility issue]
- Re: DI element [Re: html 5 and accessibility issue]
- Re: DI element [Re: html 5 and accessibility issue]
- Re: Neutrality in "HTML 5 differences from HTML 4"
- Re: Neutrality in "HTML 5 differences from HTML 4"
- Re: Wiki page for style attribute
- Re: Neutrality in "HTML 5 differences from HTML 4"
- Re: Accesskey - spec proposal
- Re: html 5 and accessibility issue
- Re: Wiki page for style attribute
- Re: DI element
- Re: Wiki page for style attribute
- Re: DI element
- Re: Neutrality in "HTML 5 differences from HTML 4"
- Re: Proposal for a new element instead of <style scoped>
- Re: DI element
- Proposal for a new element instead of <style scoped>
- Re: Neutrality in "HTML 5 differences from HTML 4"
- Re: CSS syntax inside scoped style, was: Wiki page for style attribute
- Re: CSS syntax inside scoped style, was: Wiki page for style attribute
- Re: Accesskey - spec proposal
- Re: Neutrality in "HTML 5 differences from HTML 4"
- CSS syntax inside scoped style, was: Wiki page for style attribute
- Re: Neutrality in "HTML 5 differences from HTML 4"
- Re: DI element [Re: html 5 and accessibility issue]
- Re: Accesskey - spec proposal
- Re: [html] HTML elements index
- Re: Wiki page for style attribute
- Re: [html] HTML elements index
- Re: Neutrality in "HTML 5 differences from HTML 4"
- Re: Wiki page for style attribute
- Re: Wiki page for style attribute
- Re: html 5 and accessibility issue
- Re: Neutrality in "HTML 5 differences from HTML 4"
- Re: DI element [Re: html 5 and accessibility issue]
- Implementing Accesskey - some techniques
- Re: DI element [Re: html 5 and accessibility issue]
- Re: Neutrality in "HTML 5 differences from HTML 4"
- Re: Neutrality in "HTML 5 differences from HTML 4"
- Re: handling fallback content for still images
- Re: DI element [Re: html 5 and accessibility issue]
- Re: Neutrality in "HTML 5 differences from HTML 4"
- Re: handling fallback content for still images
- RE: Define: Fall Back
- Re: DI element [Re: html 5 and accessibility issue]
- Re: DI element [Re: html 5 and accessibility issue]
- Re: some thoughts on objections to publishing ""HTML 5 differences from HTML 4"
- Re: DI element [Re: html 5 and accessibility issue]
- Re: DI element [Re: html 5 and accessibility issue]
- Re: Accesskey - spec proposal
- Re: Accesskey - spec proposal
- Re: handling fallback content for still images
- Re: handling fallback content for still images
- Re: Accesskey - spec proposal
- Re: Accesskey - spec proposal
- Re: Accesskey - spec proposal
- Re: DI element [Re: html 5 and accessibility issue]
- Re: handling fallback content for still images
- Re: DI element [Re: html 5 and accessibility issue]
- Re: Accesskey - spec proposal
- Re: handling fallback content for still images
- Re: Neutrality in "HTML 5 differences from HTML 4"
- Re: handling fallback content for still images
- Accesskey - spec proposal
- Re: Neutrality in "HTML 5 differences from HTML 4"
- Re: Neutrality in "HTML 5 differences from HTML 4"
- Re: Neutrality in "HTML 5 differences from HTML 4"
- Re: handling fallback content for still images
- Re: handling fallback content for still images
- Re: some thoughts on objections to publishing ""HTML 5 differences from HTML 4"
- Re: Neutrality in "HTML 5 differences from HTML 4"
- Re: DI element [Re: html 5 and accessibility issue]
- Re: Neutrality in "HTML 5 differences from HTML 4"
- Re: Neutrality in "HTML 5 differences from HTML 4"
- Re: Neutrality in "HTML 5 differences from HTML 4"
- Re: Neutrality in "HTML 5 differences from HTML 4"
- Re: Summary: Naming Issue, Proposals
- Re: handling fallback content for still images
- Re: handling fallback content for still images
- Re: accessibility of video element
- Re: handling fallback content for still images
- Re: handling fallback content for still images
- Re: Neutrality in "HTML 5 differences from HTML 4"
- Re: Summary: Naming Issue, Proposals
- Re: Neutrality in "HTML 5 differences from HTML 4"
- Update: Naming Issue, Proposals
- Re: handling fallback content for still images
- Re: Summary: Naming Issue, Proposals
- Re: handling fallback content for still images
- Re: handling fallback content for still images
- Re: handling fallback content for still images
- Re: handling fallback content for still images
- Re: handling fallback content for still images
- Re: handling fallback content for still images
- Re: handling fallback content for still images
- Re: handling fallback content for still images
- Re: LONGDESC: some current problems and a proposed solution added to the wiki
- Re: LONGDESC: some current problems and a proposed solution added to the wiki
- Re: handling fallback content for still images
- Re: LONGDESC: some current problems and a proposed solution added to the wiki
- Re: html 5 and accessibility issue
- Re: handling fallback content for still images
- Re: handling fallback content for still images
- Re: html 5 and accessibility issue
- Re: DI element [Re: html 5 and accessibility issue]
Monday, 2 July 2007
- Re: Summary: Naming Issue, Proposals
- Re: some thoughts on objections to publishing ""HTML 5 differences from HTML 4"
- Re: Un-subscribe from public-html without leaving HTMLWG?
- Re: Un-subscribe from public-html without leaving HTMLWG?
- Re: html 5 and accessibility issue
- Re: some thoughts on objections to publishing ""HTML 5 differences from HTML 4"
- Re: some thoughts on objections to publishing ""HTML 5 differences from HTML 4"
- accessibility of video element
- translation task added to survey (was: HTML5 differences ...)
- Re: LONGDESC: some current problems and a proposed solution added to the wiki
- Re: handling fallback content for still images
- Re: LONGDESC: some current problems and a proposed solution added to the wiki
- Re: DI element [Re: html 5 and accessibility issue]
- Re: <code type="...">
- Re: LONGDESC: some current problems and a proposed solution added to the wiki
- Re: LONGDESC: some current problems and a proposed solution added to the wiki
- Re: Wiki page for style attribute
- Re: <code type="...">
- Re: Wiki page for style attribute
- Re: <code type="...">
- Definitions, Clarifications & Request for Consensus on Terminology on Wiki [was Re: Define: Fall Back]
- Re: Define: Fall Back
- Re: handling fallback content for still images
- in body "select" not associated with the form pointer (detailed review of parsing algorithm)
- Re: some thoughts on objections to publishing ""HTML 5 differences from HTML 4"
- Re: Define: Fall Back
- Re: Definition items as nested DL elements (was Re: DI element)
- Re: Why the style attribute shouldn't be abandoned
- Re: "placeholder link"
- Re: HTML5 differences from HTML4 editor's draft
Sunday, 1 July 2007
Monday, 2 July 2007
- Re: Summary: Naming Issue, Proposals
- Definition items as nested DL elements (was Re: DI element)
- Re: Wiki page for style attribute
- Re: Wiki page for style attribute
- Reminder: " Release "HTML 5 differences from HTML 4" as a W3C Working Draft?" survey closes 2007-07-03.
- Re: DI element [Re: html 5 and accessibility issue]
- Re: LONGDESC: some current problems and a proposed solution added to the wiki
- Re: Drag and drop Re: html 5 and accessibility issue
- Re: html 5 and accessibility issue
- Re: DI element
- Drag and drop Re: html 5 and accessibility issue
- Re: html 5 and accessibility issue
- Re: LONGDESC: some current problems and a proposed solution added to the wiki
- Re: html 5 and accessibility issue - need of fallback content
- Re: Un-subscribe from public-html without leaving HTMLWG?
- Re: html 5 and accessibility issue
- Re: html 5 and accessibility issue
- Re: Define: Fall Back
- Re: Idea for new element to support automatic rendering of descriptive content for people with disabilities
- Re: Neutrality in "HTML 5 differences from HTML 4"
- Re: DI element
- Re: Neutrality in "HTML 5 differences from HTML 4"
- Re: Define: Fall Back
- Define: Fall Back
- Re: DI element [Re: html 5 and accessibility issue]
- Re: LONGDESC: some current problems and a proposed solution added to the wiki
- Re: LONGDESC: some current problems and a proposed solution added to the wiki
- Re: Wiki page for style attribute
- Re: handling fallback content for still images
- Re: DI element
- Re: html 5 and accessibility issue
- Re: LONGDESC: some current problems and a proposed solution added to the wiki
- Re: some thoughts on objections to publishing ""HTML 5 differences from HTML 4"
- Re: Un-subscribe from public-html without leaving HTMLWG?
- Re: [html] HTML elements index
Sunday, 1 July 2007
- Re: DI element [Re: html 5 and accessibility issue]
- Re: Wiki page for style attribute
- Re: DI element
- Re: DI element
- Re: DI element [Re: html 5 and accessibility issue]
- Re: DI element [Re: html 5 and accessibility issue]
- handling fallback content for still images
- Re: html 5 and accessibility issue - need of fallback content
- Re: html 5 and accessibility issue - need of fallback content
- Re: the market hasn't spoken - it hasn't bothered to listened
- Re: html 5 and accessibility issue - need of fallback content
- Re: html 5 and accessibility issue - need of fallback content
- Re: html 5 and accessibility issue - need of fallback content
- in body "address" (etc.) and hn starts (detailed review of parsing algorithm)
- Re: Neutrality in "HTML 5 differences from HTML 4"
- Motivation of the generic [R]CDATA parsing algorithm (detailed review of parsing algorithm)
- Re: LONGDESC: some current problems and a proposed solution added to the wiki
- Moving <title> to head not clear "in body" (detailed review of parsing algorithm)
- HTML5 3.7, 3.14.12-14, 8.2
- base, link and meta are never popped (detailed review of parsing algorithm)
- Neutrality in "HTML 5 differences from HTML 4"
- Re: LONGDESC: some current problems and a proposed solution added to the wiki
- DI element [Re: html 5 and accessibility issue]
- Re: html 5 and accessibility issue - need of fallback content
- Re: Why the style attribute shouldn't be abandoned
- Re: some thoughts on objections to publishing ""HTML 5 differences from HTML 4"
- Re: LONGDESC: some current problems and a proposed solution added to the wiki
- Re: html 5 and accessibility issue - need of fallback content
- Re: Wiki page for style attribute
- Re: LONGDESC: some current problems and a proposed solution added to the wiki
- Re: html 5 and accessibility issue - need of fallback content
- Associating dt with prior dd (was: html 5 and accessibility issue)
- Re: html 5 and accessibility issue - need of fallback content
- Re: html 5 and accessibility issue - need of fallback content
- Re: Wiki page for style attribute
- Re: LONGDESC: some current problems and a proposed solution added to the wiki
- Re: LONGDESC: some current problems and a proposed solution added to the wiki
- Re: LONGDESC: some current problems and a proposed solution added to the wiki
- Re: some thoughts on objections to publishing ""HTML 5 differences from HTML 4"
- [html] HTML elements index (update)
- Re: html 5 and accessibility issue - need of fallback content
- Re: html 5 and accessibility issue - dl element
- Re: html 5 and accessibility issue - need of fallback content
- Re: LONGDESC: some current problems and a proposed solution added to the wiki
- Re: html 5 and accessibility issue - need of fallback content
- Re: LONGDESC: some current problems and a proposed solution added to the wiki
- Re: LONGDESC: some current problems and a proposed solution added to the wiki
- Re: html 5 and accessibility issue
- Re: html 5 and accessibility issue - need of fallback content
- Re: html 5 and accessibility issue
- Re: html 5 and accessibility issue
- Re: html 5 and accessibility issue
- Re: LONGDESC: some current problems and a proposed solution added to the wiki
- Re: html 5 and accessibility issue
- Re: html 5 and accessibility issue
- Re: some thoughts on objections to publishing ""HTML 5 differences from HTML 4"
- Re: html 5 and accessibility issue - need of fallback content
- Re: LONGDESC: some current problems and a proposed solution added to the wiki
- Re: html 5 and accessibility issue
- Re: LONGDESC: some current problems and a proposed solution added to the wiki
- Re: LONGDESC: some current problems and a proposed solution added to the wiki
- Re: LONGDESC: some current problems and a proposed solution added to the wiki
- Re: LONGDESC: some current problems and a proposed solution added to the wiki
- Re: LONGDESC: some current problems and a proposed solution added to the wiki
- Re: html 5 and accessibility issue
- Re: LONGDESC: some current problems and a proposed solution added to the wiki
- Re: html 5 and accessibility issue
- Re: html 5 and accessibility issue
- Re: html 5 and accessibility issue
- Re: LONGDESC: some current problems and a proposed solution added to the wiki
- Re: html 5 and accessibility issue
- Re: LONGDESC: some current problems and a proposed solution added to the wiki
- Re: html 5 and accessibility issue
- Re: LONGDESC: some current problems and a proposed solution added to the wiki
- Re: LONGDESC: some current problems and a proposed solution added to the wiki
- Re: LONGDESC: some current problems and a proposed solution added to the wiki