Wednesday, 30 June 2010
Tuesday, 29 June 2010
- RE: ACTION-182 and Issue-27
- Re: Processing of &prod_id= in attributes
- Re: Processing of &prod_id= in attributes
- Re: Processing of &prod_id= in attributes
- Re: Processing of &prod_id= in attributes
- Re: Processing of &prod_id= in attributes
- Re: Processing of &prod_id= in attributes
- Re: Processing of &prod_id= in attributes
- Processing of &prod_id= in attributes
- Re: ACTION-182 and Issue-27
- Re: Conformance requirements related to differences that must not matter
- [Bug 10026] Scope attribute for TD
- Re: Conformance requirements related to differences that must not matter
- Conformance requirements related to differences that must not matter
- Re: HTML4 Diffs - Object, again
Sunday, 27 June 2010
- [Bug 9657] Content model of object
- Re: HTML4 Diffs - Object, again
- Re: HTML4 Diffs - Object, again
- Re: HTML4 Diffs - Object, again
- Re: HTML4 Diffs - Object, again
- Re: HTML4 Diffs - Object, again
- Re: HTML4 Diffs - Object, again
- Re: HTML4 Diffs - Object, again
- HTML4 Diffs - Object, again
Saturday, 26 June 2010
- Re: Differences between the W3C and WHATWG specifications
- IETF 78 meeting in Maastricht
- Re: Differences between the W3C and WHATWG specifications
Friday, 25 June 2010
- [Bug 10017] longdesc and @aria-describedby (ARIA)
- [Bug 10016] longdesc and @role (ARIA)
- [Bug 10015] longdesc URL checking
- Re: Differences between the W3C and WHATWG specifications
- Re: Differences between the W3C and WHATWG specifications
- Re: Differences between the W3C and WHATWG specifications
- ACTION-182 and Issue-27
- Re: CfC: Adopt ISSUE-105 canvas-usemap Change Proposal to add usemap attribute to the canvas element
- RE: Differences between the W3C and WHATWG specifications
- Re: CfC: Adopt ISSUE-105 canvas-usemap Change Proposal to add usemap attribute to the canvas element
- Re: Differences between the W3C and WHATWG specifications
- Re: Differences between the W3C and WHATWG specifications
- Re: Differences between the W3C and WHATWG specifications
- Re: CfC: Adopt ISSUE-105 canvas-usemap Change Proposal to add usemap attribute to the canvas element
- Re: on<event> attributes as global attributes
- Re: on<event> attributes as global attributes
- Re: CfC: Adopt ISSUE-105 canvas-usemap Change Proposal to add usemap attribute to the canvas element
- Re: CfC: Adopt ISSUE-105 canvas-usemap Change Proposal to add usemap attribute to the canvas element
- Re: CfC: Adopt ISSUE-105 canvas-usemap Change Proposal to add usemap attribute to the canvas element
Thursday, 24 June 2010
- Re: CfC: Adopt ISSUE-105 canvas-usemap Change Proposal to add usemap attribute to the canvas element
- Re: CfC: Adopt ISSUE-105 canvas-usemap Change Proposal to add usemap attribute to the canvas element
- Re: ISSUE-88: content-language-multiple - Straw Poll for Objections
- Re: ISSUE-88: content-language-multiple - Straw Poll for Objections
- Re: ISSUE-88: content-language-multiple - Straw Poll for Objections
- Re: ISSUE-88: content-language-multiple - Straw Poll for Objections
- Re: ISSUE-88: content-language-multiple - Straw Poll for Objections
- Re: ISSUE-88: content-language-multiple - Straw Poll for Objections
- Re: on<event> attributes as global attributes
- Re: CfC: Adopt ISSUE-105 canvas-usemap Change Proposal to add usemap attribute to the canvas element
- Re: CfC: Adopt ISSUE-101 us-ascii-ref Change Proposal to replace ASCII reference
- Re: CfC: Adopt ISSUE-105 canvas-usemap Change Proposal to add usemap attribute to the canvas element
- Re: CfC: Adopt ISSUE-105 canvas-usemap Change Proposal to add usemap attribute to the canvas element
- Re: CfC: Adopt ISSUE-105 canvas-usemap Change Proposal to add usemap attribute to the canvas element
- Re: CfC: Adopt ISSUE-101 us-ascii-ref Change Proposal to replace ASCII reference
- on<event> attributes as global attributes
- Re: CfC: Adopt ISSUE-105 canvas-usemap Change Proposal to add usemap attribute to the canvas element
- Re: CfC: Adopt ISSUE-101 us-ascii-ref Change Proposal to replace ASCII reference
- Re: CfC: Adopt ISSUE-101 us-ascii-ref Change Proposal to replace ASCII reference
- Re: CfC: Adopt ISSUE-107 plugin-fallback-example Change Proposal to replace <object> fallback example
- Re: CfC: Adopt ISSUE-107 plugin-fallback-example Change Proposal to replace <object> fallback example
- Re: CfC: Adopt ISSUE-105 canvas-usemap Change Proposal to add usemap attribute to the canvas element
- Re: CfC: Adopt ISSUE-101 us-ascii-ref Change Proposal to replace ASCII reference
- Re: Null change proposal for ISSUE-80
- Re: ISSUE-31 Change Proposal
- Re: Null change proposal for ISSUE-31
- Re: Differences between the W3C and WHATWG specifications
- Fwd: Re: Differences between the W3C and WHATWG specifications
- Re: Differences between the W3C and WHATWG specifications
- Re: Differences between the W3C and WHATWG specifications
- Re: Differences between the W3C and WHATWG specifications
- Re: Null change proposal for ISSUE-80
- Re: ISSUE-88: content-language-multiple - Straw Poll for Objections
- Re: Null change proposal for ISSUE-31
Wednesday, 23 June 2010
- Re: CfC: Adopt ISSUE-105 canvas-usemap Change Proposal to add usemap attribute to the canvas element
- Re: CfC: Adopt ISSUE-105 canvas-usemap Change Proposal to add usemap attribute to the canvas element
- Re: <figure> bugs in Differences document
- Re: ISSUE-31 Change Proposal
- Re: ISSUE-31 Change Proposal
- Re: ISSUE-88: content-language-multiple - Straw Poll for Objections
- Re: ISSUE-30: longdesc - Straw Poll for Objections
- Re: CfC: Adopt ISSUE-105 canvas-usemap Change Proposal to add usemap attribute to the canvas element
- Re: <figure> bugs in Differences document
- ISSUE-88: content-language-multiple - Straw Poll for Objections
- ISSUE-30: longdesc - Straw Poll for Objections
- Re: WG Decision: Publish six heartbeat drafts, as well as Polyglot, Alt Techniques as FPWDs
- Re: WG Decision: Publish six heartbeat drafts, as well as Polyglot, Alt Techniques as FPWDs
- ISSUE-74 canvas-accessibility - Chairs Solicit Alternate Proposals or Counter-Proposals
- ISSUE-32 table-summary - Chairs Solicit Alternate Proposals or Counter-Proposals
- Re: CfC: Adopt ISSUE-101 us-ascii-ref Change Proposal to replace ASCII reference
- Re: CfC: Adopt ISSUE-107 plugin-fallback-example Change Proposal to replace <object> fallback example
- Re: ISSUE-85 anchor-roles partial Change Proposal
- Re: CfC: Adopt ISSUE-101 us-ascii-ref Change Proposal to replace ASCII reference
- Re: CfC: Adopt ISSUE-101 us-ascii-ref Change Proposal to replace ASCII reference
- Re: Differences between the W3C and WHATWG specifications
- Re: CfC: Adopt ISSUE-101 us-ascii-ref Change Proposal to replace ASCII reference
- Re: Issue 100 Zero-Edits Counter Proposal
- Re: ISSUE-85 anchor-roles partial Change Proposal
- Re: Change proposal for ISSUE-56
- Re: Null change proposal for ISSUE-80
- Re: Null change proposal for ISSUE-31
- Re: ISSUE-31 Change Proposal
- Re: WG Decision: Publish six heartbeat drafts, as well as Polyglot, Alt Techniques as FPWDs
- Re: <figure> bugs in Differences document
- Re: WG Decision: Publish six heartbeat drafts, as well as Polyglot, Alt Techniques as FPWDs
- Re: CfC: Adopt ISSUE-105 canvas-usemap Change Proposal to add usemap attribute to the canvas element
- Re: WG Decision: Publish six heartbeat drafts, as well as Polyglot, Alt Techniques as FPWDs
- Re: CfC: Adopt ISSUE-105 canvas-usemap Change Proposal to add usemap attribute to the canvas element
- Re: CfC: Adopt ISSUE-105 canvas-usemap Change Proposal to add usemap attribute to the canvas element
- Re: WG Decision: Publish six heartbeat drafts, as well as Polyglot, Alt Techniques as FPWDs
- Re: CfC: Adopt ISSUE-105 canvas-usemap Change Proposal to add usemap attribute to the canvas element
- Re: <figure> bugs in Differences document
- Re: WG Decision: Publish six heartbeat drafts, as well as Polyglot, Alt Techniques as FPWDs
Tuesday, 22 June 2010
- Re: How to parse </foo </bar>
- Re: Insertion point for script@onload
- How to parse </foo </bar>
- Re: WG Decision: Publish six heartbeat drafts, as well as Polyglot, Alt Techniques as FPWDs
- Re: WG Decision: Publish six heartbeat drafts, as well as Polyglot, Alt Techniques as FPWDs
- Re: WG Decision: Publish six heartbeat drafts, as well as Polyglot, Alt Techniques as FPWDs
- Re: WG Decision: Publish six heartbeat drafts, as well as Polyglot, Alt Techniques as FPWDs
- Re: Insertion point for script@onload
- Re: HTML5 Profiles - First Editors Draft
- Re: Insertion point for script@onload
- Bug 9241 (was Re: Differences between the W3C and WHATWG specifications)
- Insertion point for script@onload
- Re: Differences between the W3C and WHATWG specifications
- Re: Differences between the W3C and WHATWG specifications
- Re: Differences between the W3C and WHATWG specifications
- Re: Differences between the W3C and WHATWG specifications
- Re: Differences between the W3C and WHATWG specifications
- Re: Differences between the W3C and WHATWG specifications
Monday, 21 June 2010
- Re: Differences between the W3C and WHATWG specifications
- Polyglot Guidance for HTML5 Foreign Content Exceptions
- RE: Adopt ISSUE-105 canvas-usemap Change Proposal to add usemap attribute to the canvas element
- Re: Differences between the W3C and WHATWG specifications
- Re: Differences between the W3C and WHATWG specifications
- Re: Differences between the W3C and WHATWG specifications
Sunday, 20 June 2010
- Re: Differences between the W3C and WHATWG specifications
- Re: Notes on the draft polyglot document Polyglot document
- Re: Differences between the W3C and WHATWG specifications
- RE: Notes on the draft polyglot document Polyglot document
- Re: Differences between the W3C and WHATWG specifications
Friday, 18 June 2010
- Re: some conformance questions
- Re: Differences between the W3C and WHATWG specifications
- Re: Differences between the W3C and WHATWG specifications
- Re: Differences between the W3C and WHATWG specifications
- Re: some conformance questions
- Re: Differences between the W3C and WHATWG specifications
- Re: Differences between the W3C and WHATWG specifications
- Re: Notes on the draft polyglot document Polyglot document
- Re: some conformance questions
- Re: table layout conformance (was: some conformance questions)
- Re: some conformance questions
- Re: some conformance questions
- Re: Notes on the draft polyglot document Polyglot document
- Re: table layout conformance
- Re: some conformance questions
- RE: Notes on the draft polyglot document Polyglot document
- Re: some conformance questions
- Re: Differences between the W3C and WHATWG specifications
- Re: some conformance questions
Thursday, 17 June 2010
- Developer and Public Editions Re: Differences between the W3C and WHATWG specifications
- Re: table layout conformance (was: some conformance questions)
- Re: Change proposal for ISSUE-85
- Re: Change proposal for ISSUE-85
- Re: Differences between the W3C and WHATWG specifications
- Re: Differences between the W3C and WHATWG specifications
- RE: Notes on the draft polyglot document Polyglot document
- RE: Notes on the draft polyglot document Polyglot document
- Re: Change proposal for ISSUE-85
- Re: Change proposal for ISSUE-85
- Re: table layout conformance
- Re: table layout conformance (was: some conformance questions)
- Re: table layout conformance (was: some conformance questions)
- table layout conformance (was: some conformance questions)
- Re: some conformance questions
- [Bug 9872] trigger a conformance error when javascript is included in href attribute
- [Bug 9871] provide normative advice to conformance checkers about use of onevent handler attributes
- Re: some conformance questions
- Re: some conformance questions
- Re: some conformance questions
- Re: Change proposal for ISSUE-85
- Re: some conformance questions
- Re: some conformance questions
- Re: some conformance questions
- Re: some conformance questions
- Re: some conformance questions
- Re: some conformance questions
- Re: Change proposal for ISSUE-85
- Re: Differences between the W3C and WHATWG specifications
- Re: Differences between the W3C and WHATWG specifications
- Re: Change proposal for ISSUE-85
- Re: Change proposal for ISSUE-85
- Re: Change proposal for ISSUE-85
- Re: some conformance questions
- Re: Change proposal for ISSUE-85
- Re: Differences between the W3C and WHATWG specifications
- Re: some conformance questions
- Re: some conformance questions
- Re: some conformance questions
- Re: some conformance questions
- Re: Differences between the W3C and WHATWG specifications
- Re: some conformance questions
- Re: Change proposal for ISSUE-85
- Re: Change proposal for ISSUE-85
- Re: some conformance questions
- Re: Differences between the W3C and WHATWG specifications
- Re: Change proposal for ISSUE-85
- some conformance questions
- Re: Change proposal for ISSUE-85
- Re: Change proposal for ISSUE-85
- Re: Change proposal for ISSUE-85
Wednesday, 16 June 2010
- Re: Change proposal for ISSUE-85
- Re: Change proposal for ISSUE-85
- Re: Change proposal for ISSUE-85
- Re: Change proposal for ISSUE-85
- Re: Change proposal for ISSUE-85
- Re: Change proposal for ISSUE-85
- Re: Change proposal for ISSUE-85
- Re: Change proposal for ISSUE-85
- RE: HTML WG F2F meeting, Nov 4-5 at TPAC 2010, Lyon, France
- Re: Change proposal for ISSUE-85
- [Bug 9936] onclick attributes on any element that is not focusable should trigger a conformance error
- Re: Change proposal for ISSUE-85
- Re: Change proposal for ISSUE-85
- Re: HTML-A11Y Task Force Recommendation: ISSUE-74 Canvas-Accessibility
- Re: Change proposal for ISSUE-85
- Re: Change proposal for ISSUE-85
- Re: Change proposal for ISSUE-85
- Re: Change proposal for ISSUE-85
- Re: Change proposal for ISSUE-85
- Re: Change proposal for ISSUE-85
- Objectionism (Was: Change proposal for ISSUE-85)
- Re: Change proposal for ISSUE-85
- Re: Change proposal for ISSUE-85
- Re: Change proposal for ISSUE-85
- Re: Change proposal for ISSUE-85
- Re: Change proposal for ISSUE-85
- Re: Change proposal for ISSUE-56
- Re: Change proposal for ISSUE-85
- Re: Change proposal for ISSUE-85
- ISSUE-105 (was Re: Change Proposals, objections, and the Decision Policy)
- Re: Change Proposals, objections, and the Decision Policy
- Re: CfC: Adopt ISSUE-101 us-ascii-ref Change Proposal to replace ASCII reference
- Re: Change Proposals, objections, and the Decision Policy
- Re: Change proposal for ISSUE-56
- Re: Change Proposals, objections, and the Decision Policy
- Re: Change Proposals, objections, and the Decision Policy
- Re: Change Proposals, objections, and the Decision Policy
- Re: Change proposal for ISSUE-85
- Re: Change Proposals, objections, and the Decision Policy
- Re: Change proposal for ISSUE-56
- Re: CfC: Adopt ISSUE-101 us-ascii-ref Change Proposal to replace ASCII reference
- Re: CfC: Adopt ISSUE-101 us-ascii-ref Change Proposal to replace ASCII reference
- Re: Change Proposals, objections, and the Decision Policy
- Re: Change proposal for ISSUE-56
- Re: Change proposal for ISSUE-85
- Re: Change proposal for ISSUE-85
- Change proposal for ISSUE-56
- Re: Change proposal for ISSUE-85
- Change proposal for ISSUE-85
- Re: Change proposal for ISSUE-85
- Re: Change proposal for ISSUE-85
- Re: CfC: Adopt ISSUE-101 us-ascii-ref Change Proposal to replace ASCII reference
- Re: Change proposal for ISSUE-85
- Re: Change proposal for ISSUE-85
- Re: Change proposal for ISSUE-85
- Re: Change proposal for ISSUE-85
Tuesday, 15 June 2010
- Re: Change Proposals, objections, and the Decision Policy
- Re: CfC: Adopt ISSUE-101 us-ascii-ref Change Proposal to replace ASCII reference
- Re: Differences between the W3C and WHATWG specifications
- Re: CfC: Adopt ISSUE-101 us-ascii-ref Change Proposal to replace ASCII reference
- Re: CfC: Adopt ISSUE-101 us-ascii-ref Change Proposal to replace ASCII reference
- Re: CfC: Adopt ISSUE-101 us-ascii-ref Change Proposal to replace ASCII reference
- Re: CfC: Adopt ISSUE-101 us-ascii-ref Change Proposal to replace ASCII reference
- Re: CfC: Adopt ISSUE-101 us-ascii-ref Change Proposal to replace ASCII reference
- Re: Change Proposals, objections, and the Decision Policy
- Re: Change proposal for ISSUE-85
- Re: Change proposal for ISSUE-85
- Re: CfC: Adopt ISSUE-101 us-ascii-ref Change Proposal to replace ASCII reference
- Re: CfC: Adopt ISSUE-101 us-ascii-ref Change Proposal to replace ASCII reference
- Re: ruby /ruby
- Re: CfC: Adopt ISSUE-101 us-ascii-ref Change Proposal to replace ASCII reference
- Re: Differences between the W3C and WHATWG specifications
- Re: CfC: Adopt ISSUE-101 us-ascii-ref Change Proposal to replace ASCII reference
- Re: CfC: Adopt ISSUE-101 us-ascii-ref Change Proposal to replace ASCII reference
- Re: CfC: Adopt ISSUE-101 us-ascii-ref Change Proposal to replace ASCII reference
- Re: CfC: Adopt ISSUE-101 us-ascii-ref Change Proposal to replace ASCII reference
- Re: CfC: Adopt ISSUE-101 us-ascii-ref Change Proposal to replace ASCII reference
- Re: Change Proposals, objections, and the Decision Policy
- Re: Change Proposals, objections, and the Decision Policy
- Re: CfC: Adopt ISSUE-101 us-ascii-ref Change Proposal to replace ASCII reference
- Re: Change Proposals, objections, and the Decision Policy
- RE: Change Proposals, objections, and the Decision Policy
- Re: CfC: Adopt ISSUE-105 canvas-usemap Change Proposal to add usemap attribute to the canvas element
- Re: Change Proposals, objections, and the Decision Policy
- Re: TAG requests addition to section 3.2.1 of Part 3 [#155]
- Re: ISSUE-109 aria-section-title - Chairs Solicit Alternate Proposals or Counter-Proposals
- ISSUE-109 aria-section-title - Chairs Solicit Alternate Proposals or Counter-Proposals
- CfC: Adopt ISSUE-107 plugin-fallback-example Change Proposal to replace <object> fallback example
- CfC: Adopt ISSUE-105 canvas-usemap Change Proposal to add usemap attribute to the canvas element
- CfC: Adopt ISSUE-101 us-ascii-ref Change Proposal to replace ASCII reference
- Re: Change Proposals, objections, and the Decision Policy
- Re: HTML-A11Y Task Force Recommendation: ISSUE-74 Canvas-Accessibility
- Re: Change Proposals, objections, and the Decision Policy
- Re: Change Proposals, objections, and the Decision Policy
- Re: Change Proposals, objections, and the Decision Policy
- Re: Change Proposals, objections, and the Decision Policy
- Re: Change Proposals, objections, and the Decision Policy
- Re: TAG requests addition to section 3.2.1 of Part 3 [#155]
- Re: Change Proposals, objections, and the Decision Policy
- Re: Change Proposals, objections, and the Decision Policy
- Re: Change Proposals, objections, and the Decision Policy
Monday, 14 June 2010
- Re: text/sandboxed-html
- Re: text/sandboxed-html
- RE: HTML-A11Y Task Force Recommendation: ISSUE-74 Canvas-Accessibility
- RE: HTML-A11Y Task Force Recommendation: ISSUE-74 Canvas-Accessibility
- HTML-A11Y Task Force Recommendation: ISSUE-74 Canvas-Accessibility
- Re: Change Proposals, objections, and the Decision Policy
- Change Proposals, objections, and the Decision Policy
- Re: Differences between the W3C and WHATWG specifications
- Re: Differences between the W3C and WHATWG specifications
- Re: Differences between the W3C and WHATWG specifications
- Re: Differences between the W3C and WHATWG specifications
Sunday, 13 June 2010
Saturday, 12 June 2010
- Re: Differences between the W3C and WHATWG specifications
- Re: Request for editing guidance
- Re: Differences between the W3C and WHATWG specifications
- Re: Request for editing guidance
- Re: Request for editing guidance
- Re: Request for editing guidance
- Re: Canvas drawImage question
- Re: Request for editing guidance
- Differences between the W3C and WHATWG specifications
Friday, 11 June 2010
- Re: Canvas drawImage question
- Re: Notes on the draft polyglot document Polyglot document
- Re: Notes on the draft polyglot document Polyglot document
- Re: Notes on the draft polyglot document Polyglot document
- Re: Notes on the draft polyglot document Polyglot document
- Re: Notes on the draft polyglot document Polyglot document
- Re: Notes on the draft polyglot document Polyglot document
- Re: Notes on the draft polyglot document Polyglot document
- Re: Canvas drawImage question
- Re: Canvas drawImage question
- Re: Canvas drawImage question
- Re: Canvas drawImage question
- Re: Canvas drawImage question
- Canvas drawImage question
- Re: [whatwg] ISSUE-86, Re: hixie: Remove the HTML-to-Atom mapping definition from the W3C version of the spec. (whatwg r5100)
- Re: Request to halt the heartbeat publication of HTML5 WG Draft
- Re: Notes on the draft polyglot document Polyglot document
- Re: Notes on the draft polyglot document Polyglot document
- Re: Request for editing guidance
- Re: Request for editing guidance
- Re: Request for editing guidance
- Re: Request for editing guidance
- Re: text/sandboxed-html
- Re: text/sandboxed-html
Thursday, 10 June 2010
- Re: text/sandboxed-html
- Re: Request for editing guidance
- Re: Request for editing guidance
- Re: Request for editing guidance
- Re: Request for editing guidance
- Re: Request for editing guidance
- Re: text/sandboxed-html
- Re: text/sandboxed-html
- Re: Request for editing guidance
- Re: Request for editing guidance
- Re: text/sandboxed-html
- Re: text/sandboxed-html
- Re: Request for editing guidance
- {minutes} HTML WG telecon 2010-06-10: action items, decision policy, task force reports, publication status
- Re: Notes on the draft polyglot document Polyglot document
- Re: Request to halt the heartbeat publication of HTML5 WG Draft
- Re: Request for editing guidance
- Re: Notes on the draft polyglot document Polyglot document
- Re: Request to halt the heartbeat publication of HTML5 WG Draft
- Re: Notes on the draft polyglot document Polyglot document
- Re: Notes on the draft polyglot document Polyglot document
- Re: Notes on the draft polyglot document Polyglot document
- Re: Request to halt the heartbeat publication of HTML5 WG Draft
- Re: Notes on the draft polyglot document Polyglot document
- Re: provide reference and info about HTML5: Techniques for providing useful text alternatives in html5 spec
- Re: Notes on the draft polyglot document Polyglot document
- Re: Notes on the draft polyglot document Polyglot document
- Re: Notes on the draft polyglot document Polyglot document
- Re: Notes on the draft polyglot document Polyglot document
- Re: Notes on the draft polyglot document Polyglot document
- Re: Notes on the draft polyglot document Polyglot document
- RE: Request for editing guidance
- Re: Notes on the draft polyglot document Polyglot document
- FW: {agenda} HTML WG telecon 2010-06-10: action items, decision policy, task force reports, publication status
- Re: Notes on the draft polyglot document Polyglot document
- Re: Notes on the draft polyglot document Polyglot document
Wednesday, 9 June 2010
- Re: TAG requests addition to section 3.2.1 of Part 3 [#155]
- Re: Notes on the draft polyglot document Polyglot document
- IETF BoF @IETF-78 Maastricht: HASMAT - HTTP Application Security Minus Authentication and Transport
- Re: Request for editing guidance
- Re: Request for editing guidance
- Re: Request for editing guidance
- Re: Request for editing guidance
- Re: Request to halt the heartbeat publication of HTML5 WG Draft
- Re: Request for editing guidance
- Re: Request for editing guidance
- Re: Request for editing guidance
- Re: Request for editing guidance
- Re: Request for editing guidance
- Re: Request for editing guidance
- RE: Request for editing guidance
- Re: Request for editing guidance
- Re: Request for editing guidance
- Re: Request for editing guidance
- Re: Request for editing guidance
- Re: Request for editing guidance
- Re: Request for editing guidance
- OFF TOPIC: SVG Progress Contest
- Re: Notes on the draft polyglot document Polyglot document
- Re: Notes on the draft polyglot document Polyglot document
- Re: TAG requests addition to section 3.2.1 of Part 3 [#155]
- Re: Request for editing guidance
- Re: Request for editing guidance
- Re: Request for editing guidance
- Re: Notes on the draft polyglot document Polyglot document
- Re: Notes on the draft polyglot document Polyglot document
- Re: Request for editing guidance
- Notes on the draft polyglot document Polyglot document
- <figure> bugs in Differences document
- Re: Request for editing guidance
- RE: Request to halt the heartbeat publication of HTML5 WG Draft
- Last Call Working Drafts transition announcement of the API and Ontology for Media Resource 1.0
- Re: preparing WG publication
- Re: Request to halt the heartbeat publication of HTML5 WG Draft
- Request for editing guidance
- Re: Request to halt the heartbeat publication of HTML5 WG Draft
- Re: Request to halt the heartbeat publication of HTML5 WG Draft
- Request to halt the heartbeat publication of HTML5 WG Draft
Tuesday, 8 June 2010
- Re: provide reference and info about HTML5: Techniques for providing useful text alternatives in html5 spec
- RE: preparing WG publication
- Re: provide reference and info about HTML5: Techniques for providing useful text alternatives in html5 spec
- Re: preparing WG publication
- Re: preparing WG publication
- RE: preparing WG publication
- Re: preparing WG publication
- Re: aside and figure elements
- Re: aside and figure elements
- RE: preparing WG publication
- RE: preparing WD publication
- Re: preparing WG publication
- Re: aside and figure elements
- RE: aside and figure elements
- RE: aside and figure elements
- Re: preparing WG publication
- Re: preparing WD publication
- Re: preparing WG publication
- provide reference and info about HTML5: Techniques for providing useful text alternatives in html5 spec
- RE: aside and figure elements
- preparing WD publication
- Re: preparing WG publication
- Re: preparing WG publication
- RE: aside and figure elements
- Re: preparing WG publication
- preparing WG publication
- Re: aside and figure elements
- Re: aside and figure elements
- HTML5, Forms issue
- [Bug 9876] Clarify that a figure can be any content with a caption
- Re: aside and figure elements
- RE: aside and figure elements
- Re: use of figure/figcaption
- Re: use of figure/figcaption
- Re: use of figure/figcaption
- RE: aside and figure elements
- Re: aside and figure elements
- Re: use of figure/figcaption
- Re: use of figure/figcaption
- Re: aside and figure elements
- Re: aside and figure elements
- use of figure/figcaption
- Re: aside and figure elements
- Re: aside and figure elements
- Re: aside and figure elements
- Re: aside and figure elements
Monday, 7 June 2010
- Re: aside and figure elements
- Re: aside and figure elements
- Re: aside and figure elements
- Re: aside and figure elements
- Re: aside and figure elements
- Re: aside and figure elements
- Re: aside and figure elements
- Re: aside and figure elements
- Re: aside and figure elements
- Re: aside and figure elements
- Re: aside and figure elements
- Re: aside and figure elements
- Re: aside and figure elements
- Re: aside and figure elements
- Re: aside and figure elements
- Re: aside and figure elements
- Re: aside and figure elements
- Re: aside and figure elements
- Re: aside and figure elements
- Re: aside and figure elements
- Re: aside and figure elements
- Re: aside and figure elements
- Re: aside and figure elements
- Re: aside and figure elements
- RE: Working Group Decision on ISSUE-91: Removing the aside Element
- RE: Working Group Decision on ISSUE-91: Removing the aside Element
- Re: aside and figure elements
- Re: Working Group Decision on ISSUE-91: Removing the aside Element
- Re: aside and figure elements
- Re: Working Group Decision on ISSUE-91: Removing the aside Element
- Re: Working Group Decision on ISSUE-91: Removing the aside Element
- Re: aside and figure elements
- Re: aside and figure elements
- Re: aside and figure elements
- Re: aside and figure elements
- Re: aside and figure elements
- Re: aside and figure elements
- Re: aside and figure elements
- Re: aside and figure elements
- Re: aside and figure elements
- Re: aside and figure elements
- Re: aside and figure elements
- Re: aside and figure elements
- Re: aside and figure elements
- Re: aside and figure elements
- Re: aside and figure elements
- Re: aside and figure elements
- Re: aside and figure elements
- Re: aside and figure elements
- Re: aside and figure elements
- Re: aside and figure elements
- Re: aside and figure elements
- Re: aside and figure elements
- Re: aside and figure elements
- Re: aside and figure elements
- Re: aside and figure elements
- Re: Change proposal for ISSUE-85
- [Bug 9872] trigger a conformance error when javascript is included in href attribute
- Re: Change proposal for ISSUE-85
Sunday, 6 June 2010
- Re: Change proposal for ISSUE-85
- Re: Change proposal for ISSUE-85
- Re: aside and figure elements
- Re: Change proposal for ISSUE-85
- Re: Change proposal for ISSUE-85
- Re: Change proposal for ISSUE-85
- Re: aside and figure elements
- Re: Change proposal for ISSUE-85
- Re: aside and figure elements
- Re: Change proposal for ISSUE-103
- Change proposal for ISSUE-85
- Change proposal for ISSUE-103
Saturday, 5 June 2010
- RE: Working Group Decision on ISSUE-91: Removing the aside Element
- aside and figure elements
- Re: [whatwg] ISSUE-86, Re: hixie: Remove the HTML-to-Atom mapping definition from the W3C version of the spec. (whatwg r5100)
- RE: Working Group Decision on ISSUE-91: Removing the aside Element
Friday, 4 June 2010
- Re: Working Group Decision on ISSUE-91: Removing the aside Element
- Re: Working Group Decision on ISSUE-91: Removing the aside Element
- RE: Working Group Decision on ISSUE-91: Removing the aside Element
- Re: Working Group Decision on ISSUE-91: Removing the aside Element
- RE: Working Group Decision on ISSUE-91: Removing the aside Element
- Re: Working Group Decision on ISSUE-91: Removing the aside Element
- RE: Working Group Decision on ISSUE-91: Removing the aside Element
- Re: Working Group Decision on ISSUE-91: Removing the aside Element
- RE: Working Group Decision on ISSUE-91: Removing the aside Element
- RE: Working Group Decision on ISSUE-91: Removing the aside Element
- Re: text/sandboxed-html
- Re: Working Group Decision on ISSUE-91: Removing the aside Element
- Re: text/sandboxed-html
- Re: text/sandboxed-html
- Re: text/sandboxed-html
- Re: Working Group Decision on ISSUE-91: Removing the aside Element
- Re: Working Group Decision on ISSUE-91: Removing the aside Element
- Re: text/sandboxed-html
- Re: Working Group Decision on ISSUE-91: Removing the aside Element
- Re: Working Group Decision on ISSUE-66 - Image Analysis Heuristics
- Re: Working Group Decision on ISSUE-66 - Image Analysis Heuristics
- Re: ISSUE-89 idioms - Chairs Solicit Alternate Proposals or Counter-Proposals
- Re: ISSUE-89 idioms - Chairs Solicit Alternate Proposals or Counter-Proposals
- [Bug 9835] Remove image analysis
- Re: WG Decision: Publish six heartbeat drafts, as well as Polyglot, Alt Techniques as FPWDs
- RE: text/sandboxed-html
Thursday, 3 June 2010
- Re: text/sandboxed-html
- Re: text/sandboxed-html
- Re: text/sandboxed-html
- [css2.1] handling of U+0000 - match html5?
- Re: Change proposals and objections:
- Re: WG Decision: Publish six heartbeat drafts, as well as Polyglot, Alt Techniques as FPWDs
- Re: Change proposals and objections: (was: Working Group Decision)
- Re: text/sandboxed-html
- Re: text/sandboxed-html
- Re: ISSUE-115 (rel-canonical-human): Chairs Solicit Proposals
- Re: ISSUE-114 (rel-canonical-organization): Chairs Solicit Proposals
- Re: ISSUE-112 (meta-keywords-not): Chairs Solicit Proposals
- Re: ISSUE-113 (forced-fragment): Chairs Solicit Proposals
- Re: ISSUE-111 (checkbox-required): Chairs Solicit Proposals
- [minutes] HTML WG 20100603
- Re: text/sandboxed-html
- Re: Working Group Decision on ISSUE-91: Removing the aside Element
- [Bug 9775] "positioned to a multiple of the line dimensions of the first line of the cue" - enforcing the same line height for every line ihurts text rendering appearance for no apparent reason. This is especially true if text styling is supported (bold text is larg
- [Bug 9774] "consecutive lines displayed below each other" - since subtitles tend to be rendered at the bottom, it's actually better for new subtitles to be rendered higher up. Of course, the individual lines of each subtitle still extend downwards, but it's still po
- [Bug 9773] There is not a clear difference between "subtitles" and "captions". These are mostly used to describe "closed captions" (binary transmissions in TV broadcasts) vs "subtitles" (text files), as far as I know.
- Re: text/sandboxed-html
- [Bug 9817] Details element Focus problem
- Re: Working Group Decision on ISSUE-91: Removing the aside Element
- Re: Working Group Decision on ISSUE-91: Removing the aside Element
- Re: Working Group Decision on ISSUE-91: Removing the aside Element
- Re: WG Decision: Publish six heartbeat drafts, as well as Polyglot, Alt Techniques as FPWDs
- Re: Working Group Decision on ISSUE-91: Removing the aside Element
- Re: Working Group Decision on ISSUE-91: Removing the aside Element
- Re: Working Group Decision on ISSUE-91: Removing the aside Element
- Re: WG Decision: Publish six heartbeat drafts, as well as Polyglot, Alt Techniques as FPWDs
- Re: Working Group Decision on ISSUE-66 - Image Analysis Heuristics
- Re: Working Group Decision on ISSUE-91: Removing the aside Element
- Re: Working Group Decision on ISSUE-91: Removing the aside Element
- Re: WG Decision: Publish six heartbeat drafts, as well as Polyglot, Alt Techniques as FPWDs
Wednesday, 2 June 2010
- Re: WG Decision: Publish six heartbeat drafts, as well as Polyglot, Alt Techniques as FPWDs
- Re: Working Group Decision on ISSUE-91: Removing the aside Element
- [Bug 9835] Remove image analysis
- Re: WG Decision: Publish six heartbeat drafts, as well as Polyglot, Alt Techniques as FPWDs
- Re: WG Decision: Publish six heartbeat drafts, as well as Polyglot, Alt Techniques as FPWDs
- WG Decision: Publish six heartbeat drafts, as well as Polyglot, Alt Techniques as FPWDs
- Re: Working Group Decision on ISSUE-91: Removing the aside Element
- Change proposals and objections: (was: Working Group Decision)
- Reminder: Seeking comments on LCWDs of Server-events, Web Storage, Web Workers; deadline 30-June-2010
- Re: Working Group Decision on ISSUE-91: Removing the aside Element
- Re: Working Group Decision on ISSUE-91: Removing the aside Element
- ISSUE-86, Re: hixie: Remove the HTML-to-Atom mapping definition from the W3C version of the spec. (whatwg r5100)
- Re: CfC: Adopt ISSUE-86 Change Proposal to remove Atom conversion
- Re: Working Group Decision on ISSUE-91: Removing the aside Element
- Re: Working Group Decision on ISSUE-91: Removing the aside Element
- Re: Working Group Decision on ISSUE-91: Removing the aside Element
- Re: Working Group Decision on ISSUE-91: Removing the aside Element
- Re: Working Group Decision on ISSUE-91: Removing the aside Element
- Re: Working Group Decision on ISSUE-91: Removing the aside Element
- Re: Working Group Decision on ISSUE-91: Removing the aside Element
- Re: Working Group Decision on ISSUE-91: Removing the aside Element
- Re: Working Group Decision on ISSUE-91: Removing the aside Element
- Re: Working Group Decision on ISSUE-91: Removing the aside Element
- Re: Working Group Decision on ISSUE-90: Removing the figure Element
- Re: Working Group Decision on ISSUE-91: Removing the aside Element
Tuesday, 1 June 2010
- Re: Working Group Decision on ISSUE-91: Removing the aside Element
- RE: Working Group Decision on ISSUE-66 - Image Analysis Heuristics
- Re: Working Group Decision on ISSUE-91: Removing the aside Element
- Re: Working Group Decision on ISSUE-66 - Image Analysis Heuristics
- RE: Working Group Decision on ISSUE-66 - Image Analysis Heuristics
- Working Group Decision on ISSUE-91: Removing the aside Element
- Working Group Decision on ISSUE-90: Removing the figure Element
- Working Group Decision on ISSUE-66 - Image Analysis Heuristics
- Re: CfC: Adopt ISSUE-86 Change Proposal to remove Atom conversion