Friday, 31 August 2007
- Re: Prevalence of ill-formed XHTML
- Re: keep conformance objective (detailed review of section 1. Introduction)
- RE: User Testing of Accessiblity Features
- Re: keep conformance objective (detailed review of section 1. Introduction)
- Re: User Testing of Accessiblity Features
- Re: Downloading of images by UA
- Re: let authors choose text/html or application/xhtml+xml (detailed review of section 1. Introduction)
- Re: Prevalence of ill-formed XHTML (was: Re: let authors choose text/html or application/xhtml+xml)
- Re: let authors choose text/html or application/xhtml+xml (detailed review of section 1. Introduction)
- Prevalence of ill-formed XHTML (was: Re: let authors choose text/html or application/xhtml+xml)
- Re: Investigating the proposed alt attribute recommendations in HTML 5
- Re: let authors choose text/html or application/xhtml+xml (detailed review of section 1. Introduction)
- Re: Investigating the proposed alt attribute recommendations in HTML 5
- Re: Investigating the proposed alt attribute recommendations in HTML 5
- Re: let authors choose text/html or application/xhtml+xml (detailed review of section 1. Introduction)
- Microsoft review of HTML5 draft delayed
- Re: let authors choose text/html or application/xhtml+xml (detailed review of section 1. Introduction)
- Re: Typos and suggestions for small corrections in WF2 Section 2 (Part of the detailed review of WF2)
- Re: let authors choose text/html or application/xhtml+xml (detailed review of section 1. Introduction)
- making better ad hoc use of class attribute values
- Re: let authors choose text/html or application/xhtml+xml (detailed review of section 1. Introduction)
- Re: let authors choose text/html or application/xhtml+xml (detailed review of section 1. Introduction)
- Re: let authors choose text/html or application/xhtml+xml (detailed review of section 1. Introduction)
- Re: let authors choose text/html or application/xhtml+xml (detailed review of section 1. Introduction)
- Re: let authors choose text/html or application/xhtml+xml (detailed review of section 1. Introduction)
- Re: Typos and suggestions for small corrections in WF2 Section 2 (Part of the detailed review of WF2)
- Re: let authors choose text/html or application/xhtml+xml (detailed review of section 1. Introduction)
- Re: Typos and suggestions for small corrections in WF2 Section 2 (Part of the detailed review of WF2)
- Re: Screen-reader behaviour
- Re: Investigating the proposed alt attribute recommendations in HTML 5
- Re: let authors choose text/html or application/xhtml+xml (detailed review of section 1. Introduction)
- Re: let authors choose text/html or application/xhtml+xml (detailed review of section 1. Introduction)
- Re: let authors choose text/html or application/xhtml+xml (detailed review of section 1. Introduction)
- Re: let authors choose text/html or application/xhtml+xml (detailed review of section 1. Introduction)
- Re: let authors choose text/html or application/xhtml+xml (detailed review of section 1. Introduction)
- Re: let authors choose text/html or application/xhtml+xml (detailed review of section 1. Introduction)
- Re: let authors choose text/html or application/xhtml+xml (detailed review of section 1. Introduction)
- Re: Examples for recommending alt omission needed for testing
- WF2 2.13. Adding type attribute for the output element (Part of detailed review of WF2)
- Re: Patterns for explicit associations
- Re: let authors choose text/html or application/xhtml+xml (detailed review of section 1. Introduction)
- Typos and suggestions for small corrections in WF2 Section 2 (Part of the detailed review of WF2)
- Re: Screen-reader behaviour
- Re: Screen-reader behaviour
- Re: Investigating the proposed alt attribute recommendations in HTML 5
- RE: Screen-reader behaviour
- Re: change "scientific documents" to "basic hypertext" (detailed review of section 1. Introduction)
- Examples for recommending alt omission needed for testing
- Re: Screen-reader behaviour
- Re: The only name for the xml serialisation of html5
- Re: let authors choose text/html or application/xhtml+xml (detailed review of section 1. Introduction)
- keeping out semantic facilities for theoretical purity
- Re: The only name for the xml serialisation of html5
- Re: "presentation concerns" out of scope? (detailed review of section 1. Introduction)
- Re: Investigating the proposed alt attribute recommendations in HTML 5
- Re: let authors choose text/html or application/xhtml+xml (detailed review of section 1. Introduction)
- Re: Screen-reader behaviour
- Re: Screen-reader behaviour
- Re: Screen-reader behaviour
- Re: User Testing of Accessiblity Features
- Re: Investigating the proposed alt attribute recommendations in HTML 5
- Re: Investigating the proposed alt attribute recommendations in HTML 5
- Re: let authors choose text/html or application/xhtml+xml (detailed review of section 1. Introduction)
- Re: Investigating the proposed alt attribute recommendations in HTML 5
Thursday, 30 August 2007
- Re: let authors choose text/html or application/xhtml+xml (detailed review of section 1. Introduction)
- Re: let authors choose text/html or application/xhtml+xml (detailed review of section 1. Introduction)
- RE: User Testing of Accessiblity Features
- Is there a WIKI of test cases? Re: User Testing of Accessiblity Features
- product classes, "support some version of XML" (detailed review of section 1. Introduction)
- let authors choose text/html or application/xhtml+xml (detailed review of section 1. Introduction)
- keep conformance objective (detailed review of section 1. Introduction)
- strike "This specification should be read like all other specifications." (detailed review of section 1. Introduction)
- Re: User Testing of Accessiblity Features
- auction sites and XHTML 2 (detailed review of section 1. Introduction)
- "presentation concerns" out of scope? (detailed review of section 1. Introduction)
- spell out HTML in title and/or abstract (detailed review of section 1. Introduction)
- "vague subject referred to as Web Applications" (detailed review of section 1. Introduction)
- change "scientific documents" to "basic hypertext" (detailed review of section 1. Introduction)
- RE: Investigating the proposed alt attribute recommendations in HTML 5
- Re: agenda 30 Aug HTML WG teleconference
- Re: Screen-reader behaviour
- Re: Screen-reader behaviour
- Re: Screen-reader behaviour
- Re: User Testing of Accessiblity Features
- Re: Investigating the proposed alt attribute recommendations in HTML 5
- RE: User Testing of Accessiblity Features
- Re: Equivalents (was Re: Multilanguage alt/title)
- Re: Equivalents (was Re: Multilanguage alt/title)
- Re: Screen-reader behaviour
- Re: Investigating the proposed alt attribute recommendations in HTML 5
- Screen-reader behaviour
- Re: Investigating the proposed alt attribute recommendations in HTML 5
- Re: Alt Text for A Key Part of the Content
- Re: User Testing of Accessiblity Features
- Re: User Testing of Accessiblity Features
- Re: Investigating the proposed alt attribute recommendations in HTML 5
- Re: User Testing of Accessiblity Features
- Re: User Testing of Accessiblity Features
- Re: User Testing of Accessiblity Features
- Re: Investigating the proposed alt attribute recommendations in HTML 5
- Re: User Testing of Accessiblity Features
- The only name for the xml serialisation of html5
- Re: User Testing of Accessiblity Features
- Re: User Testing of Accessiblity Features
- Re: Investigating the proposed alt attribute recommendations in HTML 5
- Re: Investigating the proposed alt attribute recommendations in HTML 5
- Re: Investigating the proposed alt attribute recommendations in HTML 5
- RE: User Testing of Accessiblity Features
- Re: Investigating the proposed alt attribute recommendations in HTML 5
- Re: Equivalents (was Re: Multilanguage alt/title)
- Re: Multilanguage alt/title
- Re: Equivalents (was Re: Multilanguage alt/title)
- Re: Multilanguage alt/title
- Re: Investigating the proposed alt attribute recommendations in HTML 5
- Re: review of content type rules by IETF/HTTP community
- Re: review of content type rules by IETF/HTTP community
- Re: Investigating the proposed alt attribute recommendations in HTML 5
- Equivalents (was Re: Multilanguage alt/title)
- Re: Investigating the proposed alt attribute recommendations in HTML 5
- Re: Multilanguage alt/title
- Re: Multilanguage alt/title
- Re: Heuristic Tests for Data Tables (Discussion)
- Re: Investigating the proposed alt attribute recommendations in HTML 5
- Re: Investigating the proposed alt attribute recommendations in HTML 5
- Re: Multilanguage alt/title
- Re: Multilanguage alt/title
- Re: Investigating the proposed alt attribute recommendations in HTML 5
Wednesday, 29 August 2007
- Re: Investigating the proposed alt attribute recommendations in HTML 5
- Re: Multilanguage alt/title
- agenda 30 Aug HTML WG teleconference
- Re: Investigating the proposed alt attribute recommendations in HTML 5
- Re: Investigating the proposed alt attribute recommendations in HTML 5
- Re: Investigating the proposed alt attribute recommendations in HTML 5
- Re: Investigating the proposed alt attribute recommendations in HTML 5
- Re: Investigating the proposed alt attribute recommendations in HTML 5
- Re: Investigating the proposed alt attribute recommendations in HTML 5
- Investigating the proposed alt attribute recommendations in HTML 5
- teleconference bridge for 30 Aug HTML WG teleconference
- RE: Ruby in HTML
- Re: Multilanguage alt/title
- RE: User Testing of Accessiblity Features
- RE: User Testing of Accessiblity Features
- Re: review of content type rules by IETF/HTTP community
- Re: review of content type rules by IETF/HTTP community
- Re[2]: <meta name=register>, Browser as passive tool
- Re[7]: <table presentation="pie"> (was: Re: <table chart="pie">)
- Re[5]: <pages> <page>...<page> </pages>
- Re: User Testing of Accessiblity Features
- Re: review of content type rules by IETF/HTTP community
- Re: review of content type rules by IETF/HTTP community
Tuesday, 28 August 2007
- Re: User Testing of Accessiblity Features
- Detailed review of Section 2. The Document Object Model.
- Re: User Testing of Accessiblity Features
- Re: Multilanguage alt/title
- Re: User Testing of Accessiblity Features
- RE: User Testing of Accessiblity Features
- Re: User Testing of Accessiblity Features
- Re: User Testing of Accessiblity Features
- RE: User Testing of Accessiblity Features
- Re: Alt Text for A Key Part of the Content
- Re: Alt Text for A Key Part of the Content
- Re: Multilanguage alt/title
- RE: User Testing of Accessiblity Features
- Re: Removing the data attribute on <object> (detailed review of Semantics)
- Re: review of content type rules by IETF/HTTP community
- Re: review of content type rules by IETF/HTTP community
- Re: [HDP] Other comments from RI
- Multilanguage alt/title
- Re: [HDP] Other comments from RI
- Re: Serialize U+00A0 as in HTML? (detailed review of Serializing HTML fragments)
- Re: Serialize U+00A0 as in HTML? (detailed review of Serializing HTML fragments)
- Re[2]: Decision cube
- Re: User Testing of Accessiblity Features
- Re: [HDP] Other comments from RI
- Re: [whatwg] Offline Web Apps
Monday, 27 August 2007
- Re: [HDP] Other comments from RI
- Re: User Testing of Accessiblity Features
- Re: review of content type rules by IETF/HTTP community
- Re: review of content type rules by IETF/HTTP community
- Re: review of content type rules by IETF/HTTP community
- Re: Serialize U+00A0 as in HTML? (detailed review of Serializing HTML fragments)
- Re: Serialize U+00A0 as in HTML? (detailed review of Serializing HTML fragments)
- Re: Serialize U+00A0 as in HTML? (detailed review of Serializing HTML fragments)
- Serialize U+00A0 as in HTML? (detailed review of Serializing HTML fragments)
- Re: Re[3]: <pages> <page>...<page> </pages>
- Re: review of content type rules by IETF/HTTP community
- Re: [HDP] Other comments from RI
- Re: Re[5]: <table presentation="pie"> (was: Re: <table chart="pie">)
- Re: review of content type rules by IETF/HTTP community
- Re: Marking Up Accessible Comic Strips
- Re: [HDP] Other comments from RI
- Re: [HDP] Other comments from RI
- Re: <meta name=register>, Browser as passive tool
- Re: <meta name=register>, Browser as passive tool
- Re: review of content type rules by IETF/HTTP community
- Re[5]: <table presentation="pie"> (was: Re: <table chart="pie">)
- Re[6]: <table presentation="pie"> (was: Re: <table chart="pie">)
- Re[3]: <pages> <page>...<page> </pages>
- Re[3]: <meta name=register>, Browser as passive tool
- correction of auto-table and auto-tree
- auto-table & presentation=decart
- <table><tside>: displaying of table 3x100 of DBMS as table 10x10
- Decision cube
- Re: review of content type rules by IETF/HTTP community
- Re: review of content type rules by IETF/HTTP community
- Re: review of content type rules by IETF/HTTP community
- Re: [HDP] Other comments from RI
- Re: Alt Text for A Key Part of the Content
Sunday, 26 August 2007
- Re: review of content type rules by IETF/HTTP community
- Re: review of content type rules by IETF/HTTP community
- Re: review of content type rules by IETF/HTTP community
- Re: review of content type rules by IETF/HTTP community
- Re: review of content type rules by IETF/HTTP community
- Re: review of content type rules by IETF/HTTP community
- Re: review of content type rules by IETF/HTTP community
- Re: review of content type rules by IETF/HTTP community
- Re: Marking Up Accessible Comic Strips
- Re: [HDP] Other comments from RI
- Alt Text for A Key Part of the Content
- Marking Up Accessible Comic Strips
- Re: how to get my login info?
- how to get my login info?
Saturday, 25 August 2007
- Re: review of content type rules by IETF/HTTP community
- Re: review of content type rules by IETF/HTTP community
- Re: review of content type rules by IETF/HTTP community
- Re: Form Serialization
- Re: review of content type rules by IETF/HTTP community
Friday, 24 August 2007
- Re: This Working Group needs a Secretary
- RE: non-conforming authoring tools: the backplane of portals, networking & photo sites
Saturday, 25 August 2007
- Re: Image Equivalent Content Wiki page
- Re: review of content type rules by IETF/HTTP community
- Re: review of content type rules by IETF/HTTP community
- Re: review of content type rules by IETF/HTTP community
- Re: review of content type rules by IETF/HTTP community
- Re: review of content type rules by IETF/HTTP community
- Re: review of content type rules by IETF/HTTP community
- Re: Image Equivalent Content Wiki page
- Re: review of content type rules by IETF/HTTP community
Friday, 24 August 2007
- Re: review of content type rules by IETF/HTTP community
- Re: [whatwg] Answering the question... (timing of table headers issue)
- Re: Heuristic Tests for Data Tables (Discussion)
- Re: This Working Group needs a Secretary
- Re: Heuristic Tests for Data Tables (Discussion)
- Re: review of content type rules by IETF/HTTP community
- Re: review of content type rules by IETF/HTTP community
- Re: review of content type rules by IETF/HTTP community
- Re: Heuristic Tests for Data Tables (Discussion)
- Re: [whatwg] Answering the question... (timing of table headers issue)
- Re: This Working Group needs a Secretary
- Re: [whatwg] Answering the question... (timing of table headers issue)
- [HDP] Why Accessibility Is An Important & Essential Principle
- RE: [whatwg] Answering the question... (timing of table headers issue)
- Re: Heuristic Tests for Data Tables (Discussion)
- Image Equivalent Content Wiki page
- Re: review of content type rules by IETF/HTTP community
- RE: [HDP] Other comments from RI
- RE: [HDP] Missing principles
- Re: review of content type rules by IETF/HTTP community
- This Working Group needs a Secretary
- Re: [HDP] Other comments from RI
- Re: [HDP] Other comments from RI
- Re: [HDP] Other comments from RI
- Re: review of content type rules by IETF/HTTP community
- Re: non-conforming authoring tools: the backplane of portals, networking & photo sites
- Re: review of content type rules by IETF/HTTP community
- Re: Offline Web Apps
- Re: Offline Web Apps
- Re: <object> content-type sniffing (detailed review of Semantics)
- Re: <object> content-type sniffing (detailed review of Semantics)
- Re: <object> content-type sniffing (detailed review of Semantics)
- Re: [whatwg] Answering the question... (timing of table headers issue)
- Re: Offline Web Apps
- Re: <object> content-type sniffing (detailed review of Semantics)
- Offline Web Apps
- Re: An open letter to Anne van Kesteren
- Re: An open letter to Anne van Kesteren
- Re: [HDP] Missing principles
- Re: review of content type rules by IETF/HTTP community
Thursday, 23 August 2007
- Re: [HDP] Missing principles
- [HDP] principle "Universal Access"
- RE: Answering the question... (timing of table headers issue)
- Re: Answering the question... (timing of table headers issue)
- RE: An open letter to Anne van Kesteren
- Re: Add Example Explaining that Alt Text is Dependent Upon the Context
- Re: review of content type rules by IETF/HTTP community
- RE: Answering the question... (timing of table headers issue)
- Re: "real life" longdesc examples
- RE: Answering the question... (timing of table headers issue)
- "real life" longdesc examples
- Re: Answering the question... (timing of table headers issue)
- Re: Answering the question...
- Answering the question...
- Re: Add Example Explaining that Alt Text is Dependent Upon the Context
- non-conforming authoring tools: the backplane of portals, networking & photo sites
- Re: Add Example Explaining that Alt Text is Dependent Upon the Context
- Re: <object> content-type sniffing (detailed review of Semantics)
- Re: conformance (was Re: Review of 3.15.1. The table element)
- Re: <object> content-type sniffing (detailed review of Semantics)
- Re: Add Example Explaining that Alt Text is Dependent Upon the Context
- [HDP] Other comments from RI
- Re: <object> content-type sniffing (detailed review of Semantics)
- An open letter to Anne van Kesteren
- Re: [HDP] Missing principles
- Re: Add Example Explaining that Alt Text is Dependent Upon the Context
- [HDP] Missing principles
- Re: Add Example Explaining that Alt Text is Dependent Upon the Context
- conformance (was Re: Review of 3.15.1. The table element)
- Re: Review of 3.15.1. The table element
- <object> content-type sniffing (detailed review of Semantics)
- Re: Review of 3.15.1. The table element
- Re: Add Example Explaining that Alt Text is Dependent Upon the Context
- Re: Add Example Explaining that Alt Text is Dependent Upon the Context
- Re: Add Example Explaining that Alt Text is Dependent Upon the Context
- Re: [HDP] Response to Review of HTML Design Principles Questionnaire
- Re: [HDP] Secure by design
- Re: [HDP] Secure by design
- Re: Finding Real Use Cases for Longdesc
- Re: [HDP] Secure by design
- Re: Finding Real Use Cases for Longdesc
- Re: [HDP] Secure by design
- Finding Real Use Cases for Longdesc
- Re: Review of 3.15.1. The table element
- Re: Review of 3.15.1. The table element
- Re: (Un)Ordered lists
- Re: Add Example Explaining that Alt Text is Dependent Upon the Context
- Re: [HDP] Response to Review of HTML Design Principles Questionnaire
- Re: [HDP] Response to Review of HTML Design Principles Questionnaire
- Add Example Explaining that Alt Text is Dependent Upon the Context
- Re: [HDP] Response to Review of HTML Design Principles Questionnaire
- Re: [HDP] Response to Review of HTML Design Principles Questionnaire
- [HDP] Secure by design
- Re: [HDP] Response to Review of HTML Design Principles Questionnaire
- Re: [HDP] Support World Languages
- Re: Forms Taskforce participation
- [HDP] Pave the Cowpaths
- Re: Whitespace after </body> (detailed review of parsing algorithm)
- Re: Forms Taskforce participation
- Re: Empty vs no alt attribute (was Re: Baby Steps or Backwards Steps?)
- Re: Forms Taskforce participation
- Re: Whitespace after </body> (detailed review of parsing algorithm)
Wednesday, 22 August 2007
- Re: Empty vs no alt attribute (was Re: Baby Steps or Backwards Steps?)
- Re: Whitespace after </body> (detailed review of parsing algorithm)
- Re: [HDP] Response to Review of HTML Design Principles Questionnaire
- [HDP] Rename "Pave the Cowpaths" to something less analogy-prone
- Re: Forms Taskforce participation
- Re: [HDP] Support World Languages
- Re: [HDP] Solving real problems
- Re: review of content type rules by IETF/HTTP community
- Re: [HDP] Response to Review of HTML Design Principles Questionnaire
- Re: Review of 3.15.1. The table element
- Re: [HDP] Response to Review of HTML Design Principles Questionnaire
- Re: Review of 3.15.1. The table element
- Re: Forms Taskforce participation
- Re: Forms Taskforce participation
- Re: Forms Taskforce participation
- Re: Review of 3.15.1. The table element
- Re: Review of 3.15.1. The table element
- Re: Review of 3.15.1. The table element
- Re: Review of 3.15.1. The table element
- Re: Review of 3.15.1. The table element
- Re: Review of 3.15.1. The table element
- Re: [HDP] Response to Review of HTML Design Principles Questionnaire
- Review of 3.15.1. The table element
- Web Forms 2.0 and a Cross-Browser Implementation
- Re: [HDP] Response to Review of HTML Design Principles Questionnaire
- Re: IE's AND EVERYONE ELSE'S object implementation problems (was RE: Baby Steps or Backwards Steps?)
- Re: [HDP] Response to Review of HTML Design Principles Questionnaire
- Re: [HDP] Response to Review of HTML Design Principles Questionnaire
- [HDP] Response to Review of HTML Design Principles Questionnaire
- Case-insensitive comparison (part of my detailed review of tokenization)
- Removing the data attribute on <object> (detailed review of Semantics)
- Re: IE's AND EVERYONE ELSE'S object implementation problems (was RE: Baby Steps or Backwards Steps?)
- Re: Forms Taskforce participation
- Whitespace after </body> (detailed review of parsing algorithm)
- Re: (code, sample output and keyboard/device input <code>, <samp>, <kybd>) part of my review of 3.12 Phrase elements
- Re: Review of 3.14.11. The canvas element
- Re: Empty vs no alt attribute (was Re: Baby Steps or Backwards Steps?)
- Re: User Testing elements of HTML 5 spec
- Re: Empty vs no alt attribute (was Re: Baby Steps or Backwards Steps?)
- Supporting real accessibility Re: Seeing the open issues
- Re: Review of 3.14.11. The canvas element
- Re: Forms Taskforce participation
- Re: Difference of content model of |ins| and |del| (part of detailed spec review of Edits)
- Re: review of content type rules by IETF/HTTP community
- Re: IE's AND EVERYONE ELSE'S object implementation problems (was RE: Baby Steps or Backwards Steps?)
- Re: Forms Taskforce participation
- Re: review of content type rules by IETF/HTTP community
- Re: IE's AND EVERYONE ELSE'S object implementation problems (was RE: Baby Steps or Backwards Steps?)
- Re: IE's AND EVERYONE ELSE'S object implementation problems (was RE: Baby Steps or Backwards Steps?)
Tuesday, 21 August 2007
Wednesday, 22 August 2007
- Re: IE's AND EVERYONE ELSE'S object implementation problems (was RE: Baby Steps or Backwards Steps?)
- Re: Forms Taskforce participation
- Fwd: Review of Distributed Extensibility in HTML5
- Re: review of content type rules by IETF/HTTP community
- Re: Empty vs no alt attribute (was Re: Baby Steps or Backwards Steps?)
- Re: review of content type rules by IETF/HTTP community
- Re: getting feedback from other w3c "accessibility" lists (was: A better ALT)
- Re: review of content type rules by IETF/HTTP community
- Re: Forms Taskforce participation
- Re: review of content type rules by IETF/HTTP community
- Re: link warmth
- Re: getting feedback from other w3c "accessibility" lists (was: A better ALT)
- Re: IE's AND EVERYONE ELSE'S object implementation problems (was RE: Baby Steps or Backwards Steps?)
- Re: IE's AND EVERYONE ELSE'S object implementation problems (was RE: Baby Steps or Backwards Steps?)
- Re: Forms Taskforce participation
- Re: review of content type rules by IETF/HTTP community
- Re: review of content type rules by IETF/HTTP community
- Re: review of content type rules by IETF/HTTP community
- Re: Empty vs no alt attribute (was Re: Baby Steps or Backwards Steps?)
- Re: Seeing the open issues
- Re: IE's AND EVERYONE ELSE'S object implementation problems (was RE: Baby Steps or Backwards Steps?)
Tuesday, 21 August 2007
- Re: IE's AND EVERYONE ELSE'S object implementation problems (was RE: Baby Steps or Backwards Steps?)
- Re: IE's AND EVERYONE ELSE'S object implementation problems (was RE: Baby Steps or Backwards Steps?)
- Re: review of content type rules by IETF/HTTP community
- Re: Forms Taskforce participation
- Re: review of content type rules by IETF/HTTP community
- Re: review of content type rules by IETF/HTTP community
- Re: IE's AND EVERYONE ELSE'S object implementation problems (was RE: Baby Steps or Backwards Steps?)
- Re: IE's AND EVERYONE ELSE'S object implementation problems (was RE: Baby Steps or Backwards Steps?)
- Re: review of content type rules by IETF/HTTP community
- Re: Forms Taskforce participation
- Re: review of content type rules by IETF/HTTP community
- Re: IE's AND EVERYONE ELSE'S object implementation problems (was RE: Baby Steps or Backwards Steps?)
- Re: Implementing HTMLDocument on all Documents (detailed review of the DOM)
- Re: Implementing HTMLDocument on all Documents (detailed review of the DOM)
- RE: IE's AND EVERYONE ELSE'S object implementation problems (was RE: Baby Steps or Backwards Steps?)
- Re: review of content type rules by IETF/HTTP community
- Re: Forms Taskforce participation
- Re: review of content type rules by IETF/HTTP community
- Re: review of content type rules by IETF/HTTP community
- Re: Seeing the open issues
- Re: no mention of BOMs in sniffing algorithm
- Re: IE's AND EVERYONE ELSE'S object implementation problems (was RE: Baby Steps or Backwards Steps?)
- Re: Empty vs no alt attribute (was Re: Baby Steps or Backwards Steps?)
- Re: Review of 3.14.11. The canvas element
- Re: (Un)Ordered lists
- Re: (Un)Ordered lists
- Re: Seeing the open issues
- Re: review of content type rules by IETF/HTTP community
- Re: Seeing the open issues
- Re: review of content type rules by IETF/HTTP community (new thread?)
- Re: Rewriting |m|
- Re: (Un)Ordered lists
- Re: review of content type rules by IETF/HTTP community (new thread?)
- Rewriting |m|
- Visible greater-than sign (part of detailed review of edits)
- Re: Suggestions for the Pave the Cowpaths Examples
- Re: Implementing HTMLDocument on all Documents (detailed review of the DOM)
- Difference of content model of |ins| and |del| (part of detailed spec review of Edits)
- Re: review of content type rules by IETF/HTTP community
- Re: Placeholder Text for Text Boxes
- Review of 3.14.11. The canvas element
- Re: Implementing HTMLDocument on all Documents (detailed review of the DOM)
- RE: IE's AND EVERYONE ELSE'S object implementation problems (was RE: Baby Steps or Backwards Steps?)
- Re: Implementing HTMLDocument on all Documents (detailed review of the DOM)
- Re: review of content type rules by IETF/HTTP community
- (Un)Ordered lists
- Re: Implementing HTMLDocument on all Documents (detailed review of the DOM)
- Re: review of content type rules by IETF/HTTP community
- Re: review of content type rules by IETF/HTTP community
- Re: Empty vs no alt attribute (was Re: Baby Steps or Backwards Steps?)
- Re: Implementing HTMLDocument on all Documents (detailed review of the DOM)
- RE: Empty vs no alt attribute (was Re: Baby Steps or Backwards Steps?)
- Re: Empty vs no alt attribute (was Re: Baby Steps or Backwards Steps?)
- Re: no mention of BOMs in sniffing algorithm
- Re: Forms Taskforce participation
- Re: review of content type rules by IETF/HTTP community (new thread?)
- Re: Placeholder Text for Text Boxes
- Re: Forms Taskforce participation
- Re: review of content type rules by IETF/HTTP community
- Re: Suggestions for the Pave the Cowpaths Examples
- Re: document.title (detailed review of the DOM)
- IE's AND EVERYONE ELSE'S object implementation problems (was RE: Baby Steps or Backwards Steps?)
- Re: review of content type rules by IETF/HTTP community
- Re: review of content type rules by IETF/HTTP community
- Re: Implementing HTMLDocument on all Documents (detailed review of the DOM)
- Re: review of content type rules by IETF/HTTP community
- Re: Implementing HTMLDocument on all Documents (detailed review of the DOM)
- Re: Seeing the open issues
- Implementing HTMLDocument on all Documents (detailed review of the DOM)
- IE's object implementation problems (was RE: Baby Steps or Backwards Steps?)
- HTML5 - Video and audio codecs for video elements
- Re: review of content type rules by IETF/HTTP community
- Re: Seeing the open issues
- Re: Seeing the open issues
- Re: review of content type rules by IETF/HTTP community
- Re: Placeholder Text for Text Boxes
- Re: Other syntax: part of my review of 8 The HTML syntax
- Re: [Offtopic] Re: Placeholder Text for Text Boxes
- Re: Forms Taskforce participation
- Re: Heuristic Tests for Data Tables (Discussion)
- Re: Forms Taskforce participation
- Hierarchical link types
- no mention of BOMs in sniffing algorithm
Monday, 20 August 2007
- Re: numeric character references and Unicode surrogate pairs: part of my review of 8 The HTML syntax
- is OBJECT broken? if so by whom & what can be done?
- Permitted slash not defined in terms of void elements (part of my detailed review of the tokenization section)
- RE: Placeholder Text for Text Boxes
- Re: Seeing the open issues
- Seeing the open issues
- Re: review of content type rules by IETF/HTTP community
- Re: review of content type rules by IETF/HTTP community
- Re: review of content type rules by IETF/HTTP community
- Re: review of content type rules by IETF/HTTP community
- Re: review of content type rules by IETF/HTTP community
- Re: review of content type rules by IETF/HTTP community
- Re: Suggestions for the Pave the Cowpaths Examples
- Re: Suggestions for the Pave the Cowpaths Examples
- Re: review of content type rules by IETF/HTTP community
- Re: Suggestions for the Pave the Cowpaths Examples
- Re: review of content type rules by IETF/HTTP community
- Suggestions for the Pave the Cowpaths Examples
- Re: review of content type rules by IETF/HTTP community
- content type configuration prototype, usability testing? [was: review ... by IETF/HTTP community]
- Re: review of content type rules by IETF/HTTP community
- RE: Baby Steps or Backwards Steps?
- Re: review of content type rules by IETF/HTTP community
- Re: numeric character references and Unicode surrogate pairs: part of my review of 8 The HTML syntax
- Re: review of content type rules by IETF/HTTP community
- Re: review of content type rules by IETF/HTTP community
- Re: review of content type rules by IETF/HTTP community
- Re: review of content type rules by IETF/HTTP community
- Re: Placeholder Text for Text Boxes
- Re: Placeholder Text for Text Boxes
- Re: numeric character references and Unicode surrogate pairs: part of my review of 8 The HTML syntax
- Re: review of content type rules by IETF/HTTP community
- [Offtopic] Re: Placeholder Text for Text Boxes
- Re: Placeholder Text for Text Boxes
- Re: review of content type rules by IETF/HTTP community
- Re: Placeholder Text for Text Boxes
- Re: Placeholder Text for Text Boxes
- Placeholder Text for Text Boxes
- Re: review of content type rules by IETF/HTTP community
- process proposals should start off-list [was: ... categorize messages and threads]
- Re: review of content type rules by IETF/HTTP community
- Re: numeric character references and Unicode surrogate pairs: part of my review of 8 The HTML syntax
- Re: numeric character references and Unicode surrogate pairs: part of my review of 8 The HTML syntax
- Re: numeric character references and Unicode surrogate pairs: part of my review of 8 The HTML syntax
- Review of table processing model (section 3.15.11. Processing model)
- Re: Other syntax: part of my review of 8 The HTML syntax
- Re: using an attribute to categorize the @alt state [was Baby Steps or Backwards Steps?]
- Re: M| Motion to use prefix to categorize messages and threads (Robert's Rules of Order over Email)
- Re: abbreviation exposition and pronunciation
- Re: using an attribute to categorize the @alt state [was Baby Steps or Backwards Steps?]
- Re: M| Motion to use prefix to categorize messages and threads (Robert's Rules of Order over Email)
- Re: Empty vs no alt attribute (was Re: Baby Steps or Backwards Steps?)
- Re: Empty vs no alt attribute (was Re: Baby Steps or Backwards Steps?)
Sunday, 19 August 2007
- Re: review of content type rules by IETF/HTTP community
- Re: review of content type rules by IETF/HTTP community
- Re: review of content type rules by IETF/HTTP community
- Re: abbreviation exposition and pronunciation
- Re: M| Motion to use prefix to categorize messages and threads (Robert's Rules of Order over Email)
- M| Motion to use prefix to categorize messages and threads (Robert's Rules of Order over Email)
- Design Principles Premise
- numeric character references and Unicode surrogate pairs: part of my review of 8 The HTML syntax
- Re: abbreviation exposition and pronunciation
- Re: using an attribute to categorize the @alt state [was Baby Steps or Backwards Steps?]
- Re: Empty vs no alt attribute (was Re: Baby Steps or Backwards Steps?)
- Re: using an attribute to categorize the @alt state [was Baby Steps or Backwards Steps?]
Saturday, 18 August 2007
- Re: using an attribute to categorize the @alt state [was Baby Steps or Backwards Steps?]
- Re: Empty vs no alt attribute (was Re: Baby Steps or Backwards Steps?)
- Re: Empty vs no alt attribute (was Re: Baby Steps or Backwards Steps?)
- Re: Stripping leading line feeds
- Stripping leading line feeds
- Re: A better longdesc
- Re: A better ALT
- A better ALT
- Re: Empty vs no alt attribute (was Re: Baby Steps or Backwards Steps?)
- getting feedback from other w3c "accessibility" lists (was: A better ALT)
- A better ALT
- Re: edits to the draft should reflect the consensus of the WG
- [HDP] 3.3. Media Independence
- editorial comment about "4.7.4. Content-Type sniffing: feed or HTML"
- Re: review of content type rules by IETF/HTTP community
- Re: edits to the draft should reflect the consensus of the WG
- Re: review of content type rules by IETF/HTTP community
- Re: Dropping <input usemap="">
- Re: Empty vs no alt attribute (was Re: Baby Steps or Backwards Steps?)
Friday, 17 August 2007
- Re: review of content type rules by IETF/HTTP community
- Re: review of content type rules by IETF/HTTP community
- review of content type rules by IETF/HTTP community
- Re: Empty vs no alt attribute (was Re: Baby Steps or Backwards Steps?)
Thursday, 16 August 2007
Friday, 17 August 2007
- Re: Dropping <input usemap="">
- Editorial issues (part of detailed review of "Determining the type of a new resource in a browsing context")
- Step 10 of Feed/HTML sniffing (part of detailed review of "Determining the type of a new resource in a browsing context")
- Re: edits to the draft should reflect the consensus of the WG
- Re: edits to the draft should reflect the consensus of the WG
- Re: Heuristic Tests for Data Tables (Discussion)
- please review "XHTML Role Attribute Module" working draft
- <figure> and <img> (was Re: edits to the draft should reflect the consensus of the WG)
- Re: edits to the draft should reflect the consensus of the WG
- Re: table, cell, heading, leader, trailer, header, footer, runner, TABLE, THEAD, TFOOT, part of my review of 3.15 Tabular data
- review of HTML Design Principles - questionnaire
- Re: using an attribute to categorize the @alt state [was Baby Steps or Backwards Steps?]
- Re: [Spam] Re: using an attribute to categorize the @alt state [was Baby Steps or Backwards Steps?]
- Re: using an attribute to categorize the @alt state [was Baby Steps or Backwards Steps?]
- [HDP] 3.3. Media Independence
- Re: table, cell, heading, leader, trailer, header, footer, runner, TABLE, THEAD, TFOOT, part of my review of 3.15 Tabular data
- Re: HTML Design Principles Review
- Re: Ian's Approach to Editing (Was: using an attribute to categorize the @alt state)
- Re: Ian's Approach to Editing (Was: using an attribute to categorize the @alt state)
- Re: using an attribute to categorize the @alt state [was Baby Steps or Backwards Steps?]
- Re: Form Serialization
- Re: using an attribute to categorize the @alt state [was Baby Steps or Backwards Steps?]
- Re: Dropping <input usemap="">
- Re: table, cell, heading, leader, trailer, header, footer, runner, TABLE, THEAD, TFOOT, part of my review of 3.15 Tabular data
- Re: table, cell, heading, leader, trailer, header, footer, runner, TABLE, THEAD, TFOOT, part of my review of 3.15 Tabular data
- Re: Form Serialization
- Re: using an attribute to categorize the @alt state [was Baby Steps or Backwards Steps?]
- Re: QA vs. Baby Steps, Cowpaths, RealProblems
- QA vs. Baby Steps, Cowpaths, RealProblems
- Re: using an attribute to categorize the @alt state [was Baby Steps or Backwards Steps?]
- Re: [HDP] error in "Support World Languages"
- Re: [HDP] error in "Support World Languages"
- Re: Dropping <input usemap="">
- Re: Form Serialization
Thursday, 16 August 2007
- [HDP] error in "Support World Languages"
- [ FIELDSET ] - disabled and readonly
- Form Serialization
- Re: using an attribute to categorize the @alt state [was Baby Steps or Backwards Steps?]
- Re: HTML Design Principles Review
- Re: HTML Design Principles Review
- Re: Support for Design Principles
- Re: Support for Design Principles (was: Design Principles survey delayed)
- Re: Baby Steps or Backwards Steps?
- Re: Baby Steps or Backwards Steps?
- Fwd: Baby Steps or Backwards Steps?
- Re: Baby Steps or Backwards Steps?
- Re: Baby Steps or Backwards Steps?
- Re: Baby Steps or Backwards Steps?
- Re: link warmth
- RE: Baby Steps or Backwards Steps?
- Re: link warmth
Wednesday, 15 August 2007
Thursday, 16 August 2007
- Re: Baby Steps or Backwards Steps?
- Re: 4.5. Interfaces for URI manipulation
- Re: Empty vs no alt attribute (was Re: Baby Steps or Backwards Steps?)
- Re: Design Principles survey delayed
- HTML Design Principles Review
- Re: Requirements for research (Was: Dropping <input usemap="">)
- Empty vs no alt attribute (was Re: Baby Steps or Backwards Steps?)
- Re: Baby Steps or Backwards Steps?
- Re: Dropping <input usemap="">
- Re: Requirements for research (Was: Dropping <input usemap="">)
- Re: Dropping <input usemap="">
- Re: Requirements for research (Was: Dropping <input usemap="">)
- Re: Requirements for research (Was: Dropping <input usemap="">)
- Re: Requirements for research (Was: Dropping <input usemap="">)
- Re: Dropping <input usemap="">
- 4.5. Interfaces for URI manipulation
- Re: Requirements for research (Was: Dropping <input usemap="">)
- Re: Dropping <input usemap="">
- Re: Requirements for research (Was: Dropping <input usemap="">)
- Re: Requirements for research (Was: Dropping <input usemap="">)
- Re: Requirements for research (Was: Dropping <input usemap="">)
- Re: Support for Design Principles (was: Design Principles survey delayed)
- Re: Requirements for research (Was: Dropping <input usemap="">)
- Re: Dropping <input usemap="">
- Re: Dropping <input usemap="">
- Re: Requirements for research (Was: Dropping <input usemap="">)
- Re: Dropping <input usemap="">
- Re: Dropping <input usemap="">
- Re: edits to the draft should reflect the consensus of the WG
- Re: Evidence of usefulness of specific accessibility solutions (was Rewording the Design Principles)
- Re: Baby Steps or Backwards Steps?
- Re: Heuristic Tests for Data Tables (Discussion)
- Re: Baby Steps or Backwards Steps?
- Re: Maxmizing Useful alt Text (Was: Baby Steps or Backwards Steps?)
- Re: Dropping <input usemap="">
- Re: edits to the draft should reflect the consensus of the WG
- Re: Baby Steps or Backwards Steps?
- Re: Dropping <input usemap="">
- Re: Baby Steps or Backwards Steps?
- Re: Omitting alt Where It's Unknown (Was: Baby Steps or Backwards Steps?)
- Re: Baby Steps or Backwards Steps?
- Re: Support for Design Principles (was: Design Principles survey delayed)
- Re: Baby Steps or Backwards Steps?
- Re: using an attribute to categorize the @alt state
- Re: Baby Steps or Backwards Steps?
- Re: using an attribute to categorize the @alt state
- Re: Baby Steps or Backwards Steps?
- Re: Baby Steps or Backwards Steps?
- Re: edits to the draft should reflect the consensus of the WG
- using an attribute to categorize the @alt state [was Baby Steps or Backwards Steps?]
- Re: Dropping <input usemap="">
- Re: Dropping <input usemap="">
- Re: edits to the draft should reflect the consensus of the WG
- Re: Baby Steps or Backwards Steps?
- Re: edits to the draft should reflect the consensus of the WG
- Re: Baby Steps or Backwards Steps?
- Re: Dropping <input usemap="">
- Re: Dropping <input usemap="">
- Re: Dropping <input usemap="">
- Re: Baby Steps or Backwards Steps?
- edits to the draft should reflect the consensus of the WG
- Re: Other syntax: part of my review of 8 The HTML syntax
- Re: Baby Steps or Backwards Steps?
- Re: Requirements for research (Was: Dropping <input usemap="">)
- Re: The arbitrary 80% (Baby Steps)
- Re: Dropping <input usemap="">
- Re: Dropping <input usemap="">
- Re: [admin] W3C Wiki migration
- Re: Dropping <input usemap="">
- Re: Dropping <input usemap="">
Wednesday, 15 August 2007
- Re: Dropping <input usemap="">
- Re: Research needs tracking
- Re: Baby Steps or Backwards Steps?
- Re: Dropping <input usemap="">
- Re: Dropping <input usemap="">
- Re: Baby Steps or Backwards Steps?
- Re: Dropping <input usemap="">
- Re: Dropping <input usemap="">
- Re: unconference agenda for HTML WG meeting 8-9 Nov?
- Re: Dropping <input usemap="">
- Re: Dropping <input usemap="">
- practical use/techniques of alt attribute for images
- Re: Dropping <input usemap="">
- Re: Baby Steps or Backwards Steps?
- Re: agenda HTML WG 16 Aug: design principles, spec reviews, table headers, XML serialization name, forms TF, ...
- Re: Baby Steps or Backwards Steps?
- agenda HTML WG 16 Aug: design principles, spec reviews, table headers, XML serialization name, forms TF, ...
- Baby Steps or Backwards Steps?
- Re: Dropping <input usemap="">
- Re: Distributed Extensibility
- Forms Taskforce participation
- Design Principles survey delayed
- Re: Dropping <input usemap="">
- Re: Research needs tracking
- agenda HTML WG teleconference 16 Aug (in progress)
- RE: Ruby in HTML
- Re: [admin] W3C Wiki migration
- Re: [admin] W3C Wiki migration
- Re: Dropping <input usemap="">
- Re: Dropping <input usemap="">
- Re: Keeping some order in the wiki
- Re: Keeping some order in the wiki
- Re: Stephen Ferg's Table Research
- Re: Serializing PIs in HTML (detailed review of Serializing HTML fragments)
- Re: Dropping <input usemap="">
- Re: Stephen Ferg's Table Research
- Editorial: "child node" (detailed review of Serializing HTML fragments)
- Re: Dropping <input usemap="">
- <object>: should the name attribute be allowed for form submission with plug-ins?
- Serializing PIs in HTML (detailed review of Serializing HTML fragments)
- Re: Stephen Ferg's Table Research
- Re: Stephen Ferg's Table Research
- Requirements for research (Was: Dropping <input usemap="">)
- Re: Dropping <input usemap="">
- Re: editing the wiki Re: The arbitrary 80% (Baby Steps)
- Re: Dropping <input usemap="">
- Re: table, cell, heading, leader, trailer, header, footer, runner, TABLE, THEAD, TFOOT, part of my review of 3.15 Tabular data
- Re: editing the wiki Re: The arbitrary 80% (Baby Steps)
Tuesday, 14 August 2007
Wednesday, 15 August 2007
- editing the wiki Re: The arbitrary 80% (Baby Steps)
- Re: The arbitrary 80% (Baby Steps)
- Re: The arbitrary 80% (Baby Steps)
- Re: Keeping some order in the wiki
- Re: Keeping some order in the wiki
- Re: Dropping <input usemap="">
- Re: Keeping some order in the wiki
- The arbitrary 80% (Baby Steps)
Tuesday, 14 August 2007
Wednesday, 15 August 2007
- Re: Dropping <input usemap="">
- Re: Dropping <input usemap="">
- Re: Stephen Ferg's Table Research
- Re: Stephen Ferg's Table Research
- Re: Ruby in HTML
- Re: [admin] W3C Wiki migration
- Re: Keeping some order in the wiki
Tuesday, 14 August 2007
- Re: Dropping <input usemap="">
- Re: Keeping some order in the wiki (was Re: problem-statements for HTML 4.01 differences)
- Re: Improving the Header Relationship Algorithm (Discussion)
- Heuristic Tests for Data Tables (Discussion)
- Keeping some order in the wiki (was Re: problem-statements for HTML 4.01 differences)
- Re: Heuristic Tests for Data Tables (Discussion)
- Heuristic Tests for Data Tables (Discussion)
- Re: Dropping <input usemap="">
- Re: Dropping <input usemap="">
- Re: Dropping <input usemap="">
- Re: Dropping <input usemap=""> (was: Rewording the Design Principles: Pave the Cowpaths and Don't Reinvent the Wheel)
- Starting On Topic (Rant)
- Re: Rewording the Design Principles: Pave the Cowpaths and Don't Reinvent the Wheel
- Re: highlighting of "major known issues" in the working draft
- Re: Rewording the Design Principles: Pave the Cowpaths and Don't Reinvent the Wheel
- Re: highlighting of "major known issues" in the working draft
- Re: Rewording the Design Principles: Pave the Cowpaths and Don't Reinvent the Wheel
- Re: highlighting of "major known issues" in the working draft
- Re: Rewording the Design Principles: Pave the Cowpaths and Don't Reinvent the Wheel
- Re: Other syntax: part of my review of 8 The HTML syntax
- Re: Other syntax: part of my review of 8 The HTML syntax
- highlighting of "major known issues" in the working draft
- Other syntax: part of my review of 8 The HTML syntax
- Re: Stephen Ferg's Table Research
- Re: Stephen Ferg's Table Research
- Re: Research needs tracking
- Re: Stephen Ferg's Table Research
- Re: Rewording the Design Principles: Pave the Cowpaths and Don't Reinvent the Wheel]
- Research needs tracking
- Re: Stephen Ferg's Table Research
- problem-statements for HTML 4.01 differences
- Re: Stephen Ferg's Table Research
- Re: Stephen Ferg's Table Research
- Re: Stephen Ferg's Table Research
- WYSIWYG, GUI, visual and non-semantic editors: final part of my review of 9 WYSIWYG editors
- Re: Rewording the Design Principles: Pave the Cowpaths and Don't Reinvent the Wheel
- Re: Stephen Ferg's Table Research
- Re: [admin] W3C Wiki migration
Monday, 13 August 2007
- WYSIWYG, GUI, visual and non-semantic editors: part of my review of 9 WYSIWYG editors
- Re: HTML5 Draft Request: use an ISO 639-2 specified language
- Re: Rewording the Design Principles: Pave the Cowpaths and Don't Reinvent the Wheel
- Re: HTML5 Draft Request: use an ISO 639-2 specified language
- Re: HTML5 Draft Request: use an ISO 639-2 specified language
- Re: [admin] W3C Wiki migration
- HTML5 Draft Request: use an ISO 639-2 specified language
- Re: [admin] W3C Wiki migration
- Re: Improving the Header Relationship Algorithm (Discussion)
- Re: Distributed Extensibility
- Re: Rewording the Design Principles: Pave the Cowpaths and Don't Reinvent the Wheel
- Re: Rewording the Design Principles: Pave the Cowpaths and Don't Reinvent the Wheel
- a web site that is incompatible with HTML5 namespace requirements for HTML serialization
- Rewording the Design Principles: Pave the Cowpaths and Don't Reinvent the Wheel
- Re: Distributed Extensibility
- Re: Distributed Extensibility
- Improving the Header Relationship Algorithm (Discussion)
- Re: [admin] W3C Wiki migration
- Re: Distributed Extensibility
- Re: 3.8.10. The address element
- Stephen Ferg's Table Research
- Re: HEADERS, FOR whom - any ID?
- Re: 3.8.10. The address element
- Multipage version of spec
- Re: [admin] W3C Wiki migration
- Re: [admin] W3C Wiki migration
- Re: non-leading <param>s in <object> fallback (detailed review of Semantics)
- Re: Text presentation of image maps (detailed review of Semantics)
- Re: 3.8.10. The address element
- Re: non-leading <param>s in <object> fallback (detailed review of Semantics)
- Re: [admin] W3C Wiki migration
- Re: [admin] W3C Wiki migration
- [admin] W3C Wiki migration
Friday, 10 August 2007
- Re: Review: 3.4.6. The irrelevant attribute
- COLGROUP and COL, TR and TBODY: part of my review of 3.15 Tabular data
- table, DOM interfaces, cell, heading, leader, trailer, header, footer, runner, TABLE, CAPTION, COLGROUP, COL, THEAD, TFOOT, TR, part of my review of 3.15 Tabular data
- table, presentational attributes, 2-D 2d 2 dimensional cells, data, header,heading, attribute inheritance, TABLE, CAPTION, COLGROUP, COL, THEAD, TFOOT, TR, part of my review of 3.15 Tabular data
Thursday, 9 August 2007
- Re: SMIL 3 WD and HTML 5 Editor's draft
- Re: table, column group, column, row groups, TABLE, CAPTION, COLGROUP, COL, THEAD, TFOOT, TR, part of my review of 3.15 Tabular data
- table, cell, heading, row, header, TD, TH,TR: part of my review of 3.15 Tabular data
- table, column group, column, row groups, TABLE, CAPTION, COLGROUP, COL, THEAD, TFOOT, TR, part of my review of 3.15 Tabular data
- SMIL 3 WD and HTML 5 Editor's draft
- Re: HEADERS, FOR whom - any ID?
- Re: HEADERS, FOR whom - any ID?
- Re: HEADERS, FOR whom - any ID?
Wednesday, 8 August 2007
- Re: HEADERS, FOR whom - any ID?
- Re: HEADERS, FOR whom - any ID?
- Re: HEADERS, FOR whom - any ID?
- Re: 3.8. Sections
- Re: complex tables: heading cells and summary cells
- Re: 3.8. Sections
- Re: complex tables: heading cells and summary cells
- Re: 3.8. Sections
- Multipage version of spec (was Re: 3.8.10. The address element)
- Re: 3.8. Sections
- Re: 3.8.10. The address element
- Re: 3.8. Sections
- Re: 3.8. Sections
- Text presentation of image maps with <object> (detailed review of Semantics)
- Re: 3.8. Sections
- Re: 3.8. Sections
- Re: 3.8. Sections
- Text presentation of image maps (detailed review of Semantics)
- Re: 9. WYSIWYG editor (enforcing the signature)
- Re: 3.8.10. The address element
- Re: meta refresh (3.7.5.3. Pragma directives)
- Re: meta refresh (3.7.5.3. Pragma directives)
- Re: meta refresh (3.7.5.3. Pragma directives)
- Re: meta refresh (3.7.5.3. Pragma directives)
- Re: 3.8. Sections
- Re: 3.8.10. The address element
- Re: meta refresh (3.7.5.3. Pragma directives)
- Re: HEADERS, FOR whom - any ID?
- Re: meta refresh (3.7.5.3. Pragma directives)
- Re: HEADERS, FOR whom - any ID?
- Re: HEADERS, FOR whom - any ID?
- Re: complex tables: heading cells and summary cells
- Re: complex tables: heading cells and summary cells
- Re: HEADERS, FOR whom - any ID?
Tuesday, 7 August 2007
- Re: HEADERS, FOR whom - any ID?
- Re: HEADERS, FOR whom - any ID?
- Re: 3.8. Sections
- Re: Determining Script Type
- Re: meta refresh (3.7.5.3. Pragma directives)
- Re: meta refresh (3.7.5.3. Pragma directives)
- complex tables: heading cells and summary cells
- Re: meta refresh (3.7.5.3. Pragma directives)
- Determining Script Type
- Re: authoring @lang and @dir (was 3.6. The root element)
- Re: authoring @lang and @dir (was 3.6. The root element)
- Re: HEADERS, FOR whom - any ID?
- Re: 3.8.10. The address element
- Re: 3.8. Sections
- Re: authoring @lang and @dir (was 3.6. The root element)
- Re: Rewording Algorithms and Script Types
- Re: 3.8.10. The address element
- Re: meta refresh (3.7.5.3. Pragma directives)
- Re: meta refresh (3.7.5.3. Pragma directives)
- Re: meta refresh (3.7.5.3. Pragma directives)
- Re: meta refresh (3.7.5.3. Pragma directives)
- rewording algorithms
- Re: 3.8.10. The address element
- Re: (code, sample output and keyboard/device input <code>, <samp>, <kybd>) part of my review of 3.12 Phrase elements
- Re: meta refresh (3.7.5.3. Pragma directives)
- Re: 3.8.10. The address element
- Re: meta refresh (3.7.5.3. Pragma directives)
- Re: meta refresh (3.7.5.3. Pragma directives)
- Re: 3.8.10. The address element
- meta refresh (3.7.5.3. Pragma directives)
- Re: 3.8.10. The address element
- 3.8. Sections
- 3.8.10. The address element
- non-leading <param>s in <object> fallback (detailed review of Semantics)
- Re: authoring @lang and @dir (was 3.6. The root element)
- Re: 9. WYSIWYG editor (enforcing the signature)
- Re: HEADERS, FOR whom - any ID?
- Re: Distributed Extensibility
- RE: authoring @lang and @dir (was 3.6. The root element)
- Re: authoring @lang and @dir (was 3.6. The root element)
- Re: authoring @lang and @dir (was 3.6. The root element)
- Re: Data Table Collections (Research)
- Re: HEADERS, FOR whom - any ID?
Monday, 6 August 2007
Tuesday, 7 August 2007
- Re: HEADERS, FOR whom - any ID?
- Re: 9. WYSIWYG editor (enforcing the signature)
- Re: HEADERS, FOR whom - any ID?
- Re: Table Collection - W3C HTML Working Group Top 200 Survey
Monday, 6 August 2007
- Re: Table Collection - W3C HTML Working Group Top 200 Survey
- Re: HEADERS, FOR whom - any ID?
- Re: Data Table Collections (Research)
- Re: Semantics (was : Formal Recorded Complaint)
- Re: Likert scale for survey? (on design principles)
- Re: Distributed Extensibility
- Re: <p><table> parsing (detailed review of parsing algorithm)
- Re: HEADERS, FOR whom - any ID?
- Re: Semantics (was : Formal Recorded Complaint)
- Re: HEADERS, FOR whom - any ID?
- Re: Likert scale for survey? (on design principles)
- Re: Likert scale for survey? (on design principles)
- Re: Semantics (was : Formal Recorded Complaint)
- Re: Semantics (was : Formal Recorded Complaint)
- Re: Distinguishing different aspects of accessibility
- Semantics (was : Formal Recorded Complaint)
- Re: Formal Recorded Complaint
- Re: Distributed Extensibility
- Re: Likert scale for survey? (on design principles)
- Re: Distinguishing different aspects of accessibility
- Re: Distributed Extensibility
- Re: Assertions regarding the quality of HTML documents
- Re: Distinguishing different aspects of accessibility
- Re: 3.14.11. The canvas element
- Assertions regarding the quality of HTML documents
- Re: Distinguishing different aspects of accessibility
- Re: 9. WYSIWYG editor (enforcing the signature)
- Re: 9. WYSIWYG editor (enforcing the signature)
- Re: 9. WYSIWYG editor (enforcing the signature)
- Re: Marking up alternative versions of content
- Re: Distributed Extensibility
- Re: 9. WYSIWYG editor (enforcing the signature)
- Re: Marking up alternative versions of content
- Re: Data Table Collections (Research)
- Data Table Collections (Research)
- Re: HEADERS, FOR whom - any ID?
- Re: HEADERS, FOR whom - any ID?
- Re: Marking up alternative versions of content
- Re: integration of WF2 into HTML5 draft -- when, if, and how?
- Re: Marking up alternative versions of content
- Re: HEADERS, FOR whom - any ID?
Sunday, 5 August 2007
- Detailed review of 3.14.9. Media elements
- Re: Distributed Extensibility
- Re: 3.14.11. The canvas element
- Re: Marking up alternative versions of content
- Re: Marking up alternative versions of content
- Re: Distributed Extensibility
- 3.8.8. The header element
- 3.14.11. The canvas element
- Re: Distributed Extensibility
- Re: Detailed review of 3.12.10. The time element
- Re: Detailed review of 3.12.10. The time element
- Re: Detailed review of 3.12.10. The time element
- Re: Detailed review of 3.12.10. The time element
- Re: integration of WF2 into HTML5 draft -- when, if, and how?
- Re: Detailed review of 3.12.10. The time element
- Re: Detailed review of 3.12.10. The time element
- Re: arguments for retention of LEGEND and FIELDSET
- arguments for retention of LEGEND and FIELDSET
- Re: HEADERS, FOR whom - any ID?
- Re: integration of WF2 into HTML5 draft -- when, if, and how?
- Re: The <label>
- Re: integration of WF2 into HTML5 draft -- when, if, and how?
- Re: Detailed review of 3.12.10. The time element
- Re: integration of WF2 into HTML5 draft -- when, if, and how?
- Re: The canvas element (detailed review)
- Re: Marking up alternative versions of content
- Re: Marking up alternative versions of content
- Re: Distributed Extensibility
- Re: The <label>
- Re: transparent content model and proposed ALT element
Saturday, 4 August 2007
- Re: Marking up alternative versions of content
- integration of WF2 into HTML5 draft -- when, if, and how?
- Re: HEADERS, FOR whom - any ID?
- Re: HEADERS, FOR whom - any ID?
- Re: HEADERS, FOR whom - any ID?
- Re: 9. WYSIWYG editor (enforcing the signature)
- Re: Distributed Extensibility
- Re: The canvas element (detailed review)
- Detailed review of 3.12.10. The time element
- The <label>
- Re: 9. WYSIWYG editor (enforcing the signature)
- Re: Distributed Extensibility
- Re: Distributed Extensibility
- Re: DIV as an inline container
- Re: Distributed Extensibility
- Re: DIV as an inline container
- Re: Distributed Extensibility
- Re: Distributed Extensibility
- Re: HEADERS, FOR whom - any ID?
- Re: Distributed Extensibility
- Re: Distributed Extensibility
- Re: HEADERS, FOR whom - any ID?
- Re: Distributed Extensibility
- Re: 9. WYSIWYG editor (enforcing the signature) detailed review of
- Re: 9. WYSIWYG editor (enforcing the signature)
- Re: DIV as an inline container
- Re: The canvas element (detailed review)
- Re: 9. WYSIWYG editor (enforcing the signature) detailed review of
- Likert scale for survey?
- Re: Distributed Extensibility
- Re: Distributed Extensibility
- Re: Distributed Extensibility
- Re: DIV as an inline container
- Re: 9. WYSIWYG editor (enforcing the signature)
- W3C terminology (was Re: Rephrasing Universal Access Design Principle)
- Re: transparent content model and proposed ALT element
- Re: transparent content model
- Re: Marking up links to alternative versions of content
- Re: transparent content model
- Re: Marking up alternative versions of content
- transparent content model
- Re: Marking up alternative versions of content
- Re: Marking up alternative versions of content
- Re: The canvas element (detailed review)
- Re: HEADERS, FOR whom - any ID?
- Re: Marking up links to alternative versions of content
- HEADERS, FOR whom - any ID?
- Re: Marking up alternative versions of content
- Re: 3.15 Tabular Data Review
- Re: Rephrasing Universal Access Design Principle (was Re: Formal Recorded Complaint)
- Re: 9. WYSIWYG editor (enforcing the signature) detailed review of
- The canvas element (detailed review)
- Re: 9. WYSIWYG editor (enforcing the signature)
- DIV as an inline container
- Re: Marking up alternative versions of content
- Re: 9. WYSIWYG editor (enforcing the signature)
- Re: 9. WYSIWYG editor (enforcing the signature)
Friday, 3 August 2007
- Rephrasing Universal Access Design Principle (was Re: Formal Recorded Complaint)
- Re: Distributed Extensibility
- Re: 9. WYSIWYG editor (enforcing the signature)
- Re: 9. WYSIWYG editor (enforcing the signature)
- Re: 9. WYSIWYG editor (enforcing the signature)
- Re: 9. WYSIWYG editor (enforcing the signature)
- Re: Distinguishing different aspects of accessibility
- Re: 9. WYSIWYG editor (enforcing the signature)
- Re: 9. WYSIWYG editor (enforcing the signature) detailed review of
- Re: Distributed Extensibility
- Re: 9. WYSIWYG editor (enforcing the signature) detailed review of
- Re: ID Characters (was: Re: 3.4. Global attributes)
- Re: Distributed Extensibility
- care with subject lines, please [was: Formal Recorded Complaint]
- Re: Formal Recorded Complaint
- Re: Marking up links to alternative versions of content
- Re: Distributed Extensibility
- Re: Distributed Extensibility
- Issues surrounding Tables: backwards compatibility and complex tables
- Re: 9. WYSIWYG editor (enforcing the signature) detailed review of
- Re: 9. WYSIWYG editor (enforcing the signature) detailed review of
- Re: Distributed Extensibility
- Re: Distributed Extensibility
- Correction for 3.2.4.2. Vaguer moments in time
- Re: CR and LF in the input stream / as NCRs (detailed review of parsing algorithm)
- Re: 9. WYSIWYG editor (enforcing the signature)
- Review: 3.4.6. The irrelevant attribute
- 9. WYSIWYG editor (enforcing the signature)
- completion of review of "Prose" section (currently 3.9)
- Re: Distinguishing different aspects of accessibility (was Re: Marking up links to alternative versions of content)
- The br element: part of review of "Prose" section (currently 3.9)
- The p element: part of review of "Prose" section (currently 3.9)
- Re: Formal Recorded Complaint
- Re: Formal Recorded Complaint
- Re: Use Cases for The <canvas> Element
- Re: Maturity of XML
- Re: Marking up links to alternative versions of content
Thursday, 2 August 2007
- Re: Minutes, HTML WG 2007-08-02 phone conference
- Re: Distributed Extensibility
- Real solutions, semantics, and proposals of members of this WG
- Re: Minutes, HTML WG 2007-08-02 phone conference
- Re: authoring @lang and @dir (was 3.6. The root element)
- Re: CR and LF in the input stream / as NCRs (detailed review of parsing algorithm)
- Re: Comments on IRC log
- Re: Distributed Extensibility
- Minutes, HTML WG 2007-08-02 phone conference
- Re: Distributed Extensibility
- Re: Steps Towards a Common WG Vocabulary
- Re: Maturity of XML
- Re: Distributed Extensibility
- Re: ID Characters (was: Re: 3.4. Global attributes)
- Re: Distributed Extensibility
- Re: Distributed Extensibility
- Re: Marking up links to alternative versions of content
- Distinguishing different aspects of accessibility (was Re: Marking up links to alternative versions of content)
- Re: Entities (part of detailed review)
- Re: Distributed Extensibility
- Re: Maturity of XML
- Re: Distributed Extensibility
- Distributed Extensibility
- Re: Entities (part of detailed review)
- Re: Entities (part of detailed review)
- RE: @lang => @dir (was 3.6. The root element)
- Re: 3.15 Tabular Data Review
- RE: authoring @lang and @dir (was 3.6. The root element)
- Re: Use Cases for The <canvas> Element
- 3.8.5. The blockquote element
- Ruby in HTML
- Re: Formal Recorded Complaint
- Re: @lang => @dir (was 3.6. The root element)
- 3.8.1. The body element
- Re: Entities (part of detailed review)
- Re: Maturity of XML
- Re: Character encoding errors (detailed review of parsing algorithm)
- Re: Comments on IRC log
- Re: Conformance checkers
- Re: Marking up links to alternative versions of content (was: Re: conflation of issues or convergence of interests?)
- Re: XML versions
- Re: XML versions
- Re: authoring @lang and @dir (was 3.6. The root element)
- Re: ID Characters (was: Re: 3.4. Global attributes)
- Re: authoring @lang and @dir (was 3.6. The root element)
- Re: ID Characters (was: Re: 3.4. Global attributes)
- Re: authoring @lang and @dir (was 3.6. The root element)
- Re: Character encoding errors (detailed review of parsing algorithm)
- Re: Comments on IRC log
- Re: ID Characters (was: Re: 3.4. Global attributes)
- Re: ID Characters (was: Re: 3.4. Global attributes)
- Re: Maturity of XML
- Re: ID Characters (was: Re: 3.4. Global attributes)
- Re: ID Characters (was: Re: 3.4. Global attributes)
- Indexing agreement on accessibility
- Re: Conformance checkers
- @lang => @dir (was 3.6. The root element)
- Re: authoring @lang and @dir (was 3.6. The root element)
- Re: Use Cases for The <canvas> Element
- Re: authoring @lang and @dir (was 3.6. The root element)
- traffic shaping on the list
- Re: conflation of issues or convergence of interests?
- Re: Maturity Re: (of XML)
- Re: Opening thoughts on WAI-ARIA in HTML5
- Re: ID Characters (was: Re: 3.4. Global attributes)
- Steps Towards a Common WG Vocabulary
- Re: Marking up links to alternative versions of content
- Re: Why HTML should be taught as HTML without pretending it is XML
- Re: conflation of issues or convergence of interests?
Wednesday, 1 August 2007
- Re: Formal Recorded Complaint
- Re: Lack of AT implementors participation (was Comments on IRC log)
- Re: 3.15 Tabular Data Review
- Re: conflation of issues or convergence of interests?
- Re: ID Characters (was: Re: 3.4. Global attributes)
- detailed spec reviews wiki page
- Re: 3.4. Global attributes
- Re: Marking up links to alternative versions of content (was: Re: conflation of issues or convergence of interests?)
- Re: Marking up links to alternative versions of content (was: Re: conflation of issues or convergence of interests?)
- Re: Alternate Additional Attribute Set for a Single Quote Element
- Re: ID Characters (was: Re: 3.4. Global attributes)
- Re: Alternate Additional Attribute Set for a Single Quote Element
- Namespaces in HTML (Re: Use Cases for The <canvas> Element)
- Re: Marking up links to alternative versions of content
- Re: ID Characters (was: Re: 3.4. Global attributes)
- Re: Maturity Re: (of XML)
- agenda: HTML WG teleconference 2 Aug
- scribe for tomorrow's teleconference, please?
- Maturity Re: (of XML)
- UAAG Test Suite: User Agent Support for HTML 4.01
- Re: Maturity of XML
- Re: ID Characters (was: Re: 3.4. Global attributes)
- Re: Reality Check: Bi-polar Accessibility Disorder (BAD)
- Alternate Additional Attribute Set for a Single Quote Element
- Re: ID Characters (was: Re: 3.4. Global attributes)
- Re: ID Characters (was: Re: 3.4. Global attributes)
- Re: ID Characters (was: Re: 3.4. Global attributes)
- Re: ID Characters (was: Re: 3.4. Global attributes)
- Re: Maturity of XML
- Re: ID Characters (was: Re: 3.4. Global attributes)
- Re: ID Characters (was: Re: 3.4. Global attributes)
- Re: ID Characters (was: Re: 3.4. Global attributes)
- Re: 3.6. The root element
- Re: Maturity of XML
- Re: ID Characters (was: Re: 3.4. Global attributes)
- Re: 3.6. The root element
- Re: Maturity of XML
- Re: 3.6. The root element
- Re: XML versions
- Re: Character encoding errors (detailed review of parsing algorithm)
- Re: XML versions
- Re: XML versions
- Re: Entities (part of detailed review)
- Re: Entities (part of detailed review)
- Re: XML versions
- Re: Entities (part of detailed review)
- Conformance checkers
- Re: Entities (part of detailed review)
- Re: Maturity of XML
- Re: XML versions
- Maturity of XML
- Re: XHTML2 and namespaces (part of detailed review)
- XML versions
- XHTML2 and namespaces (part of detailed review)
- Namespaces (part of detailed review)
- Accessibility and design principles in action Re: Use Cases for The <canvas> Element
- Re: 3.6. The root element
- Entities (part of detailed review)
- Re: Use Cases for The <canvas> Element
- Re: Use Cases for The <canvas> Element
- Re: Formal Recorded Complaint
- Re: ID Characters (was: Re: 3.4. Global attributes)
- Re: ID Characters (was: Re: 3.4. Global attributes)
- Re: Formal Recorded Complaint
- Re: 3.6. The root element
- Re: HTML 5 proposal - OBJECT elements, environment discovery and alternative content
- Re: ID Characters (was: Re: 3.4. Global attributes)
- Re: Character encoding errors (detailed review of parsing algorithm)
- Re: Reality Check: Bi-polar Accessibility Disorder (BAD)
- Re: ID Characters (was: Re: 3.4. Global attributes)
- Re: authoring @lang and @dir (was 3.6. The root element)
- Re: 3.6. The root element
- Re: Patterns for explicit associations
- Re: Patterns for explicit associations
- Re: Character encoding errors (detailed review of parsing algorithm)
- Re: Reflecting attributes: HTMLElement (detailed review of the DOM)
- Re: <li value=bogus> (detailed review of Semantics)
- Re: Lack Of Definition Of A Valid Ratio (part of detailed review of common microsyntaxes)
- Re: 3.6. The root element
- Re: 3.6. The root element
- Re: 3.6. The root element
- Re: Formal Recorded Complaint
- Re: 3.5.2. Focus
- Re: ID Characters (was: Re: 3.4. Global attributes)
- Re: Formal Recorded Complaint
- Re: Formal Recorded Complaint
- Re: Lack of AT implementors participation (was Comments on IRC log)
- Re: ID Characters (was: Re: 3.4. Global attributes)