Monday, 30 April 2007
- Re: <font> (was Support Existing Content)
- Re: Support Existing Content
- Re: Support Existing Content (was: Proposed Design Principles review)
- Re: Support Existing Content (was: Proposed Design Principles review)
- Re: Support Existing Content (was: Proposed Design Principles review)
- Re: Support Existing Content (was: Proposed Design Principles review)
- Re: [suggestion] Allow DIV inside any element
- Re: Support Existing Content (was: Proposed Design Principles review)
- Re: About the Web Forms 2 proposal
- Re: About the Web Forms 2 proposal
- Re: Support Existing Content (was: Proposed Design Principles review)
- Re: About the Web Forms 2 proposal
- Re: HTML forms, XForms, Web Forms - which and how much?
- Re: Support Existing Content (was: Proposed Design Principles review)
- Re: Introduce <term> element
- Re: How to refer to place of document, which is not marked by author!?
- Re: Support Existing Content (was: Proposed Design Principles review)
- Re: [suggestion] Allow DIV inside any element
- Re: Support Existing Content (was: Proposed Design Principles review)
- Re: [suggestion] Allow DIV inside any element
- Re: [suggestion] Allow DIV inside any element
- Re: Allow DIV inside any element
- Re: [suggestion] Allow DIV inside any element
- Re: [suggestion] Allow DIV inside any element
- Re: How to refer to place of document, which is not marked by author!?
- Re: About the Web Forms 2 proposal
- Re: [suggestion] Allow DIV inside any element
- Re: Pandering to poor authorship
- Re: Introduce <term> element
- Re: Versioning and the end user
- Re: missing principle
- Re: Hand-coding HTML (was: New html-element: table3)
- Re: Semantic vs. Presentational (was Proposing <indent> vs. <blockquote>)
- Re: Proposing <indent> vs. <blockquote>
- Re: Support Existing Content (was: Proposed Design Principles review)
- Re: Support Existing Content (was: Proposed Design Principles review)
- Re: Support Existing Content (was: Proposed Design Principles review)
- Re: Support Existing Content (was: Proposed Design Principles review)
- Re: Support Existing Content (was: Proposed Design Principles review)
- Re: Support Existing Content (was: Proposed Design Principles review)
- Re: Support Existing Content (was: Proposed Design Principles review)
- Re: Meta-question : why so few "Re: " subjects ?
- Re: Support Existing Content (was: Proposed Design Principles review)
- Re: Meta-question : why so few "Re: " subjects ?
- Meta-question : why so few "Re: " subjects ?
- Re: Support Existing Content (was: Proposed Design Principles review)
- Re: Support Existing Content (was: Proposed Design Principles review)
- Re: HTML forms, XForms, Web Forms - which and how much?
- Re: Support Existing Content (was: Proposed Design Principles review)
- Re: HTML forms, XForms, Web Forms - which and how much?
- Re: HTML forms, XForms, Web Forms - which and how much?
- Re: Desing principles - Support World Languages example added
- Re: HTML forms, XForms, Web Forms - which and how much?
- Re: HTML forms, XForms, Web Forms - which and how much?
- Re: HTML forms, XForms, Web Forms - which and how much?
- Re: Desing principles - Support World Languages example added
- Re: [suggestion] Allow DIV inside any element
- Re: [suggestion] Allow DIV inside any element
Sunday, 29 April 2007
Monday, 30 April 2007
- Re: HTML forms, XForms, Web Forms - which and how much?
- Re: Desing principles - Support World Languages example added
- Re: HTML version issue summary?
- Re: HTML forms, XForms, Web Forms - which and how much?
- Re: HTML version issue summary?
- Re: HTML version issue summary?
- Re: HTML version issue summary?
- Re: survey of top web sites
- Re: HTML forms, XForms, Web Forms - which and how much?
- Re: survey of top web sites
Sunday, 29 April 2007
- RE: Support Existing Content (was: Proposed Design Principles review)
- Re: Support Existing Content (was: Proposed Design Principles review)
- Re: About the Web Forms 2 proposal
- Re: Support Existing Content (was: Proposed Design Principles review)
- Re: [suggestion] Allow DIV inside any element
- Re: HTML forms, XForms, Web Forms - which and how much?
- Re: [suggestion] Allow DIV inside any element
- Re: HTML version issue summary?
- Re: [suggestion] Allow DIV inside any element
- Re: Allow DIV inside any element
- Re: task list
- Re: [suggestion] Allow DIV inside any element
- Re: task list
- Re: Allow DIV inside any element
- Re: [suggestion] Allow DIV inside any element
- [suggestion] Allow DIV inside any element
- Re: About the Web Forms 2 proposal
- Re: Desing principles - Support World Languages example added
- Re: Introduce <term> element
- Re: Support Existing Content (was: Proposed Design Principles review)
- Re: Support Existing Content (was: Proposed Design Principles review)
- Re: About the Web Forms 2 proposal
- Re: Desing principles - Support World Languages example added
- Re: Desing principles - Support World Languages example added
- Re: Desing principles - Support World Languages example added
- Re: About the Web Forms 2 proposal
- Re: About the Web Forms 2 proposal
- Re: About the Web Forms 2 proposal
- Re: About the Web Forms 2 proposal
- Re: HTML version issue summary?
- Re: HTML version issue summary?
- Re: About the Web Forms 2 proposal
- Re: About the Web Forms 2 proposal
- Re: About the Web Forms 2 proposal
Saturday, 28 April 2007
Sunday, 29 April 2007
- Re: About the Web Forms 2 proposal
- Another look at the Proposed Design Principles
- Re: About the Web Forms 2 proposal
- Re: About the Web Forms 2 proposal
- Re: Hand-coding HTML
- Re: About the Web Forms 2 proposal
- Re: About the Web Forms 2 proposal
Saturday, 28 April 2007
- Re: Support Existing Content (was: Proposed Design Principles review)
- Re: Support Existing Content (was: Proposed Design Principles review)
- Re: missing principle
- Re: Hand-coding HTML (was: New html-element: table3)
- Re: About the Web Forms 2 proposal
- Re: Support Existing Content (was: Proposed Design Principles review)
- Re: Hand-coding HTML (was: New html-element: table3)
- Re: Pandering to poor authorship
- Re: HTML version issue summary?
- Re: Versioning and the end user
- Desing principles - Support World Languages example added
- Re: Support Existing Content (was: Proposed Design Principles review)
- Re: Proposed Design Principles review
- Re: Proposed Design Principles review
- Re: About the Web Forms 2 proposal
- Re: missing principle
- Re: About the Web Forms 2 proposal
- Re: missing principle
- Re: About the Web Forms 2 proposal
- Re: About the Web Forms 2 proposal
- Re: missing principle
- task list
- Re: How to refer to place of document, which is not marked by author!?
- Re: About the Web Forms 2 proposal
- Re: missing principle
- Re: How to refer to place of document, which is not marked by author!?
- Re: Introduce <term> element
- Re: missing principle
- Re: Versioning and the end user
- Re: missing principle
- Re: missing principle
- Hand-coding HTML (was: New html-element: table3)
- Re: Pandering to poor authorship (was Proposing <indent> vs. <blockquote>)
- Re: Support Existing Content (was: Proposed Design Principles review)
- Re: Proposed Design Principles updated
- Re: Support Existing Content (was: Proposed Design Principles review)
- Re: How to refer to place of document, which is not marked by author!?
- Re: Non-goal for HTML: Picture-perfect rendering
- Re: How to refer to place of document, which is not marked by author!?
- Re: About the Web Forms 2 proposal
- Semantic vs. Presentational (was Proposing <indent> vs. <blockquote>)
- Re: Proposing <indent> vs. <blockquote>
- Re: Proposing <indent> vs. <blockquote>
- Re: missing principle (small)
- Re: Proposed Design Principles review
Friday, 27 April 2007
- Re: About the Web Forms 2 proposal
- RE: Nomination for Co-Editor: Dave Hyatt
- Re: Proposed requirement: specification should provide enough detail to handle Web content
- Re: Support Existing Content (was: Proposed Design Principles review)
- Re: Support Existing Content (was: Proposed Design Principles review)
- Re: Nomination for Co-Editor: Dave Hyatt
- Re: Support Existing Content
- Re: [public-html] <none>
- Re: HTML forms, XForms, Web Forms - which and how much?
- Re: HTML forms, XForms, Web Forms - which and how much?
- Re: Support Existing Content
- Re: Proposed requirement: specification should provide enough detail to handle Web content
- HTML5 as our specification text for review? (formal question WBS survey)
- Re: missing principle
- Re: missing principle
- Re: Support Existing Content (was: Proposed Design Principles review)
- Re: missing principle
- Re: Proposed Design Principles review
- Re: Proposed requirement: specification should provide enough detail to handle Web content
- Re: [public-html] <none>
- Re: [public-html] <none>
- Re: [public-html] <none>
- Re: [public-html] <none>
- Re: HTML forms, XForms, Web Forms - which and how much?
- Re: Support Existing Content
- Re: [public-html] <none>
- Re: Support Existing Content
- Re: [public-html] <none>
- Re: [public-html] <none>
- Re: [public-html] <none>
- Re: Proposed Design Principles review
- Re: [public-html] <none>
- [public-html] <none>
- Re: Support Existing Content
- Re: Support Existing Content
- Re: Support Existing Content
- Re: Support Existing Content
- Re: survey of top web sites
- Re: Support Existing Content
- Re: missing principle
- Re: missing principle
- Re: missing principle
- Re: missing principle
- Re: missing principle
- Re: About the Web Forms 2 proposal
- missing principle
- Support Existing Content (was: Proposed Design Principles review)
- Design Principles Update
- Proposed requirement: specification should provide enough detail to handle Web content
- Re: Proposed Design Principles review
- Re: About the Web Forms 2 proposal -- from a proposed design principles point of view
- Re: HTML forms, XForms, Web Forms - which and how much?
- Re: Proposed Design Principles review
- Re: Proposed Design Principles review
- Design principles: added three examples
- Re: Proposed Design Principles review
- Re: About the Web Forms 2 proposal -- from a proposed design principles point of view
- Re: Proposed Design Principles review
- Re: Proposed Design Principles review
- RE: About the Web Forms 2 proposal -- from a proposed design principles point of view
- Re: Proposed Design Principles review
- Re: Proposed Design Principles review
- Re: Proposed Design Principles review
- Re: Proposed Design Principles review
- RE: About the Web Forms 2 proposal -- from a proposed design principles point of view
- Re: Proposed Design Principles review
- Re: Proposed Design Principles review
- Re: Proposed Design Principles review
- Re: HTML version issue summary?
- Re: Proposed Design Principles review
- Re: About the Web Forms 2 proposal -- from a proposed design principles point of view
- Re: survey of top web sites
- RE: survey of top web sites
- Re: About the Web Forms 2 proposal
- Re: HTML forms, XForms, Web Forms - which and how much?
- Re: HTML forms, XForms, Web Forms - which and how much?
- Re: HTML forms, XForms, Web Forms - which and how much?
- Re: survey of top web sites
- Re: HTML forms, XForms, Web Forms - which and how much?
- Re: About the Web Forms 2 proposal
Thursday, 26 April 2007
- Re: HTML forms, XForms, Web Forms - which and how much?
- Re: HTML forms, XForms, Web Forms - which and how much?
- Re: survey of top web sites
- RE: HTML WG teleconference 2007-04-26 minutes for review
- RE: About the Web Forms 2 proposal -- from a proposed design principles point of view
- Re: Parsing of HTML fragments
- Re: HTML WG teleconference 2007-04-26 minutes for review
- Re: HTML WG teleconference 2007-04-26 minutes for review
- HTML WG teleconference 2007-04-26 minutes for review
- Re: HTML forms, XForms, Web Forms - which and how much?
- Re: HTML forms, XForms, Web Forms - which and how much?
- Re: non-rectangular images & <img> tag
- Re: RE: survey of top web sites
- Re: HTML WG teleconference 2007-04-26 minutes for review
- Re: If we have versioning, it should be in an attribute, not the doctype
- RE: survey of top web sites
- Re: HTML forms, XForms, Web Forms - which and how much?
- Re: Feature Strings
- Re: new form control
- HTML WG teleconference 2007-04-26 minutes for review
- Re: Proposed Design Principles review
- Re: About the Web Forms 2 proposal
- RE: survey of top web sites
- Re: Proposed Design Principles review
- RE: Proposed Design Principles review
- Re: Proposed Design Principles review
- Re: INPUT-PIC form control
- Re: If we have versioning, it should be in an attribute, not the doctype
- Re: survey of top web sites
- RE: HTML forms, XForms, Web Forms - which and how much?
- About the Web Forms 2 proposal
- Proposed Design Principles review
- Re: HTML forms, XForms, Web Forms - which and how much?
- Re: non-rectangular images & <img> tag
- HTML forms, XForms, Web Forms - which and how much?
- Re: survey of top web sites
- Re: HTML version issue summary?
- scribe for today's teleconference?
- Re: Let use this convention for conversation
- Re: HTML version issue summary?
- Dublin workshop on web authoring
- Re[2]: [OBORONA-SPAM] Re: Re[2]: Fwd: Re[2]: New html-element: table3
- Re: [OBORONA-SPAM] Re: Re[2]: Fwd: Re[2]: New html-element: table3
- Re: Separation of versioning concerns
- Re: Re[2]: Fwd: Re[2]: New html-element: table3
- Re[2]: Fwd: Re[2]: New html-element: table3
- Re: HTML version issue summary?
- Re: Fwd: Re[2]: New html-element: table3
- Re[4]: New html-element: table3
- Re[2]: Fwd: Re[2]: New html-element: table3
- INPUT-PIC form control
- Re: Let use this convention for conversation
- Let use this convention for conversation
- Re: Fwd: Re[2]: New html-element: table3
- Fwd: Re[2]: New html-element: table3
- Fwd: Re: [OBORONA-SPAM] Re: Re[2]: New html-element: table3
- Fwd: Re[4]: New html-element: table3
- Fwd: Re[2]: New html-element: table3
- Re: How to refer to place of document, which is not marked by author!?
- How to refer to place of document, which is not marked by author!?
Wednesday, 25 April 2007
Thursday, 26 April 2007
Wednesday, 25 April 2007
- Re: Separation of versioning concerns
- Re: Parsing of HTML fragments
- Re: new form control
- Re: agenda: HTML WG teleconference 2007-04-26T17:00:00Z (invited participants)
- Re: agenda: HTML WG teleconference 2007-04-26T17:00:00Z
- Re: non-rectangular images & <img> tag
- Re: survey of top web sites
- Re: survey of top web sites
- Re: Separation of versioning concerns
- Re: Parsing of HTML fragments
- Re: Parsing of HTML fragments
- Re: HTML version issue summary?
- Re: agenda: HTML WG teleconference 2007-04-26T17:00:00Z
- Re: survey of top web sites
- Re: HTML version issue summary?
- Re: HTML version issue summary?
- agenda: HTML WG teleconference 2007-04-26T17:00:00Z
- Re: survey of top web sites
- Re: non-rectangular images & <img> tag
- Re: Parsing of HTML fragments
- Re: non-rectangular images & <img> tag
- Re: survey of top web sites
- Re: non-rectangular images & <img> tag
- Re: Versioning of HTML fragments
- Re: Versioning of HTML fragments
- Re: Separation of versioning concerns
- Re: Separation of versioning concerns
- Re: Separation of versioning concerns
- Re: Separation of versioning concerns
- Re: HTML version issue summary?
- Re: Separation of versioning concerns
- Re: Separation of versioning concerns
- Separation of versioning concerns
- Re: HTML version issue summary?
- Re: HTML version issue summary?
- Re: HTML version issue summary?
- Re: HTML version issue summary?
- Re: non-rectangular images & <img> tag
- Re: HTML version issue summary?
- Re: non-rectangular images & <img> tag
- Re: HTML version issue summary?
- Re: HTML version issue summary?
- Re: survey of top web sites
- Re: HTML version issue summary?
- Re: tasks to supplement HTML specification development
- Re: HTML version issue summary?
- Re: HTML version issue summary?
- Re: survey of top web sites
- Re: Re: survey of top web sites
- Re: HTML version issue summary?
- Re: HTML version issue summary?
- Re: HTML version issue summary?
- Re: survey of top web sites
- Re: HTML version issue summary?
- Re: survey of top web sites
- Re: HTML version issue summary?
- Re: HTML version issue summary?
- Re: HTML version issue summary?
- Re: HTML version issue summary?
- Re: HTML version issue summary?
- Re: HTML version issue summary?
- Re: HTML version issue summary?
- Re: HTML version issue summary?
- Re: HTML version issue summary?
- Re: HTML version issue summary?
- Re: Parsing of HTML fragments
- Re: HTML version issue summary?
- Re: Parsing of HTML fragments
- Re: Parsing of HTML fragments
Tuesday, 24 April 2007
- Re: non-rectangular images & <img> tag
- Re: Parsing of HTML fragments
- Re: Parsing of HTML fragments
- HTML version issue summary?
- Re: FAQ on joining the HTML WG as an Invited Expert
- survey of top web sites
- Re: Other roles we should fill (survey on tasks and roles)
- Re: Parsing of HTML fragments
- Re: Parsing of HTML fragments
- Re: Parsing of HTML fragments
- Re: Parsing of HTML fragments
- Re: Parsing of HTML fragments
- Re: Parsing of HTML fragments
- Parsing of HTML fragments
- Re: Versioning of HTML fragments
- Re: Re[2]: New html-element: table3
- Re: FAQ on joining the HTML WG as an Invited Expert
- Re: Re[2]: New html-element: table3
- Re: New html-element: table3
- Re: New html-element: table3
- Re: new form control
- Re: brainstorm: attributes as virtual tags
- Re: brainstorm: attributes as virtual tags
- Re[4]: new form control
- FAQ on joining the HTML WG as an Invited Expert
- brainstorm: attributes as virtual tags
- Re: non-rectangular images & <img> tag
- Re: new form control
- Re[2]: New html-element: table3
- Re: New html-element: table3
- Re: BoF at XTech
- Re: BoF at XTech
- New html-element: table3
- New html-element: table3
- Re: BoF at XTech
- Re: BoF at XTech
- Re: BoF at XTech
Monday, 23 April 2007
Tuesday, 24 April 2007
- Re: BoF at XTech (was: Re: no HTML WG meeting around XTech)
- Re: HTML WG teleconference Thu 26 Apr 1700UTC (meeting call, survey)
- Re: HTML WG teleconference Thu 26 Apr 1700UTC (meeting call, survey)
Monday, 23 April 2007
- Re: Re[2]: new form control
- Re: Now there is table-element with predetermined quantity of column.But sometimes we need to visualize three tables(for example, database tables) as one table:first table contains names of rows,second table contains names of columns (this table determine quantity of columns),third table contains data.New html-element: table-dim
- non-rectangular images & <img> tag
- BoF at XTech (was: Re: no HTML WG meeting around XTech)
- Re: If we have versioning, it should be in an attribute, not the doctype
- Re: HTML5 proposal response
- Re: Nomination for Co-Editor: Dave Hyatt
- Re: Nomination for Co-Editor: Dave Hyatt
- Re: Nomination for Co-Editor: Dave Hyatt
- Re: Now there is table-element with predetermined quantity of column. But sometimes we need to visualize three tables (for example, database tables) as one table: first table contains names of rows, second table contains names of columns (this table
- Re: Now there is table-element with predetermined quantity of column. But sometimes we need to visualize three tables (for example, database tables) as one table: first table contains names of rows, second table contains names of columns (this table
- RE: HTML5 proposal response
- Re: Nomination for Co-Editor: Dave Hyatt
- Re: A Compromise to the Versioning Debate
- Re: Issue Tracking
- Re: Nomination for Co-Editor: Dave Hyatt
- Re: Nomination for Co-Editor: Dave Hyatt
- Re: HTML5 proposal response
- Re: Nomination for Co-Editor: Dave Hyatt
- Re: HTML5 proposal response
- Re: Proposal to Adopt HTML5 (progress on recruiting editors)
- Re: Nomination for Co-Editor: Dave Hyatt
- Re: Formal definition of HTML5 (was Re: Version information)
- Re: Formal definition of HTML5 (was Re: Version information)
- Re: Formal definition of HTML5 (was Re: Version information)
- Re: Nomination for Co-Editor: Dave Hyatt
- Re: Formal definition of HTML5 (was Re: Version information)
- Re: Formal definition of HTML5 (was Re: Version information)
- Re: Versioning and html[5]
- Re: Versioning and html[5]
- Re: Formal definition of HTML5 (was Re: Version information)
- Re: A Compromise to the Versioning Debate
- Re: Versioning and html[5]
- Re: Versioning and html[5]
- Re: Versioning and html[5]
- Re: Feature Strings
- Re: Nomination for Co-Editor: Dave Hyatt
- Re: Nomination for Co-Editor: Dave Hyatt
- Now there is table-element with predetermined quantity of column.
- Re: Nomination for Co-Editor: Dave Hyatt
- Re: Nomination for Co-Editor: Dave Hyatt
- Re: Nomination for Co-Editor: Dave Hyatt
- Re: Nomination for Co-Editor: Dave Hyatt
- Re: Microsoft versioning proposal
- Re: Nomination for Co-Editor: Dave Hyatt
- Re: Nomination for Co-Editor: Dave Hyatt
- Re: Feature Strings
- Re: Nomination for Co-Editor: Dave Hyatt
- Re: Nomination for Co-Editor: Dave Hyatt
- Re: Nomination for Co-Editor: Dave Hyatt
Sunday, 22 April 2007
- Re: Nomination for Co-Editor: Dave Hyatt
- Other roles we should fill
- Re: Nomination for Co-Editor: Dave Hyatt
- Re: Proposing <indent> vs. <blockquote>
- Re: Nomination for Co-Editor: Dave Hyatt
- Re: Nomination for Co-Editor: Dave Hyatt
- Re: Nomination for Co-Editor: Dave Hyatt
- Re: Nomination for Co-Editor: Dave Hyatt
- Re: The argument for |bugmode|
- Re: A Compromise to the Versioning Debate
- Re: Nomination for Co-Editor: Dave Hyatt
- Re: Nomination for Co-Editor: Dave Hyatt
Saturday, 21 April 2007
Sunday, 22 April 2007
- Re: Microsoft versioning proposal
- Re: Nomination for Co-Editor: Dave Hyatt
- Re: The argument for |bugmode|
Saturday, 21 April 2007
- Re: A Compromise to the Versioning Debate
- Re: The argument for |bugmode|
- Re: The argument for |bugmode|
- Re: The argument for |bugmode|
- Re: Nomination for Co-Editor: Dave Hyatt
- Re: tasks to supplement HTML specification development
- Re: A Compromise to the Versioning Debate
- Re: Nomination for Co-Editor: Dave Hyatt
- Re: A Compromise to the Versioning Debate
- Re: The argument for |bugmode|
- Re: A Compromise to the Versioning Debate
- Re: The argument for |bugmode|
- Re: Introduce <term> element
- Re: The argument for |bugmode|
- RE: The argument for |bugmode|
- Re: Nomination for Co-Editor: Dave Hyatt
- Re: Nomination for Co-Editor: Dave Hyatt
- Re: Nomination for Co-Editor: Dave Hyatt
- Nomination for Co-Editor: Dave Hyatt
Friday, 20 April 2007
- RE: The argument for |bugmode|
- RE: The argument for |bugmode|
- Re: new form control
- Re: The argument for |bugmode|
- Re: Proposing <indent> vs. <blockquote>
- Re: The argument for |bugmode|
- Re: tasks to supplement HTML specification development
- Re: Editor and authors
- Re: The argument for |bugmode|
- Re: Proposing <indent> vs. <blockquote>
- Re: Editor and authors
- Re: The argument for |bugmode|
- Re: The argument for |bugmode| (was Re: If we have versioning, it should be in an attribute, not the doctype)
- Re: The argument for |bugmode|
- Update on affiliation
- Re: new form control
- Re: new form control
- Re: The argument for |bugmode| (was Re: If we have versioning, it should be in an attribute, not the doctype)
- Re: The argument for |bugmode|
- new form control
- Re: Editor and authors
- Re: Editor and authors
- Re: The argument for |bugmode|
- Re: Editor and authors
- Re: Feature Strings
- Editor and authors Re: HTML5 proposal response
- Re: The argument for |bugmode|
- Re: The argument for |bugmode| (was Re: If we have versioning, it should be in an attribute, not the doctype)
- Re: The argument for |bugmode| (was Re: If we have versioning, it should be in an attribute, not the doctype)
- Re: The argument for |bugmode|
- Re: The argument for |bugmode|
- Re: The argument for |bugmode|
- Re: The argument for |bugmode|
- Re: HTML5 proposal response
- Re: The argument for |bugmode|
- Re: The argument for |bugmode|
- Re: The argument for |bugmode|
- RE: HTML5 proposal response
Thursday, 19 April 2007
- Re: HTML5 proposal response
- HTML5 proposal response
- RE: The argument for |bugmode|
- RE: Proposal to Adopt HTML5 (progress on recruiting editors)
- Re: Feature Strings
- RE: The argument for |bugmode|
- Re: Feature Strings
- RE: Proposal to Adopt HTML5 (progress on recruiting editors)
- RE: The argument for |bugmode|
- RE: The argument for |bugmode| (was Re: If we have versioning, it should be in an attribute, not the doctype)
- Re: The argument for |bugmode| (was Re: If we have versioning, it should be in an attribute, not the doctype)
- RE: The argument for |bugmode|
- RE: Non-goal for HTML: Picture-perfect rendering
- Re: The argument for |bugmode| (was Re: If we have versioning, it should be in an attribute, not the doctype)
- Re: The argument for |bugmode| (was Re: If we have versioning, it should be in an attribute, not the doctype)
- Re: A Compromise to the Versioning Debate
- Re: Proposal to Adopt HTML5 (progress on recruiting editors)
- Re: The argument for |bugmode|
- Re: Feature Strings
- Re: The argument for |bugmode| (was Re: If we have versioning, it should be in an attribute, not the doctype)
- Re: The argument for |bugmode| (was Re: If we have versioning, it should be in an attribute, not the doctype)
- Re: Re: The argument for |bugmode| (was Re: If we have versioning, it should be in an attribute, not the doctype)
- Re: The argument for |bugmode| (was Re: If we have versioning, it should be in an attribute, not the doctype)
- Re: Feature Strings
- Feature Strings
- Re: Proposal to Adopt HTML5 (progress on recruiting editors)
- Re: The argument for |bugmode| (was Re: If we have versioning, it should be in an attribute, not the doctype)
- Re: Issue Tracking (was: Proposal to Adopt HTML5)
- Re: The argument for |bugmode| (was Re: If we have versioning, it should be in an attribute, not the doctype)
- Re: The argument for |bugmode| (was Re: If we have versioning, it should be in an attribute, not the doctype)
- Re: If we have versioning, it should be in an attribute, not the doctype
- Re: Request for Decision: Design Principles
- Re: Proposal to Adopt HTML5 (progress on recruiting editors)
- specification name [was: Proposal to Adopt HTML5]
- Re: The argument for |bugmode|
- Re: quality of authoring tools' output (was Versioning and html[5])
- Re: The argument for |bugmode| (was Re: If we have versioning, it should be in an attribute, not the doctype)
- Re: Non-goal for HTML: Picture-perfect rendering
- Re: The argument for |bugmode|
- Re: The argument for |bugmode| (was Re: If we have versioning, it should be in an attribute, not the doctype)
- Re: The argument for |bugmode| (was Re: If we have versioning, it should be in an attribute, not the doctype)
- Re: The argument for |bugmode| (was Re: If we have versioning, it should be in an attribute, not the doctype)
- Re: Eolas vs. <object>
- Re: The argument for |bugmode| (was Re: If we have versioning, it should be in an attribute, not the doctype)
- Re: The argument for |bugmode| (was Re: If we have versioning, it should be in an attribute, not the doctype)
- Re: Proposal to Adopt HTML5 (progress on recruiting editors)
- Re: The argument for |bugmode| (was Re: If we have versioning, it should be in an attribute, not the doctype)
- Re: Proposal to Adopt HTML5 (progress on recruiting editors)
- Re: Proposal to Adopt HTML5 (progress on recruiting editors)
- Re: The argument for |bugmode| (was Re: If we have versioning, it should be in an attribute, not the doctype)
- RE: quality of authoring tools' output
- Re: Formal definition of HTML5 (was Re: Version information)
- Re: Non-goal for HTML: Picture-perfect rendering
- Re: Eolas vs. <object>
- Re: Microsoft versioning proposal
- Re: The argument for |bugmode|
- Issue Tracking (was: Proposal to Adopt HTML5)
- Re: Non-goal for HTML: Picture-perfect rendering
- Re: The argument for |bugmode| (was Re: If we have versioning, it should be in an attribute, not the doctype)
- Re: Proposal to Adopt HTML5
- Re: Proposal to Adopt HTML5
- Re: quality of authoring tools' output (was Versioning and html[5])
Wednesday, 18 April 2007
- Re: Proposal to Adopt HTML5
- Re: Proposal to Adopt HTML5 (progress on recruiting editors)
- Re: Proposal to Adopt HTML5 (progress on recruiting editors)
- Re: HTML WG teleconference Thu 26 Apr 1700UTC (meeting call, survey)
- Re: Proposal to Adopt HTML5
- Re: HTML WG teleconference Thu 26 Apr 1700UTC (meeting call, survey)
- Re: Request for Decision: Design Principles
- RE: quality of authoring tools' output (was Versioning and html[5])
- supplemental HTML WG orientation teleconference (same survey)
- Re: Proposal to Adopt HTML5
- Re: Proposal to Adopt HTML5
- RE: quality of authoring tools' output (was Versioning and html[5])
- HTML WG teleconference Thu 26 Apr 1700UTC (meeting call, survey)
- Re: Request for Decision: Design Principles
- Re: several messages on versioning
- Re: Request for Decision: Design Principles
- Re: Request for Decision: HTML5 Proposal
- Re: Request for Decision: HTML5 Proposal
- Re: Request for Decision: Design Principles
- Re: The argument for |bugmode| (was Re: If we have versioning, it should be in an attribute, not the doctype)
- Re: Request for Decision: Design Principles
- Re: Precision of <canvas> rendering (was: Re: Formal definition of HTML5)
- Re: The argument for |bugmode| (was Re: If we have versioning, it should be in an attribute, not the doctype)
- Re: Request for Decision: HTML5 Proposal
- Re: Non-goal for HTML: Picture-perfect rendering
- Re: Request for Decision: Design Principles
- about this mailing list
- Re: Request for Decision: HTML5 Proposal
- Re: A Concrete Example for the HTML Versioning Debate
- Re: The argument for |bugmode| (was Re: If we have versioning, it should be in an attribute, not the doctype)
- Re: Request for Decision: HTML5 Proposal
- Re: Request for Decision: HTML5 Proposal
- Re: Request for Decision: HTML5 Proposal
- Re: The argument for |bugmode| (was Re: If we have versioning, it should be in an attribute, not the doctype)
- Re: Request for Decision: HTML5 Proposal
- Re: The argument for |bugmode| (was Re: If we have versioning, it should be in an attribute, not the doctype)
- RE: The argument for |bugmode| (was Re: If we have versioning, it should be in an attribute, not the doctype)
- RE: Microsoft versioning proposal
- RE: The argument for |bugmode| (was Re: If we have versioning, it should be in an attribute, not the doctype)
- RE: Precision of <canvas> rendering (was: Re: Formal definition of HTML5)
- RE: The argument for |bugmode| (was Re: If we have versioning, it should be in an attribute, not the doctype)
Tuesday, 17 April 2007
Wednesday, 18 April 2007
- Re: A Concrete Example for the HTML Versioning Debate
- Re: Non-goal for HTML: Picture-perfect rendering
- Re: The argument for |bugmode| (was Re: If we have versioning, it should be in an attribute, not the doctype)
- Re: Precision of <canvas> rendering (was: Re: Formal definition of HTML5)
- Re: The argument for |bugmode| (was Re: If we have versioning, it should be in an attribute, not the doctype)
- Re: A Concrete Example for the HTML Versioning Debate
- Re: Non-goal for HTML: Picture-perfect rendering
- Re: The argument for |bugmode| (was Re: If we have versioning, it should be in an attribute, not the doctype)
- Re: Introduce <term> element
- Re: Non-goal for HTML: Picture-perfect rendering
- Re: tasks to supplement HTML specification development
- Re: The argument for |bugmode| (was Re: If we have versioning, it should be in an attribute, not the doctype)
- Re: A Concrete Example for the HTML Versioning Debate
- Re: A Concrete Example for the HTML Versioning Debate
- Re: A Concrete Example for the HTML Versioning Debate
- Re: The argument for |bugmode| (was Re: If we have versioning, it should be in an attribute, not the doctype)
- Re: A Concrete Example for the HTML Versioning Debate
- Re: Precision of <canvas> rendering (was: Re: Formal definition of HTML5)
- Re: Perception of HTML5 (was Re: Formal definition of HTML5)
- Re: A Compromise to the Versioning Debate
- Re: The argument for |bugmode| (was Re: If we have versioning, it should be in an attribute, not the doctype)
- Re: A Concrete Example for the HTML Versioning Debate
- Re: A Concrete Example for the HTML Versioning Debate
- Re: A Concrete Example for the HTML Versioning Debate
- Re: A Compromise to the Versioning Debate
- Re: A Concrete Example for the HTML Versioning Debate
- static and dinamic schemes
- Re: A Concrete Example for the HTML Versioning Debate
- RE: Request for Decision: Design Principles
- Re: A Concrete Example for the HTML Versioning Debate
- A Concrete Example for the HTML Versioning Debate
- Re: Versioning and html[5]
- Re: A Compromise to the Versioning Debate
- Request for Decision: HTML5 Proposal
- Request for Decision: Design Principles
- Re: legacy of incompetence? [was: a compromise to the versioning debate]
- Re: Non-goal for HTML: Picture-perfect rendering
- Re: Formal definition of HTML5 (was Re: Version information)
- Re: Non-goal for HTML: Picture-perfect rendering
- RE: Eolas vs. <object>
- Re: Non-goal for HTML: Picture-perfect rendering
- Re: Non-goal for HTML: Picture-perfect rendering
- The argument for |bugmode| (was Re: If we have versioning, it should be in an attribute, not the doctype)
- Re: If we have versioning, it should be in an attribute, not the doctype
- Re: If we have versioning, it should be in an attribute, not the doctype
- Re: Microsoft versioning proposal
- Re: If we have versioning, it should be in an attribute, not the doctype
- Re: If we have versioning, it should be in an attribute, not the doctype
- RE: Precision of <canvas> rendering (was: Re: Formal definition of HTML5)
Tuesday, 17 April 2007
- Re: [XBL Primer] new scenarios
- Re: legacy of incompetence? [was: a compromise to the versioning debate]
- Re: Eolas vs. <object>
- Re: legacy of incompetence? [was: a compromise to the versioning debate]
- Re: Microsoft versioning proposal
- Re: legacy of incompetence? [was: a compromise to the versioning debate]
- Re: If we have versioning, it should be in an attribute, not the doctype
- Re: Versioning and html[5]
- Re: If we have versioning, it should be in an attribute, not the doctype
- Re: Proposing <indent> vs. <blockquote>
- Re: Perception of HTML5 (was Re: Formal definition of HTML5)
- Re: If we have versioning, it should be in an attribute, not the doctype
- Re: Proposing <indent> vs. <blockquote>
- RE: If we have versioning, it should be in an attribute, not the doctype
- Re: Versioning and html[5]
- Re: If we have versioning, it should be in an attribute, not the doctype
- Re: If we have versioning, it should be in an attribute, not the doctype
- RE: Microsoft versioning proposal
- Re: Versioning and the end user
- Re: Versioning and the end user
- RE: If we have versioning, it should be in an attribute, not the doctype
- Re: If we have versioning, it should be in an attribute, not the doctype
- Re: Perception of HTML5 (was Re: Formal definition of HTML5)
- RE: legacy of incompetence? [was: a compromise to the versioning debate]
- RE: Versioning and the end user
- Re: If we have versioning, it should be in an attribute, not the doctype
- Re: If we have versioning, it should be in an attribute, not the doctype
- Re: Versioning and the end user
- Re: Formal definition of HTML5 (was Re: Version information)
- Re: Proposing <indent> vs. <blockquote>
- Re: Formal definition of HTML5 (was Re: Version information)
- Re: Precision of <canvas> rendering (was: Re: Formal definition of HTML5)
- Precision of <canvas> rendering (was: Re: Formal definition of HTML5)
- RE: Versioning and html[5]
- RE: Versioning and html[5]
- If we have versioning, it should be in an attribute, not the doctype
- Eolas vs. <object>
- Re: Versioning and html[5]
- Re: Formal definition of HTML5 (was Re: Version information)
- Re: Versioning and html[5]
- Re: legacy of incompetence? [was: a compromise to the versioning debate]
- Re: A Compromise to the Versioning Debate
- Re: legacy of incompetence? [was: a compromise to the versioning debate]
- Re: Versioning and the end user
- Re: Versioning and the end user
- Re: Perception of HTML5 (was Re: Formal definition of HTML5)
- Re: legacy of incompetence? [was: a compromise to the versioning debate]
- Re: Formal definition of HTML5 (was Re: Version information)
- Re: Formal definition of HTML5 (was Re: Version information)
- Re: legacy of incompetence? [was: a compromise to the versioning debate]
- Re: Formal definition of HTML5 (was Re: Version information)
- Re: Formal definition of HTML5 (was Re: Version information)
- Re: RDFa Use Cases and Primer Working Drafts - Comments Welcome!
- Re: Formal definition of HTML5 (was Re: Version information)
- Re: Formal definition of HTML5 (was Re: Version information)
- Re: legacy of incompetence? [was: a compromise to the versioning debate]
- Re: Formal definition of HTML5 (was Re: Version information)
- Re: Formal definition of HTML5 (was Re: Version information)
- Re: Formal definition of HTML5 (was Re: Version information)
- Re: legacy of incompetence? [was: a compromise to the versioning debate]
- Re: RDFa Use Cases and Primer Working Drafts - Comments Welcome!
- RDFa Use Cases and Primer Working Drafts - Comments Welcome!
- Re: legacy of incompetence? [was: a compromise to the versioning debate]
- Re: Proposing <indent> vs. <blockquote>
Monday, 16 April 2007
- Re: Proposing <indent> vs. <blockquote>
- Re: legacy of incompetence? [was: a compromise to the versioning debate]
Tuesday, 17 April 2007
- Perception of HTML5 (was Re: Formal definition of HTML5)
- Re: Formal definition of HTML5 (was Re: Version information)
- Re: Formal definition of HTML5 (was Re: Version information)
- Re: Formal definition of HTML5 (was Re: Version information)
- Re: Formal definition of HTML5 (was Re: Version information)
- Re: Formal definition of HTML5 (was Re: Version information)
- Re: Formal definition of HTML5 (was Re: Version information)
- Re: Formal definition of HTML5 (was Re: Version information)
- Re: A Compromise to the Versioning Debate
- Re: Proposing <indent> vs. <blockquote>
- Re: A Compromise to the Versioning Debate
- Re: A Compromise to the Versioning Debate
- Re: Versioning and the end user
- Versioning and the end user
Monday, 16 April 2007
Tuesday, 17 April 2007
- Re: Formal definition of HTML5 (was Re: Version information)
- Re: Formal definition of HTML5 (was Re: Version information)
- Re: Formal definition of HTML5 (was Re: Version information)
- Re: Non-goal for HTML: Picture-perfect rendering
Monday, 16 April 2007
- Re: Non-goal for HTML: Picture-perfect rendering
- Re: Non-goal for HTML: Picture-perfect rendering
- Re: A Compromise to the Versioning Debate
- Re: Non-goal for HTML: Picture-perfect rendering
- Re: Non-goal for HTML: Picture-perfect rendering
- Re: A Compromise to the Versioning Debate
- Re: Non-goal for HTML: Picture-perfect rendering
- Re: Non-goal for HTML: Picture-perfect rendering
- Re: Formal definition of HTML5 (was Re: Version information)
- RE: Versioning and html[5]
- Re: Formal definition of HTML5
- Re: Formal definition of HTML5 (was Re: Version information)
- RE: Formal definition of HTML5 (was Re: Version information)
- Re: A Compromise to the Versioning Debate
- Re: Versioning and html[5]
- Re: Formal definition of HTML5 (was Re: Version information)
- Re: Non-goal for HTML: Picture-perfect rendering
- Re: Non-goal for HTML: Picture-perfect rendering
- Re: Formal definition of HTML5 (was Re: Version information)
- Re: Non-goal for HTML: Picture-perfect rendering
- Re: Versioning and html[5]
- Re: A Compromise to the Versioning Debate
- Re: Non-goal for HTML: Picture-perfect rendering
- RE: Versioning and html[5]
- Re: Formal definition of HTML5 (was Re: Version information)
- Re: Versioning and html[5]
- Re: Non-goal for HTML: A Graphics API
- Re: Formal definition of HTML5 (was Re: Version information)
- Re: Formal definition of HTML5 (was Re: Version information)
- Re: Non-goal for HTML: Picture-perfect rendering
- Re: Pandering to poor authorship (was Proposing <indent> vs. <blockquote>)
- Re: Non-goal for HTML: Picture-perfect rendering
- Re: Non-goal for HTML: A Graphics API
- Re: Formal definition of HTML5 (was Re: Version information)
- Re: Aphorisms of First Principle [was Proposed Design Principles]
- Non-goal for HTML: A Graphics API
- Re: Formal definition of HTML5 (was Re: Version information)
- RE: Formal definition of HTML5 (was Re: Version information)
- Non-goal for HTML: Picture-perfect rendering
- RE: Formal definition of HTML5 (was Re: Version information)
- Re: Formal definition of HTML5 (was Re: Version information)
- usability testing [was: Proposing <indent> vs. <blockquote>]
- RE: Formal definition of HTML5 (was Re: Version information)
- Re: Formal definition of HTML5 (was Re: Version information)
- RE: Versioning and html[5]
- Re: Formal definition of HTML5 (was Re: Version information)
- Re: Formal definition of HTML5 (was Re: Version information)
- Re: Formal definition of HTML5 (was Re: Version information)
- Re: Formal definition of HTML5 (was Re: Version information)
- Re: Proposing <indent> vs. <blockquote>
Sunday, 15 April 2007
- RE: Formal definition of HTML5 (was Re: Version information)
- Re: A Compromise to the Versioning Debate
Monday, 16 April 2007
- Re: [whatwg] Video proposals
- Re: A Compromise to the Versioning Debate
- Re: A Compromise to the Versioning Debate
- Re: Pandering to poor authorship (was Proposing <indent> vs. <blockquote>)
- Re: A Compromise to the Versioning Debate
- Re: Pandering to poor authorship (was Proposing <indent> vs. <blockquote>)
- Re: Proposing <indent> vs. <blockquote>
- Re: A Compromise to the Versioning Debate
- Re: Pandering to poor authorship (was Proposing <indent> vs. <blockquote>)
- Re: Versioning and html[5]
- Re: legacy of incompetence? [was: a compromise to the versioning debate]
- Re: Pandering to poor authorship (was Proposing <indent> vs. <blockquote>)
- Re: Proposing <indent> vs. <blockquote>
- Re: A Compromise to the Versioning Debate
- Re: Proposing <indent> vs. <blockquote>
- Re: Pandering to poor authorship (was Proposing <indent> vs. <blockquote>)
- Re: A Compromise to the Versioning Debate
- Re: A Compromise to the Versioning Debate
- Re: A Compromise to the Versioning Debate
- Re: legacy of incompetence? [was: a compromise to the versioning debate]
- Re: legacy of incompetence? [was: a compromise to the versioning debate]
- Re: legacy of incompetence? [was: a compromise to the versioning debate]
- Re: legacy of incompetence? [was: a compromise to the versioning debate]
- Re: legacy of incompetence? [was: a compromise to the versioning debate]
- Re: HTML/XHTML
- RE: Versioning and html[5]
- Re: legacy of incompetence? [was: a compromise to the versioning debate]
- RE: Versioning and html[5]
- Re: Proposing <indent> vs. <blockquote>
- RE: Versioning and html[5]
- RE: Versioning and html[5]
- RE: Versioning and html[5]
- RE: Versioning and html[5]
- Re: Formal definition of HTML5 (was Re: Version information)
Sunday, 15 April 2007
- Re: Proposing <indent> vs. <blockquote>
- Re: A Compromise to the Versioning Debate
- Re: legacy of incompetence? [was: a compromise to the versioning debate]
- Re: A Compromise to the Versioning Debate
- Re: legacy of incompetence? [was: a compromise to the versioning debate]
- Re: Proposing <indent> vs. <blockquote>
- Re: Aphorisms of First Principle [was Proposed Design Principles]
- Re: Versioning and html[5]
- Re: Versioning and html[5]
- Re: legacy of incompetence? [was: a compromise to the versioning debate]
- Re: Versioning and html[5]
- Re: A Compromise to the Versioning Debate
- Re: legacy of incompetence? [was: a compromise to the versioning debate]
- Re: Versioning and html[5]
- Re: Proposing <indent> vs. <blockquote>
- Re: legacy of incompetence? [was: a compromise to the versioning debate]
- Re: A Compromise to the Versioning Debate
- Re: legacy of incompetence? [was: a compromise to the versioning debate]
- Re: legacy of incompetence? [was: a compromise to the versioning debate]
- Re: Versioning and html[5]
- Re: Versioning and html[5]
- Re: A Compromise to the Versioning Debate
- Re: Formal definition of HTML5 (was Re: Version information)
- Re: A Compromise to the Versioning Debate
- legacy of incompetence? [was: a compromise to the versioning debate]
- Re: Versioning and html[5]
- Re: Proposing <indent> vs. <blockquote>
- Re: Proposing <indent> vs. <blockquote>
- Re: Proposing <indent> vs. <blockquote>
- oops
- Re: A Compromise to the Versioning Debate
- Re: Versioning and html[5]
- How frozen is frozen?
- Re: Formal definition of HTML5 (was Re: Version information)
- Re: Formal definition of HTML5 (was Re: Version information)
- Re: Formal definition of HTML5 (was Re: Version information)
- Re: A Compromise to the Versioning Debate
- Re: A Compromise to the Versioning Debate
- Re: A Compromise to the Versioning Debate
- Re: A Compromise to the Versioning Debate
- Re: A Compromise to the Versioning Debate
- Re: A Compromise to the Versioning Debate
- Re: A Compromise to the Versioning Debate
- Re: Formal definition of HTML5 (was Re: Version information)
- Re: A Compromise to the Versioning Debate
- Re: A Compromise to the Versioning Debate
- Re: Formal definition of HTML5 (was Re: Version information)
- Re: A Compromise to the Versioning Debate
- Re: Formal definition of HTML5 (was Re: Version information)
- Re: Formal definition of HTML5 (was Re: Version information)
- Re: Formal definition of HTML5 (was Re: Version information)
- Re: A Compromise to the Versioning Debate
- Re: A Compromise to the Versioning Debate
- RE: Versioning and html[5]
- Re: Formal definition of HTML5 (was Re: Version information)
- Re: A Compromise to the Versioning Debate
- Re: A Compromise to the Versioning Debate
- Re: Formal definition of HTML5 (was Re: Version information)
- RE: Versioning and html[5]
- A Compromise to the Versioning Debate
- Re: Opt-in solutions ...and problems
- Re: Pandering to poor authorship (was Proposing <indent> vs. <blockquote>)
- Re: Introduce <term> element
- RE: Versioning and html[5]
- RE: Formal definition of HTML5 (was Re: Version information)
- Re: Patents and public (was: RE: Proposal to Adopt HTML5)
- Re: Versioning and html[5]
- RE: Patents and public
- RE: Formal definition of HTML5 (was Re: Version information)
- RE: Versioning and html[5]
- RE: Versioning and html[5]
- Re: Versioning and html[5]
- Re: Versioning and html[5]
- Re: Versioning and html[5]
- Re: Versioning and html[5]
- Re: Versioning and html[5]
- RE: Versioning and html[5]
- RE: Versioning and html[5]
- RE: Versioning and html[5]
- Re: Versioning and html[5]
- RE: Formal definition of HTML5 (was Re: Version information)
- RE: Versioning and html[5]
- Re: Pandering to poor authorship (was Proposing <indent> vs. <blockquote>)
- Re: Versioning and html[5]
- Re: Versioning and html[5]
Saturday, 14 April 2007
- Re: Versioning and html[5]
- Re: Proposing <indent> vs. <blockquote>
- RE: Versioning and html[5]
- Re: Versioning and html[5]
- Re: Versioning and html[5]
- Re: Versioning and html[5]
- Re: Versioning and html[5]
- Re: Formal definition of HTML5 (was Re: Version information)
- Re: Pandering to poor authorship (was Proposing <indent> vs. <blockquote>)
- Re: Versioning and html[5]
- Re: Versioning and html[5]
- Re: Versioning and html[5]
- Re: Versioning and html[5]
- Re: HTML/XHTML
- Re: Versioning and html[5]
- Re: Versioning and html[5]
- Re: Current working draft
- RE: Current working draft
- Re: Versioning and html[5]
- Current working draft
- Re: Versioning and html[5]
- Re: HTML/XHTML
- HTML/XHTML
- taking threads to www-archive or offline altogether
- Re: Proposing <indent> vs. <blockquote>
- Re: Version information
- Re: Version information
Friday, 13 April 2007
Saturday, 14 April 2007
- Re: Version information
- Re: Proposing <indent> vs. <blockquote>
- Re: Patents and public
- Re: Versioning and html[5]
- Re: Versioning and html[5]
- Re: Formal definition of HTML5 (was Re: Version information)
- Re: Versioning and html[5]
- Re: Versioning and html[5]
- Re: Versioning and html[5]
- Re: Formal definition of HTML5 (was Re: Version information)
- Re: Versioning and html[5]
- Re: Versioning and html[5]
- Re: Versioning and html[5]
- Re: Formal definition of HTML5 (was Re: Version information)
- Re: Proposing <indent> vs. <blockquote>
- Re: Proposing <indent> vs. <blockquote>
- Re: Proposing <indent> vs. <blockquote>
- Re: Proposing <indent> vs. <blockquote>
- Re: Formal definition of HTML5 (was Re: Version information)
- Re: Proposing <indent> vs. <blockquote>
- Re: Formal definition of HTML5 (was Re: Version information)
- Re: Aphorisms of First Principle [was Proposed Design Principles]
- Re: Patents and public
- Re: Pandering to poor authorship (was Proposing <indent> vs. <blockquote>)
- Re: Level of specification detail
- Re: Proposing <indent> vs. <blockquote>
- Re: Proposing <indent> vs. <blockquote>
- Re: Proposing <indent> vs. <blockquote>
- Re: Proposing <indent> vs. <blockquote>
- Re: Version information
- Re: Versioning and html[5]
- Re: Versioning and html[5]
- Re: Versioning and html[5]
- Re: Versioning and html[5]
- Re: Proposing <indent> vs. <blockquote>
- Re: Versioning and html[5]
- Re: Versioning and html[5]
- Re: Versioning and html[5]
- Re: Versioning and html[5]
- Re: Versioning and html[5]
- Re: Versioning and html[5]
Friday, 13 April 2007
- Re: Versioning and html[5]
- Re: Versioning and html[5]
- RE: Formal definition of HTML5 (was Re: Version information)
- RE: Versioning and html[5]
- Re: Versioning and html[5]
- Re: Versioning and html[5]
- RE: Formal definition of HTML5 (was Re: Version information)
- RE: Versioning and html[5]
- Re: Versioning and html[5]
- Re: Versioning and html[5]
- RE: Versioning and html[5]
- RE: Versioning and html[5]
- Re: Formal definition of HTML5 (was Re: Version information)
- RE: Versioning and html[5]
- Re: Versioning and html[5]
- RE: Versioning and html[5]
- RE: Versioning and html[5]
- RE: Level of specification detail (Was Re: Proposal to Adopt HTML5)
- RE: Versioning and html[5]
- Re: denying users direct access to document source
- denying users direct access to document source
- Re: Formal definition of HTML5 (was Re: Version information)
- User Agent (browser) WG at W3C [was: New discussion group are need]
- Microsoft versioning proposal
- RE: Versioning and html[5]
- RE: Level of specification detail (Was Re: Proposal to Adopt HTML5)
- RE: Versioning and html[5]
- RE: Versioning and html[5]
- RE: Versioning and html[5]
- RE: Versioning and html[5]
- RE: Versioning and html[5]
- RE: Versioning and html[5]
- RE: Intent to Conform (was Re: Version information)
- RE: Patents and public (was: RE: Proposal to Adopt HTML5)
- Re: Versioning and html[5]
- Re: Versioning and html[5]
- Re: Version information
- Re: New discussion group are need
- Re: Version information
- Re: New discussion group are need
- Re: New discussion group are need
- New discussion group are need
- Re[2]: special immediate form: TREE
- RE: Proposal to Adopt HTML5
Wednesday, 11 April 2007
Friday, 13 April 2007
- special immediate form: SELECT (LOOKER)
- Re: special immediate form: TREE special immediate form: TREE special immediate form: TREE
- special immediate form: TREE special immediate form: TREE special immediate form: TREE
- Re: small consultation
- small consultation
- Re: Formal definition of HTML5 (was Re: Version information)
- Re: wg members status
- Re: Opt-in solutions ...and problems (was Re: Versioning and html[5])
- Re: Versioning and html[5]
- Re: Formal definition of HTML5 (was Re: Version information)
- Re: Opt-in solutions ...and problems (was Re: Versioning and html[5])
- Re: Versioning and html[5]
- Re: Formal definition of HTML5 (was Re: Version information)
- Re: Formal definition of HTML5 (was Re: Version information)
- Re: Versioning and html[5]
- Re: Formal definition of HTML5 (was Re: Version information)
- regrets
- Re: Formal definition of HTML5 (was Re: Version information)
- Re: Versioning and html[5]
- Re: Versioning and html[5]
- Re: Versioning and html[5]
- Re: Formal definition of HTML5 (was Re: Version information)
- Formal definition of HTML5 (was Re: Version information)
- Re: Mask in string of address
- Mask in string of address
- Re: Versioning and html[5]
- Re: Opt-in solutions ...and problems (was Re: Versioning and html[5])
- Re: Versioning and html[5]
- Re: Versioning and html[5]
- Re: Versioning and html[5]
- Re: Version information
- Re: Versioning and html[5]
- Re: Version information
- are necessary tag PACK ?
- Re: Versioning and html[5]
- Re: Version information
- Re: Versioning and html[5]
- Re: Versioning and html[5]
- Re: Versioning and html[5]
- Aphorisms of First Principle [was Proposed Design Principles]
- Re: Opt-in solutions ...and problems (was Re: Versioning and html[5])
- Opt-in solutions ...and problems (was Re: Versioning and html[5])
- Re: Level of specification detail (Was Re: Proposal to Adopt HTML5)
- Re: Level of specification detail (Was Re: Proposal to Adopt HTML5)
- Re: Versioning and html[5]
- Re: Versioning and html[5]
Thursday, 12 April 2007
Friday, 13 April 2007
- Re: Versioning and html[5]
- Re: Level of specification detail (Was Re: Proposal to Adopt HTML5)
- Re: Pandering to poor authorship (was Proposing <indent> vs. <blockquote>)
Thursday, 12 April 2007
- RE: Versioning and html[5]
- RE: Versioning and html[5]
- Re: Versioning and html[5]
- Re: ensuring the existence & enhancing the power of Q
- RE: Versioning and html[5]
- Re: Deviance from SGML (was Re: Version information)
- Re: Version information
- Deviance from SGML (was Re: Version information)
- RE: Versioning and html[5]
- RE: Intent to Conform (was Re: Version information)
- RE: Versioning and html[5]
- RE: Versioning and html[5]
- Re: Version information
- RE: Versioning and html[5]
- RE: Versioning and html[5]
- Re: Versioning and html[5]
- Re: Version information
- RE: Versioning and html[5]
- Re: Versioning and html[5]
- Re: Version information
- Re: Version information
- Re: Version information
- Re: Version information
- Re: Patents and public (was: RE: Proposal to Adopt HTML5)
- Re: Version information
- Re: Version information
- Re: Version information
- Re: Version information
- Re: Version information
- Re: Version information
- Re: Version information
- Re: Versioning and html[5]
- Re: Proposing <indent> vs. <blockquote>
- Re: Intent to Conform (was Re: Version information)
- Re: Versioning and html[5]
- Re: Versioning and html[5]
- <object> attributes (Was: Versioning and html[5])
- Re: Versioning and html[5]
- Re: Level of specification detail (Was Re: Proposal to Adopt HTML5)
- Re: Versioning and html[5]
- Re: Versioning and html[5]
- Re: Proposal to Adopt HTML5 (patent policy FAQ))
- Re: Intent to Conform (was Re: Version information)
- Re: Intent to Conform (was Re: Version information)
- Re: Versioning and html[5]
- Re: Versioning and html[5]
- Re: Versioning and html[5]
- RE: Intent to Conform (was Re: Version information)
- Patents and public (was: RE: Proposal to Adopt HTML5)
- Re: Intent to Conform (was Re: Version information)
- Re: Proposal to Adopt HTML5
- Re: Versioning and html[5]
- Re: Proposing <indent> vs. <blockquote>
- Re: wg members status
- Re: wg members status
- RE: Versioning and html[5]
- Versioning and html[5]
- RE: Intent to Conform (was Re: Version information)
- Re: Level of specification detail
- Re: Alternate HTML 5 adoption proposal?
- Re: Proposal to Adopt HTML5
- Re: Proposal to Adopt HTML5
- Re: Proposal to Adopt HTML5
- Re: Proposing <indent> vs. <blockquote>
- RE: Proposal to Adopt HTML5
- Re: Proposing <indent> vs. <blockquote>
- Re[2]: brainstorm: repeating form controls
- Re: Pandering to poor authorship (was Proposing <indent> vs. <blockquote>)
- Re: Level of specification detail
- Re: Design Principles updated
- Re: Level of specification detail (Was Re: Proposal to Adopt HTML5)
- Re: Proposal to Adopt HTML5
- Re: tasks to supplement HTML specification development
- Re: Proposal to Adopt HTML5
- Re: Design Principles updated
- Re: Design Principles updated
- Re: Intent to Conform (was Re: Version information)
- Re: Pandering to poor authorship (was Proposing <indent> vs. <blockquote>)
- Re: Level of specification detail
- Re: Design Principles updated
- Design Principles updated
- Re: Organization Weakness Re: Proposal to Adopt HTML5
- Re: Organization Weakness Re: Proposal to Adopt HTML5
- Organization Weakness Re: Proposal to Adopt HTML5
- Re: splitting HTML5 into chunks
- Re: Proposing <indent> vs. <blockquote>
- Re: Proposing <indent> vs. <blockquote>
- Re: Level of specification detail (Was Re: Proposal to Adopt HTML5)
- Re: Level of specification detail (Was Re: Proposal to Adopt HTML5)
- Re: Proposing <indent> vs. <blockquote>
- Re: Proposing <indent> vs. <blockquote>
- Re: Proposing <indent> vs. <blockquote>
- Re: Proposal to Adopt HTML5
- Re: Proposal to Adopt HTML5
- Re: Proposal to Adopt HTML5
- Re: splitting HTML5 into chunks
- Re: Level of specification detail (Was Re: Proposal to Adopt HTML5)
Wednesday, 11 April 2007
Thursday, 12 April 2007
- Re: Proposal to Adopt HTML5 -- procedural issue
- Canvas testing Re: tasks to supplement HTML specification development
Wednesday, 11 April 2007
- Re: Proposal to Adopt HTML5
- Re: splitting HTML5 into chunks [was: Proposal to Adopt HTML5]
- Re: wg members status
- splitting HTML5 into chunks [was: Proposal to Adopt HTML5]
- Re: tasks to supplement HTML specification development
- Re: Proposal to Adopt HTML5
- Re: Proposal to Adopt HTML5
- Re: Alternate HTML 5 adoption proposal? (Was Re: Level of specification detail)
- Re: Proposal to Adopt HTML5
- Re: Proposal to Adopt HTML5
- Re: Proposal to Adopt HTML5
- Re: Alternate HTML 5 adoption proposal? (Was Re: Level of specification detail)
- Re: Proposal to Adopt HTML5
- Re: wg members status
- Re: Alternate HTML 5 adoption proposal? (Was Re: Level of specification detail)
- Re: Proposal to Adopt HTML5
- Re: Level of specification detail (Was Re: Proposal to Adopt HTML5)
- Re: wg members status
- Re: Proposal to Adopt HTML5
- Re: wg members status
- Re: Proposal to Adopt HTML5
- Re: Proposal to Adopt HTML5
- Re: Proposal to Adopt HTML5
- Re: tasks to supplement HTML specification development
- Re: wg members status
- Re: Proposal to Adopt HTML5 -- procedural issue
- Re: Alternate HTML 5 adoption proposal? (Was Re: Level of specification detail)
- Re: Proposal to Adopt HTML5
- Re: tasks to supplement HTML specification development
- Re: tasks to supplement HTML specification development
- Re: Alternate HTML 5 adoption proposal? (Was Re: Level of specification detail)
- Alternate HTML 5 adoption proposal? (Was Re: Level of specification detail)
- Re: Level of specification detail (Was Re: Proposal to Adopt HTML5)
- Re: Proposal to Adopt HTML5
- Re: Proposal to Adopt HTML5 -- procedural issue
- Re: brainstorm: lines and existing html-elements
- tasks to supplement HTML specification development
- Re: Level of specification detail (Was Re: Proposal to Adopt HTML5)
- Care with subject lines and threads [was: Proposal to Adopt ...]
- Re: Proposal to Adopt HTML5 -- procedural issue
- access to client-side files [was: Proposal to Adopt HTML5 -- procedural issue]
- Re: Proposal to Adopt HTML5
- Re: Proposal to Adopt HTML5
- Re: Proposal to Adopt HTML5
- Re: Proposal to Adopt HTML5
- Re: Proposal to Adopt HTML5
- Re: Proposal to Adopt HTML5
- Re: Microsoft has now joined the HTML Working Group
- brainstorm: lines and existing html-elements
- Re: wg members status
- Re: Proposal to Adopt HTML5
- Re: Level of specification detail (Was Re: Proposal to Adopt HTML5)
- Re: wg members status
- Level of specification detail (Was Re: Proposal to Adopt HTML5)
- Re: wg members status
- Re: wg members status
- Re: wg members status
- Re: Proposal to Adopt HTML5 -- procedural issue
- Re: Proposal to Adopt HTML5 -- procedural issue
- wg members status
- Re: Introduce <term> element
- Re: Introduce <term> element
- RE: Proposal to Adopt HTML5 -- procedural issue
- RE: Proposal to Adopt HTML5 -- procedural issue
- Re: Proposal to Adopt HTML5
- Re: Proposal to Adopt HTML5
Tuesday, 10 April 2007
Wednesday, 11 April 2007
Tuesday, 10 April 2007
- Re: Proposal to Adopt HTML5
- Re: Proposal to Adopt HTML5 -- procedural issue
- Re: Proposal to Adopt HTML5
- Re: Proposal to Adopt HTML5
- Re: Proposal to Adopt HTML5
- Re: Proposal to Adopt HTML5
- Re: Proposal to Adopt HTML5
- Re: Proposal to Adopt HTML5
- Re: Proposal to Adopt HTML5
- Re: Proposal to Adopt HTML5
- Re: Proposal to Adopt HTML5
- Re: Proposal to Adopt HTML5
- Re: Proposal to Adopt HTML5
- Re: Proposal to Adopt HTML5
- Re: Proposal to Adopt HTML5
- Re: Proposal to Adopt HTML5
- Re: Proposal to Adopt HTML5
- Re: Proposal to Adopt HTML5
- Re: Proposal to Adopt HTML5
- Re: Proposal to Adopt HTML5
- Re: Proposal to Adopt HTML5
- Re: Proposal to Adopt HTML5
- Re: Proposal to Adopt HTML5
- Re: Proposal to Adopt HTML5
- Re: Proposal to Adopt HTML5
- Re: Proposal to Adopt HTML5
- Re: Proposal to Adopt HTML5
- Re: Proposal to Adopt HTML5
- RE: Proposal to Adopt HTML5
- RE: Proposal to Adopt HTML5
- Re: Proposal to Adopt HTML5
- Re: Proposal to Adopt HTML5
- Re: Proposal to Adopt HTML5
- RE: Proposal to Adopt HTML5
- Re: Proposal to Adopt HTML5
- Re: Proposal to Adopt HTML5
- Re: Proposal to Adopt HTML5
- RE: Proposal to Adopt HTML5
- RE: Proposal to Adopt HTML5
- RE: Proposal to Adopt HTML5
- Re: Proposal to Adopt HTML5
- Re: Proposal to Adopt HTML5
- RE: Proposal to Adopt HTML5
- RE: Proposal to Adopt HTML5
- Re: Proposal to Adopt HTML5
- Re: Proposal to Adopt HTML5
- Re: Proposal to Adopt HTML5
- Re: Overall strategy (Was Re: Proposal to Adopt HTML5)
- Re: Proposal to Adopt HTML5
- RE: Proposal to Adopt HTML5 -- procedural issue
- Re: Overall strategy
- Re: Proposal to Adopt HTML5
- Re: Overall strategy (Was Re: Proposal to Adopt HTML5)
- Overall strategy (Was Re: Proposal to Adopt HTML5)
- Re: innerHTML and setTimeout
- Re: Proposal to Adopt HTML5
- Re: Proposal to Adopt HTML5
- Re: Proposal to Adopt HTML5
- Re: Proposal to Adopt HTML5
- Re: Proposal to Adopt HTML5
- Re: Proposal to Adopt HTML5
- Re: Proposal to Adopt HTML5
- Re: Proposal to Adopt HTML5
Monday, 9 April 2007
Tuesday, 10 April 2007
- Re: Proposal to Adopt HTML5
- Re: Proposal to Adopt HTML5
- Re: Proposal to Adopt HTML5
- Re: Proposal to Adopt HTML5
- Re: Proposal to Adopt HTML5
- Re: innerHTML and setTimeout
- Proposal to Adopt HTML5
- RE: innerHTML and setTimeout
Monday, 9 April 2007
- Re: innerHTML and setTimeout
- Re: Introduce <term> element
- Re: innerHTML and setTimeout
- Re: innerHTML and setTimeout
- Re: innerHTML and setTimeout
- Re: Canvas
- RE: beforeprint event
- Re: innerHTML and setTimeout
- Re: innerHTML and setTimeout
- Re: beforeprint event
- Re: Version information
- Re: Version information
- Re: Canvas
- Re: innerHTML and setTimeout
- Re: innerHTML and setTimeout
- Re: Intent to Conform (was Re: Version information)
- Re: Version information
- RE: Intent to Conform (was Re: Version information)
- Intent to Conform (was Re: Version information)
- innerHTML and setTimeout
- RE: beforeprint event
- Re: Proposing <indent> vs. <blockquote>
- Re: Version information
- Re: Version information
- Re: Proposing <indent> vs. <blockquote>
- Re: Proposing <indent> vs. <blockquote>
- Re: beforeprint event
- Re: Proposing <indent> vs. <blockquote>
- Re: brainstorm: repeating form controls
- brainstorm: alternative form controls
- brainstorm: repeating form controls
- Re: beforeprint event
- Re: Proposing <indent> vs. <blockquote>
- Re: beforeprint event
- Re: Introduce <term> element
- Re: Use the role-attribute instead of predefined class names
- Proposing <indent> vs. <blockquote>
- beforeprint event (was: Re: Microsoft has now joined the HTML Working Group)
- Re: Microsoft has now joined the HTML Working Group
- Re: Mandated Video Format
- Re: The HTMLWG and WHATWG (Was: Default (informal) Style Sheet)
- Re: Microsoft has now joined the HTML Working Group
- RE: Version information
- Re: Version information
- RE: Version information
- RE: Microsoft has now joined the HTML Working Group
- RE: Version information
- RE: Version information
- Re: Canvas
Sunday, 8 April 2007
- Semantics is not semantics (was: HTML WG Glossary)
- Re: <table> terse mode for data entry
- Re: <table> terse mode for data entry
- Re: Canvas
- Re: Microsoft has now joined the HTML Working Group
- <table> terse mode for data entry
- HTML WG Glossary
- Re: <table type="rowsortable">
- Re: rel=noreferrer
- Re: Canvas
- Re: Canvas
- Re: rel=noreferrer
- Re: Version information
- Re: Canvas
- rel=noreferrer
- Re: Use the role-attribute instead of predefined class names
- Re: <table type="rowsortable">
- RE: Use the role-attribute instead of predefined class names
- VP3 as the Mandated Video Format?
- Canvas [was RE: Microsoft has now joined the HTML Working Group]
- Re: Use the role-attribute instead of predefined class names
- Re: Use the role-attribute instead of predefined class names
- RE: <table type="rowsortable">
- Re: Canvas
Saturday, 7 April 2007
- Re: Version information
- Re: Version information
- Re: Version information
- RE: Version information
- Re: [whatwg] Default (informal) Style Sheet
- Re: Use the role-attribute instead of predefined class names
- Re: [whatwg] Default (informal) Style Sheet
- Re: [whatwg] Default (informal) Style Sheet
- Re: Use the role-attribute instead of predefined class names
- Re: [whatwg] Default (informal) Style Sheet
- Re: [whatwg] Default (informal) Style Sheet
- Re: Use the role-attribute instead of predefined class names
- Re: Use the role-attribute instead of predefined class names
- Re: Version information
- Re: Version information
- RE: Version information
- Re: Canvas
- Re: Version information
- Re: Version information
- Re: Version information
- Re: Version information
- Re: Version information
Friday, 6 April 2007
- RE: Version information
- Re: Version information
- Re: Version information
- RE: Version information
- RE: Version information
- Re: CSS for print (was: Microsoft has now joined the HTML Working Group)
- Re: Canvas
- Re: Canvas
- Re: Canvas
- Re: Canvas
- Re: Microsoft has now joined the HTML Working Group
- RE: Canvas
- Re: Canvas
- RE: Version information
- RE: Mandated Video Format
- Re: Canvas (was: Microsoft has now joined the HTML Working Group)
- Re: Version information
- <canvas> (was Re: Microsoft has now joined the HTML Working Group)
- Re: Canvas
- Re: Canvas (was: Microsoft has now joined the HTML Working Group)
- RE: Canvas
- RE: CSS for print
- RE: Version information
- Re: Canvas
- Re: Version information
- Canvas (was: Microsoft has now joined the HTML Working Group)
- RE: CSS for print (was: Microsoft has now joined the HTML Working Group)
- RE: Version information (was Re: HTML5 vs HTML6)
- RE: Microsoft has now joined the HTML Working Group
- Re: Mandated Video Format
- RE: Mandated Video Format
- Re: Mandated Video Format
- Re: Mandated Video Format
- RE: Mandated Video Format
- RE: Mandated Video Format
- Re: CSS for print (was: Microsoft has now joined the HTML Working Group)
- CSS for print (was: Microsoft has now joined the HTML Working Group)
- Re: Use the role-attribute instead of predefined class names
- Re: Use the role-attribute instead of predefined class names
- Re: [whatwg] Default (informal) Style Sheet
- Re: Use the role-attribute instead of predefined class names
- Re: [whatwg] Default (informal) Style Sheet
- Re: Microsoft has now joined the HTML Working Group
- Re: Mandated Video Format
- Re: Mandated Video Format
- Re: Microsoft has now joined the HTML Working Group
- Re: Why <video>? (was Re: Microsoft has now joined the HTML Working Group)
Thursday, 5 April 2007
Friday, 6 April 2007
- Why <video>? (was Re: Microsoft has now joined the HTML Working Group)
- Re: DefaultStyleSheet05: (was Default (informal) Style Sheet)
- Re: [whatwg] Default (informal) Style Sheet
- Re: [whatwg] Default (informal) Style Sheet
- Re: [whatwg] Default (informal) Style Sheet
- Version information (was Re: HTML5 vs HTML6)
Thursday, 5 April 2007
- Re: Microsoft has now joined the HTML Working Group
- Re: Mandated Video Format
- RE: Mandated Video Format (was: Microsoft has now joined the HTML Working Group)
- Re: Microsoft has now joined the HTML Working Group
- RE:Re: Microsoft has now joined the HTML Working Group
- RE: GIF was -- Mandated Video Format (was: Microsoft has now joined the HTML Working Group)
- RE: Microsoft has now joined the HTML Working Group
- Re: Microsoft has now joined the HTML Working Group
- RE: Mandated Video Format
- Re: argument for deprecating BLOCKQUOTE in canonical HTML/XHTML
- RE: Microsoft has now joined the HTML Working Group
- RE: Mandated Video Format
- RE: Mandated Video Format
- Use the role-attribute instead of predefined class names
- RE: Mandated Video Format (was: Microsoft has now joined the HTML Working Group)
- Re: The HTMLWG and WHATWG (Was: Default (informal) Style Sheet)
- Re: Mandated Video Format (was: Microsoft has now joined the HTML Working Group)
- RE: The HTMLWG and WHATWG (Was: Default (informal) Style Sheet)
- Re: The HTMLWG and WHATWG (Was: Default (informal) Style Sheet)
- Re: Mandated Video Format (was: Microsoft has now joined the HTML Working Group)
- RE: Mandated Video Format (was: Microsoft has now joined the HTML Working Group)
- Re: Mandated Video Format (was: Microsoft has now joined the HTML Working Group)
- RE: Microsoft has now joined the HTML Working Group
- RE: Mandated Video Format (was: Microsoft has now joined the HTML Working Group)
- RE: The HTMLWG and WHATWG (Was: Default (informal) Style Sheet)
- RE: Microsoft has now joined the HTML Working Group
- Mandated Video Format (was: Microsoft has now joined the HTML Working Group)
- Re: Microsoft has now joined the HTML Working Group
- Re: ensuring the existence & enhancing the power of Q
- Re: argument for deprecating BLOCKQUOTE in canonical HTML/XHTML
- Re: semantics [was Re: Proposed Design Principles updated]
- Re: ensuring the existence & enhancing the power of Q
- Re: argument for deprecating BLOCKQUOTE in canonical HTML/XHTML
- Re: ensuring the existence & enhancing the power of Q
- Re: argument for deprecating BLOCKQUOTE in canonical HTML/XHTML
- RE: Microsoft has now joined the HTML Working Group
- Re: ensuring the existence & enhancing the power of Q
- Re: ensuring the existence & enhancing the power of Q
- Re: Form fields for uploading
- Re: argument for deprecating BLOCKQUOTE in canonical HTML/XHTML
- Re: argument for deprecating BLOCKQUOTE in canonical HTML/XHTML
- Re: argument for deprecating BLOCKQUOTE in canonical HTML/XHTML
- Re: Microsoft has now joined the HTML Working Group
- Re: argument for deprecating BLOCKQUOTE in canonical HTML/XHTML
- Re: Microsoft has now joined the HTML Working Group
- Re: The HTMLWG and WHATWG (Was: Default (informal) Style Sheet)
- Re: Proposed Design Principles updated
- Re: Introduce <term> element
- Re: Proposed Design Principles updated
- Re: Proposed Design Principles updated
- Role of Chair (Was: Microsoft has now joined the HTML Working Group)
- Re: Microsoft has now joined the HTML Working Group
- Re: <table type="rowsortable">
- RE: semantics [was Re: Proposed Design Principles updated]
Wednesday, 4 April 2007
- Re: Form fields for uploading
- Re: Introduce <term> element
- Re: Proposed Design Principles updated
- Re: argument for deprecating BLOCKQUOTE in canonical HTML/XHTML
- Re: argument for deprecating BLOCKQUOTE in canonical HTML/XHTML
- Re: <table type="rowsortable">
- Re: argument for deprecating BLOCKQUOTE in canonical HTML/XHTML
- Re: <table type="rowsortable">
- Re: Introduce <term> element
- Re: argument for deprecating BLOCKQUOTE in canonical HTML/XHTML
- Re: <table type="rowsortable">
- Re: <table type="rowsortable">
- Re: argument for deprecating BLOCKQUOTE in canonical HTML/XHTML
- Re: Introduce <term> element
- Re: argument for deprecating BLOCKQUOTE in canonical HTML/XHTML
- Re: argument for deprecating BLOCKQUOTE in canonical HTML/XHTML
- Re: The HTMLWG and WHATWG
- Re: HTML5 vs HTML6
- RE: Let every element have a src attribute
- RE: Proposed Design Principles updated
- RE: Proposed Design Principles updated ("don't break the web" vs respecting MIME types)
- RE: <table type="rowsortable">
- Microsoft has now joined the HTML Working Group
- Re: argument for deprecating BLOCKQUOTE in canonical HTML/XHTML
- Re: Proposed Design Principles updated ("don't break the web" vs respecting MIME types)
- Re: Proposed Design Principles updated ("don't break the web" vs respecting MIME types)
- Re: Let every element have a src attribute
- Re: Let every element have a src attribute
- Re: Let every element have a src attribute
- Re: The HTMLWG and WHATWG
- Re: <table type="rowsortable">
- Re: Let every element have a src attribute
- Re: Let every element have a src attribute
- Re: argument for deprecating BLOCKQUOTE in canonical HTML/XHTML
- <table type="rowsortable">
- semantics [was Re: Proposed Design Principles updated]
- Re: Let every element have a src attribute
- Re: Proposed Design Principles updated
- Re: Proposed Design Principles updated
- Re: Proposed Design Principles updated
- Re: argument for deprecating BLOCKQUOTE in canonical HTML/XHTML
- Re: argument for deprecating BLOCKQUOTE in canonical HTML/XHTML
- Re: HTML5 vs HTML6
- Links to DOM Ranges (was Re: argument for deprecating BLOCKQUOTE in canonical HTML/XHTML)
- Re: argument for deprecating BLOCKQUOTE in canonical HTML/XHTML
- Introduce <term> element
- Re: Proposed Design Principles updated
- Re: Proposed Design Principles updated
- Re: Proposed Design Principles updated
- Re: Proposed Design Principles updated
- Re: Proposed Design Principles updated
- Re: Proposed Design Principles updated
- Re: HTML5 vs HTML6
- Re: HTML5 vs HTML6
- Re: Proposed Design Principles updated
- Re: Proposed Design Principles updated
- Re: Proposed Design Principles updated
- Re: Proposed Design Principles updated
- Re: Proposed Design Principles updated
- Re: Let every element have a src attribute
- Re: Let every element have a src attribute
Tuesday, 3 April 2007
- Re: argument for deprecating BLOCKQUOTE in canonical HTML/XHTML
- Re: Proposed Design Principles updated
- HTML5 vs HTML6
- Re: style.background rendering - browser inconsistency
- Re: The HTMLWG and WHATWG (Was: Default (informal) Style Sheet)
- Re: Proposed Design Principles updated
- Re: style.background rendering - browser inconsistency
- Re: style.background rendering - browser inconsistency
- style.background rendering - browser inconsistency
- Re: Proposed Design Principles updated
- Re: Proposed Design Principles updated
- Re: HTML5 vs HTML6
- HTML5 vs HTML6
- Re: Proposed Design Principles updated
- Re: Proposed Design Principles updated
- Re: The HTMLWG and WHATWG (Was: Default (informal) Style Sheet)
- Re: argument for deprecating BLOCKQUOTE in canonical HTML/XHTML
- Re: Let every element have a src attribute
- Re: Let every element have a src attribute
- Re: Let every element have a src attribute
- Re: argument for deprecating BLOCKQUOTE in canonical HTML/XHTML
- Re: argument for deprecating BLOCKQUOTE in canonical HTML/XHTML
- Re: Let every element have a src attribute
- Re: Let every element have a src attribute
- Re: Proposed Design Principles updated
- Re: ensuring the existence & enhancing the power of Q
- Re: argument for deprecating BLOCKQUOTE in canonical HTML/XHTML
- Re: argument for deprecating BLOCKQUOTE in canonical HTML/XHTML
- Re: argument for deprecating BLOCKQUOTE in canonical HTML/XHTML
- Re: argument for deprecating BLOCKQUOTE in canonical HTML/XHTML
- Re: argument for deprecating BLOCKQUOTE in canonical HTML/XHTML
- Re: ensuring the existence & enhancing the power of Q
- Re: argument for deprecating BLOCKQUOTE in canonical HTML/XHTML
- Re: <abbr>, <acronym> and initialisms
- Re: <abbr>, <acronym> and initialisms
- Re: no HTML WG meeting around XTech
- Re: text/javascript as default for type attribute
- Re: Let every element have a src attribute
- Re: Let every element have a src attribute
- Re: no HTML WG meeting around XTech
- Re: ensuring the existence & enhancing the power of Q
- Re: ensuring the existence & enhancing the power of Q
- Re: text/javascript as default for type attribute
- Proposed Design Principles updated
- Re: Let every element have a src attribute
- Re: Let every element have a src attribute
- Re: ensuring the existence & enhancing the power of Q
Monday, 2 April 2007
- RE: argument for deprecating BLOCKQUOTE in canonical HTML/XHTML
- Re: ensuring the existence & enhancing the power of Q
- Re: ensuring the existence & enhancing the power of Q
- Re: ensuring the existence & enhancing the power of Q
- Re: ensuring the existence & enhancing the power of Q
- Re: argument for deprecating BLOCKQUOTE in canonical HTML/XHTML
- Re: ensuring the existence & enhancing the power of Q
- Re: ensuring the existence & enhancing the power of Q
- Re: ensuring the existence & enhancing the power of Q
- Re: ensuring the existence & enhancing the power of Q
- Re: ensuring the existence & enhancing the power of Q
- Re: ensuring the existence & enhancing the power of Q
- Re: ensuring the existence & enhancing the power of Q
- Re: ensuring the existence & enhancing the power of Q
- argument for deprecating BLOCKQUOTE in canonical HTML/XHTML
- Re: text/javascript as default for type attribute
- Re: deprecate HR; replace with LS (logical seperator)
- deprecate HR; replace with LS (logical seperator)
- Re: Bring back <ol start="N"> in Strict mode
- Re: ensuring the existence & enhancing the power of Q
- Re: Bring back <ol start="N"> in Strict mode
- Re: Naming Wiki Pages
- Re: Naming Wiki Pages
- Re: ensuring the existence & enhancing the power of Q
- Re: text/javascript as default for type attribute
- Re: ensuring the existence & enhancing the power of Q
- Re: The HTMLWG and WHATWG (Was: Default (informal) Style Sheet)
- Re: ensuring the existence & enhancing the power of Q
- Re: Bring back <ol start="N"> in Strict mode
- Re: Bring back <ol start="N"> in Strict mode
- Re: text/javascript as default for type attribute
- no HTML WG meeting around XTech
- Re: ensuring the existence & enhancing the power of Q
- Re: text/javascript as default for type attribute
- Re: text/javascript as default for type attribute
- text/javascript as default for type attribute
- Re: ensuring the existence & enhancing the power of Q
- Bring back <ol start="N"> in Strict mode
- Re: ensuring the existence & enhancing the power of Q
- Re: Naming Wiki Pages
- Re: ensuring the existence & enhancing the power of Q
- Re: Naming Wiki Pages
- Re: Proposed Design Principles
- Re: Form fields for uploading
- Re: Form fields for uploading
- Re: The HTMLWG and WHATWG (Was: Default (informal) Style Sheet)
- Re: ensuring the existence & enhancing the power of Q
- Re: abbreviations in canonical HTML (thoughts & concrete suggestions)
- Re: Form fields for uploading
- Re: Form fields for uploading
- ensuring the existence & enhancing the power of Q
- abbreviations in canonical HTML (thoughts & concrete suggestions)
- Re: Form fields for uploading
- Re: Form fields for uploading
- Form fields for uploading
- Re: Superstructure markup
- Re: Naming Wiki Pages
- Re: The HTMLWG and WHATWG (Was: Default (informal) Style Sheet)
Sunday, 1 April 2007
Monday, 2 April 2007
- New widget: picture
- Re: Posting to this list
- Re: Let every element have a src attribute
- New widget: picture
- Re: Let every element have a src attribute
Sunday, 1 April 2007
Monday, 2 April 2007
- New widget: picture
- Re: DefaultStyleSheet05: (was Default (informal) Style Sheet)
- Re: Let every element have a src attribute
- Superstructure markup
- Re: DefaultStyleSheet05: (was Default (informal) Style Sheet)
- Re: Let every element have a src attribute
- Re: DefaultStyleSheet05: (was Default (informal) Style Sheet)
- Re: [whatwg] Default (informal) Style Sheet
- Re: [whatwg] Default (informal) Style Sheet
- Re: [whatwg] Default (informal) Style Sheet
- Re: Let every element have a src attribute
- Re: Naming Wiki Pages
- Re: The HTMLWG and WHATWG (Was: Default (informal) Style Sheet)
- Re: Naming Wiki Pages
- Re: Posting to this list
- Re: Naming Wiki Pages
- Re: Let every element have a src attribute
- Re: The HTMLWG and WHATWG (Was: Default (informal) Style Sheet)
- Re: [whatwg] Default (informal) Style Sheet
- Re: Naming Wiki Pages
- Re: The HTMLWG and WHATWG (Was: Default (informal) Style Sheet)
- Re: Naming Wiki Pages
- Re: [whatwg] Default (informal) Style Sheet
- Re: [whatwg] Default (informal) Style Sheet
- Re: [whatwg] Default (informal) Style Sheet
- [admin] switch to monthly archives
- The HTMLWG and WHATWG (Was: Default (informal) Style Sheet)
- RE: Naming Wiki Pages
- Re: DefaultStyleSheet05: (was Default (informal) Style Sheet)
- DefaultStyleSheet05: (was Default (informal) Style Sheet)
- Browser Fragment Positioning (was Default (informal) Style Sheet)
- Re: Default (informal) Style Sheet
- RE: Why Have Design Principles? (was Re: Design Principles Document update)
- Re: Posting to this list
Sunday, 1 April 2007
- Why Have Design Principles? (was Re: Design Principles Document update)
- Re: Posting to this list
- Re: Doctypes and the dialects of HTML 5
- Re: [whatwg] Default (informal) Style Sheet
- Re: [whatwg] Default (informal) Style Sheet
- Re: Default (informal) Style Sheet
Saturday, 31 March 2007
Sunday, 1 April 2007
- Re: [whatwg] <video> element feedback
- Re: Default (informal) Style Sheet
- RE: [whatwg] Default (informal) Style Sheet
- Re: Design Principles Document update
- Re: Doctypes and the dialects of HTML 5
- Re: Default (informal) Style Sheet
- Default (informal) Style Sheet
- Re: Proposed Design Principles
- Re: Doctypes and the dialects of HTML 5
- Re: Multipart response support
- Re: E-mail subscription and RSS