Thursday, 31 December 2009
- Re: Public feedback on HTML5 video
- Re: Public feedback on HTML5 video
- Re: Public feedback on HTML5 video
- Re: Public feedback on HTML5 video
- Re: Public feedback on HTML5 video
- Re: Public feedback on HTML5 video
- Re: Public feedback on HTML5 video
- Re: Public feedback on HTML5 video
- Re: Public feedback on HTML5 video
- Re: Public feedback on HTML5 video
- Re: Public feedback on HTML5 video
Wednesday, 30 December 2009
- Re: Public feedback on HTML5 video
- Re: AW: Public feedback on HTML5 video
- Re: Public feedback on HTML5 video
- Re: Public feedback on HTML5 video
- Re: ISSUE-27: rel-ownership - Chairs Solicit Proposals
- Re: Public feedback on HTML5 video
- Re: ISSUE-27: rel-ownership - Chairs Solicit Proposals
- Re: Public feedback on HTML5 video
- Re: AW: Public feedback on HTML5 video
- Re: Public feedback on HTML5 video
- Re: ISSUE-27: rel-ownership - Chairs Solicit Proposals
Tuesday, 29 December 2009
- Re: Public feedback on HTML5 video
- Re: ISSUE-27: rel-ownership - Chairs Solicit Proposals
- Re: ISSUE-27: rel-ownership - Chairs Solicit Proposals
- Re: ISSUE-27: rel-ownership - Chairs Solicit Proposals
- Re: AW: Public feedback on HTML5 video
- Re: Public feedback on HTML5 video
- Re: Public feedback on HTML5 video
- Re: Public feedback on HTML5 video
- Re: Public feedback on HTML5 video
- Re: Public feedback on HTML5 video
- Re: Public feedback on HTML5 video
- Re: Public feedback on HTML5 video
- Re: Public feedback on HTML5 video
- Re: Public feedback on HTML5 video
- Re: AW: Public feedback on HTML5 video
- Re: Public feedback on HTML5 video
- RE: Public feedback on HTML5 video
- Re: Public feedback on HTML5 video
- Re: Public feedback on HTML5 video
- Re: Public feedback on HTML5 video
- Re: Public feedback on HTML5 video
- Re: AW: Public feedback on HTML5 video
- Re: Public feedback on HTML5 video
- Re: AW: Public feedback on HTML5 video
- Re: Public feedback on HTML5 video
- RE: Public feedback on HTML5 video
- Re: Public feedback on HTML5 video
Monday, 28 December 2009
- Re: Public feedback on HTML5 video
- Re: AW: Public feedback on HTML5 video
- Re: AW: Public feedback on HTML5 video
- Re: AW: Public feedback on HTML5 video
- Re: AW: Public feedback on HTML5 video
- Re: Public feedback on HTML5 video
- AW: Public feedback on HTML5 video
- AW: Public feedback on HTML5 video
- Re: Public feedback on HTML5 video
- Re: Public feedback on HTML5 video
- Re: Public feedback on HTML5 video
- Re: Public feedback on HTML5 video
- Re: Public feedback on HTML5 video
- Re: Public feedback on HTML5 video
- Re: Public feedback on HTML5 video
- RE: Public feedback on HTML5 video
- Re: Public feedback on HTML5 video
- RE: Public feedback on HTML5 video
- Re: Public feedback on HTML5 video
- Re: Public feedback on HTML5 video
- Re: Public feedback on HTML5 video
- RE: Public feedback on HTML5 video
Sunday, 27 December 2009
Saturday, 26 December 2009
Friday, 25 December 2009
Thursday, 24 December 2009
- Re: Public feedback on HTML5 video
- Re: Public feedback on HTML5 video
- Re: Public feedback on HTML5 video
- Re: Public feedback on HTML5 video
- Re: Public feedback on HTML5 video
- Re: Public feedback on HTML5 video
- Re: Public feedback on HTML5 video
- Re: Public feedback on HTML5 video
- Re: Public feedback on HTML5 video
- Re: Public feedback on HTML5 video
- Re: Public feedback on HTML5 video
Tuesday, 22 December 2009
- Re: Public feedback on HTML5 video
- Re: Public feedback on HTML5 video
- Re: Public feedback on HTML5 video
- Re: Public feedback on HTML5 video
- Re: Public feedback on HTML5 video
- Public feedback on HTML5 video
Friday, 18 December 2009
- Re: Comments about the ACTION-165 draft
- Comments about the ACTION-165 draft
- Re: ISSUE-30 (Longdesc) Change Proposal
- minutes: html5 a11y task force canvas sub group telecon minutes 2009-12-17 [draft]
Thursday, 17 December 2009
- Re: ISSUE-30 (Longdesc) Change Proposal
- Re: ISSUE-30 (Longdesc) Change Proposal
- Re: ISSUE-30 (Longdesc) Change Proposal
- Re: ACTION-133: Develop an accessibility API and model for canvas as well as attributes to specify alternative content
- Re: FW: ACTION-133: Develop an accessibility API and model for canvas as well as attributes to specify alternative content
- Re: FW: ACTION-133: Develop an accessibility API and model for canvas as well as attributes to specify alternative content
- Re: ISSUE-30 (Longdesc) Change Proposal
- Re: ISSUE-30 (Longdesc) Change Proposal
- FW: ACTION-133: Develop an accessibility API and model for canvas as well as attributes to specify alternative content
- Re: CHANGE PROPOSAL: Remove ping and hyperlink auditing (ISSUE-1 and ISSUE-2)
- Re: CHANGE PROPOSAL: Remove ping and hyperlink auditing (ISSUE-1 and ISSUE-2)
- Re: ISSUE-27: rel-ownership - Chairs Solicit Proposals
Wednesday, 16 December 2009
- Re: ISSUE-27: rel-ownership - Chairs Solicit Proposals
- Re: ISSUE-27: rel-ownership - Chairs Solicit Proposals
- Re: WebGL | The 3D Canvas Context for HTML
- Re: ISSUE-76: If we fixed namespaces, does RDFa still have problems?
- Re: X3D comments in Bug 8238.
- Re: ISSUE-27: rel-ownership - Chairs Solicit Proposals
- RE: ISSUE-76: If we fixed namespaces, does RDFa still have problems?
Tuesday, 15 December 2009
- {agenda} HTML WG telcon 2009-12-17: action items, calls for consensus/proposals, task forces
- Minutes HTML WG 10 December 2009
- Re: ISSUE-76: If we fixed namespaces, does RDFa still have problems?
- Re: http content type authoritative for object data?
- Re: ISSUE-27: rel-ownership - Chairs Solicit Proposals
- Re: CfC: Close ISSUE-67 h:tml-parsing-dom - extended to 2010-01-07
- Re: CfC: Close ISSUE-59 normative-language-reference extended to 2010-01-07
- RE: ISSUE-27: rel-ownership - Chairs Solicit Proposals
- Re: ISSUE-76: If we fixed namespaces, does RDFa still have problems?
- Re: http content type authoritative for object data?
- Selectedness when adding options (was: Re: Setting selectedIndex before adding option with that index)
- Re: Setting selectedIndex before adding option with that index
- Re: ISSUE-76: If we fixed namespaces, does RDFa still have problems?
- RE: ISSUE-76: If we fixed namespaces, does RDFa still have problems?
- RE: ISSUE-76: If we fixed namespaces, does RDFa still have problems?
- Re: http content type authoritative for object data?
Monday, 14 December 2009
- Re: ISSUE-76: If we fixed namespaces, does RDFa still have problems?
- RE: ISSUE-76: If we fixed namespaces, does RDFa still have problems?
- RE: ISSUE-76: If we fixed namespaces, does RDFa still have problems?
- RE: ISSUE-76: If we fixed namespaces, does RDFa still have problems?
- RE: ISSUE-76: If we fixed namespaces, does RDFa still have problems?
- RE: ISSUE-76: If we fixed namespaces, does RDFa still have problems?
- Re: ISSUE-76: If we fixed namespaces, does RDFa still have problems?
- Re: ISSUE-76: If we fixed namespaces, does RDFa still have problems?
- Re: ISSUE-76: If we fixed namespaces, does RDFa still have problems?
- Re: ISSUE-76: If we fixed namespaces, does RDFa still have problems?
- Re: ISSUE-76: If we fixed namespaces, does RDFa still have problems?
- Re: ISSUE-76: If we fixed namespaces, does RDFa still have problems?
- Re: ISSUE-76: If we fixed namespaces, does RDFa still have problems?
Sunday, 13 December 2009
- Re: http content type authoritative for object data?
- Re: http content type authoritative for object data?
- Re: http content type authoritative for object data?
- Re: HTML WG issues scheduled to close Dec 17 comments
- HTML WG issues scheduled to close Dec 17 comments
Saturday, 12 December 2009
- New UI for HTML5 Table Inspector
- Re: http content type authoritative for object data?
- Re: DOCTYPE versioning change proposal (ISSUE-4)
- Re: HTML CHANGE PROPOSAL; change definition of URL to normative reference to IRIBIS
- RE: DOCTYPE versioning change proposal (ISSUE-4)
- RE: HTML CHANGE PROPOSAL; change definition of URL to normative reference to IRIBIS
- RE: ISSUE-76: If we fixed namespaces, does RDFa still have problems?
- RE: ISSUE-76: If we fixed namespaces, does RDFa still have problems?
Friday, 11 December 2009
- Re: ISSUE-76: If we fixed namespaces, does RDFa still have problems?
- Re: WebGL | The 3D Canvas Context for HTML
- Re: ISSUE-76: Need feedback on splitting Microdata into separate specification
- RE: ISSUE-76: If we fixed namespaces, does RDFa still have problems?
- Re: http content type authoritative for object data?
- Features beyond HTML5
- Re: ISSUE-76: If we fixed namespaces, does RDFa still have problems?
- Re: ISSUE-76 - Microdata - Straw Poll for Objections
- Re: ISSUE-76 - Microdata - Straw Poll for Objections
- Re: ISSUE-76 - Microdata - Straw Poll for Objections
- Re: ISSUE-76: Need feedback on splitting Microdata into separate
- Re: ISSUE-76 - Microdata - Straw Poll for Objections
- [Bug 8450] Case insensitivity of @rel vs case sensitivity of URIs
- [Bug 8476] <canvas> contexts
- Re: http content type authoritative for object data?
- Re: WebGL | The 3D Canvas Context for HTML
- Re: ISSUE-76: If we fixed namespaces, does RDFa still have problems?
- Re: http content type authoritative for object data?
- Re: ISSUE-76: Need feedback on splitting Microdata into separate
- ISSUE-76: If we fixed namespaces, does RDFa still have problems?
Thursday, 10 December 2009
- WebGL | The 3D Canvas Context for HTML
- Re: X3D comments in Bug 8238.
- Re: http content type authoritative for object data?
- Re: ISSUE-76: Need feedback on splitting Microdata into separate
- Re: reasonable length of time before bugs in bugzilla database are addressed
- Re: reasonable length of time before bugs in bugzilla database are addressed
- Re: reasonable length of time before bugs in bugzilla database are addressed
- Re: reasonable length of time before bugs in bugzilla database are addressed
- Re: reasonable length of time before bugs in bugzilla database are addressed
- Re: reasonable length of time before bugs in bugzilla database are addressed
- ISSUE-76 - Microdata - Straw Poll for Objections
- Re: ISSUE-66: image-analysis - Chairs Solicit Proposals
- reasonable length of time before bugs in bugzilla database are addressed
- Re: ISSUE-76: Need feedback on splitting Microdata into separate
- Re: ISSUE-66: image-analysis - Chairs Solicit Proposals
- Re: ISSUE-76: Need feedback on splitting Microdata into separate
- Re: ISSUE-66: image-analysis - Chairs Solicit Proposals
- Re: ISSUE-76: Need feedback on splitting Microdata into separate specification
- Re: ISSUE-76: Need feedback on splitting Microdata into separate specification
- Re: http content type authoritative for object data?
- Re: http content type authoritative for object data?
- Re: http content type authoritative for object data?
- Re: ISSUE-76: Need feedback on splitting Microdata into separate specification
- Re: http content type authoritative for object data?
- Re: http content type authoritative for object data?
- Re: ISSUE-76: Need feedback on splitting Microdata into separate specification
- Re: ISSUE-76: Need feedback on splitting Microdata into separate specification
- Re: ISSUE-76: Need feedback on splitting Microdata into separate specification
- Re: ISSUE-74: canvas-accessibility - Chairs Solicit Proposals
- Re: ISSUE-76: Need feedback on splitting Microdata into separate specification
- Re: ISSUE-76: Need feedback on splitting Microdata into separate specification
- Re: http content type authoritative for object data?
- Re: ISSUE-76: Need feedback on splitting Microdata into separate specification
- Re: ISSUE-76: Need feedback on splitting Microdata into separate specification
- Re: http content type authoritative for object data?
- Re: ISSUE-76: Need feedback on splitting Microdata into separate specification
- Re: http content type authoritative for object data?
- Re: http content type authoritative for object data?
- Re: ISSUE-76: Need feedback on splitting Microdata into separate specification
- Re: Change Proposals and FPWD Resolutions
- Re: http content type authoritative for object data?
Wednesday, 9 December 2009
- ISSUE-76: CHANGE PROPOSAL (Draft 4): Separate Microdata from HTML5 Specification
- ISSUE-76: CHANGE PROPOSAL (Draft 3): Separate Microdata from HTML5 Specification
- Re: Change Proposals and FPWD Resolutions
- Re: Change Proposals and FPWD Resolutions
- Re: Change Proposals and FPWD Resolutions
- Re: Change Proposals and FPWD Resolutions
- Re: Change Proposals and FPWD Resolutions
- Re: ISSUE-83: dt-dd-semantics - Chairs Solicit Alternate Proposals or Counter-Proposals
- Re: ISSUE-83: dt-dd-semantics - Chairs Solicit Alternate Proposals or Counter-Proposals
- Re: Change Proposals and FPWD Resolutions
- Issues and Change Proposals Status list updated
- Re: ISSUE-74: canvas-accessibility - Chairs Solicit Proposals
- Re: ISSUE-63: origin-req-scope - Chairs Solicit Proposals
- Re: ISSUE-7: video-codecs - Chairs Solicit Proposals
- Re: Change Proposals and FPWD Resolutions
- Re: Change Proposals and FPWD Resolutions
- Re: ISSUE-83: dt-dd-semantics - Chairs Solicit Alternate Proposals or Counter-Proposals
- Re: Change Proposals and FPWD Resolutions
- Re: Change Proposals and FPWD Resolutions
- Re: Change Proposals and FPWD Resolutions
- Re: ISSUE-83: dt-dd-semantics - Chairs Solicit Alternate Proposals or Counter-Proposals
- Re: Change Proposals and FPWD Resolutions
- Re: Change Proposals and FPWD Resolutions
- Re: Change Proposals and FPWD Resolutions
- Re: Change Proposals and FPWD Resolutions
- Re: Change Proposals and FPWD Resolutions
- Re: Change Proposals and FPWD Resolutions
- Re: Change Proposals and FPWD Resolutions
- Re: Change Proposals and FPWD Resolutions
- Re: Change Proposals and FPWD Resolutions
- Re: Change Proposals and FPWD Resolutions
- Re: change proposal:modification to section 4.8.2.1 the img element
- Re: change proposal:modification to section 4.8.2.1 the img element
- Re: ISSUE-74: canvas-accessibility - Chairs Solicit Proposals
- Re: Ability to submit invalid forms
- Re: Ability to submit invalid forms
- Re: http content type authoritative for object data?
- Re: Ability to submit invalid forms
- Re: Inconsistent |typeof HTMLCanvasElement|
- Re: http content type authoritative for object data?
- ISSUE-74: canvas-accessibility - Chairs Solicit Proposals
- ISSUE-84: legacy-doctypes - Chairs Solicit Proposals
- ISSUE-83: dt-dd-semantics - Chairs Solicit Alternate Proposals or Counter-Proposals
- ISSUE-81: representation-vs-resource - Chairs Solicit Proposals
- ISSUE-66: image-analysis - Chairs Solicit Proposals
- ISSUE-79: meta-keywords - Chairs Solicit Proposals
- Re: Change Proposals and FPWD Resolutions
- ISSUE-76: CHANGE PROPOSAL (Draft 3): Separate Microdata from HTML5 Specification
- Re: ISSUE-76: Need feedback on splitting Microdata into separate specification
Tuesday, 8 December 2009
- CfC: Close ISSUE-73 predefined-voc (ends 2009-12-17)
- CfC: Close ISSUE-59 normative-language-reference (ends 2009-12-17)
- CfC: Close ISSUE-67 h:tml-parsing-dom (ends 2009-12-17)
- CfC: Close ISSUE-35 aria-processing (ends 2009-12-17)
- RE: ISSUE-76: Need feedback on splitting Microdata into separate specification
- Plan to resolve ISSUE-76 RDFa / Microdata
- Change Proposals and FPWD Resolutions
- Re: http content type authoritative for object data?
- Re: http content type authoritative for object data?
- Re: ISSUE-76: Need feedback on splitting Microdata into separate specification
- Re: Path forward on Microdata
- Re: HTML CHANGE PROPOSAL; change definition of URL to normative reference to IRIBIS
- Re: change proposal:modification to section 4.8.2.1 the img element
- Re: ISSUE-30 (Longdesc) Change Proposal
- Re: DOCTYPE versioning change proposal (ISSUE-4)
- Re: CHANGE PROPOSAL: Remove ping and hyperlink auditing (ISSUE-1 and ISSUE-2)
- Re: Path forward on Microdata
- http content type authoritative for object data?
- Re: Path forward on Microdata
- Re: Ability to submit invalid forms
- Ability to submit invalid forms
- Re: Inconsistent |typeof HTMLCanvasElement|
- Re: ISSUE-76: Need feedback on splitting Microdata into separate specification
- Re: ISSUE-76: Need feedback on splitting Microdata into separate specification
- Re: CHANGE PROPOSAL: Remove ping and hyperlink auditing (ISSUE-1 and ISSUE-2)
- Re: ISSUE-76: Need feedback on splitting Microdata into separate specification
- ISSUE-76: CHANGE PROPOSAL (Draft 2): Separate Microdata from HTML5 Specification
- Re: CHANGE PROPOSAL: Remove ping and hyperlink auditing (ISSUE-1 and ISSUE-2)
- Re: Splitting HTML from the HTML DOM (was Re: Renamed topic: focus and length of HTML5)
Monday, 7 December 2009
- Re: CHANGE PROPOSAL: Remove ping and hyperlink auditing (ISSUE-1 and ISSUE-2)
- Re: ISSUE-76: Need feedback on splitting Microdata into separate specification
- Re: ISSUE-76: Need feedback on splitting Microdata into separate specification
- Decision Process (Re: Splitting HTML from the HTML DOM (was Re: Renamed topic: focus and length of HTML5))
- Re: Splitting HTML from the HTML DOM (was Re: Renamed topic: focus and length of HTML5)
- Re: Splitting HTML from the HTML DOM (was Re: Renamed topic: focus and length of HTML5)
- Re: Splitting HTML from the HTML DOM (was Re: Renamed topic: focus and length of HTML5)
- Re: Splitting HTML from the HTML DOM (was Re: Renamed topic: focus and length of HTML5)
- Re: Splitting HTML from the HTML DOM (was Re: Renamed topic: focus and length of HTML5)
- Re: Splitting HTML from the HTML DOM (was Re: Renamed topic: focus and length of HTML5)
- Re: Splitting HTML from the HTML DOM (was Re: Renamed topic: focus and length of HTML5)
- Re: Splitting HTML from the HTML DOM (was Re: Renamed topic: focus and length of HTML5)
- Re: ISSUE-76: Need feedback on splitting Microdata into separate specification
- Re: ISSUE-76: Need feedback on splitting Microdata into separate specification
- Re: ISSUE-76: Need feedback on splitting Microdata into separate specification
- Re: Splitting HTML from the HTML DOM (was Re: Renamed topic: focus and length of HTML5)
- Re: Splitting HTML from the HTML DOM (was Re: Renamed topic: focus and length of HTML5)
- Path forward on Microdata
- Splitting HTML from the HTML DOM (was Re: Renamed topic: focus and length of HTML5)
- Re: Renamed topic: focus and length of HTML5
- Re: Renamed topic: focus and length of HTML5
- Re: Dropping Microdata entirely
- Re: Renamed topic: focus and length of HTML5
- Re: Dropping Microdata entirely
- Re: Dropping Microdata entirely
- Re: Dropping Microdata entirely
- Re: Renamed topic: focus and length of HTML5
- [Bug 8449] Remove extraneous material from Table section
- [Bug 8447] Tighter definition on the aside element
Sunday, 6 December 2009
- Re: ISSUE-76: Need feedback on splitting Microdata into separate specification
- Re: ISSUE-76: Need feedback on splitting Microdata into separate specification
- Re: ISSUE-76: Need feedback on splitting Microdata into separate specification
- Re: Renamed topic: focus and length of HTML5
- Inconsistent |typeof HTMLCanvasElement|
- Re: Renamed topic: focus and length of HTML5
- Re: Renamed topic: focus and length of HTML5
- Re: CHANGE PROPOSAL: Remove ping and hyperlink auditing (ISSUE-1 and ISSUE-2)
- CHANGE PROPOSAL: Remove ping and hyperlink auditing (ISSUE-1 and ISSUE-2)
Saturday, 5 December 2009
- Re: Dropping Microdata entirely
- Re: Dropping Microdata entirely
- Re: Dropping Microdata entirely
- Re: Dropping Microdata entirely
- Dropping Microdata entirely
- Re: Renamed topic: focus and length of HTML5
Friday, 4 December 2009
- Re: ISSUE-76: Need feedback on splitting Microdata into separate specification
- Re: ISSUE-76: Need feedback on splitting Microdata into separate specification
Saturday, 5 December 2009
- Re: Renamed topic: focus and length of HTML5
- Re: Renamed topic: focus and length of HTML5
- Re: ISSUE-76: Need feedback on splitting Microdata into separate specification
- Re: ISSUE-76: Need feedback on splitting Microdata into separate specification
- Re: ISSUE-76: Need feedback on splitting Microdata into separate specification
Friday, 4 December 2009
- Re: ISSUE-76: Need feedback on splitting Microdata into separate specification
- Re: ISSUE-76: Need feedback on splitting Microdata into separate specification
- Re: discussions of HTML6
- Re: discussions of HTML6
- Re: ISSUE-76: Need feedback on splitting Microdata into separate specification
- Re: ISSUE-76: Need feedback on splitting Microdata into separate specification
- Re: ISSUE-76: Need feedback on splitting Microdata into separate specification
- Re: ISSUE-76: Need feedback on splitting Microdata into separate specification
- Re: change proposal:modification to section 4.8.2.1 the img element
- Re: change proposal:modification to section 4.8.2.1 the img element
- Re: ISSUE-76: Need feedback on splitting Microdata into separate specification
- Re: ISSUE-76: Need feedback on splitting Microdata into separate specification
- Re: ISSUE-76: Need feedback on splitting Microdata into separate specification
- RE: discussions of HTML6
- Re: ISSUE-76: Need feedback on splitting Microdata into separate specification
- Re: discussions of HTML6
- Re: discussions of HTML6
- Re: ISSUE-76: Need feedback on splitting Microdata into separate specification
- Re: discussions of HTML6
- Re: ISSUE-76: Need feedback on splitting Microdata into separate specification
- Re: ISSUE-76: Need feedback on splitting Microdata into separate specification
- Re: discussions of HTML6
- Re: ISSUE-76: Need feedback on splitting Microdata into separate specification
- Re: ISSUE-76: Need feedback on splitting Microdata into separate specification
- Re: ISSUE-76: Need feedback on splitting Microdata into separate specification
- Re: Renamed topic: focus and length of HTML5 was Re: ISSUE-76: Need feedback on splitting Microdata into separate specification
- Renamed topic: focus and length of HTML5, was: ISSUE-76: Need feedback on splitting Microdata into separate specification
- Re: Renamed topic: focus and length of HTML5 was Re: ISSUE-76: Need feedback on splitting Microdata into separate specification
- Renamed topic: focus and length of HTML5 was Re: ISSUE-76: Need feedback on splitting Microdata into separate specification
- discussions of HTML6
- Re: ISSUE-76: Need feedback on splitting Microdata into separate specification
- Re: ISSUE-76: Need feedback on splitting Microdata into separate specification
- Re: ISSUE-76: Need feedback on splitting Microdata into separate specification
- Re: ISSUE-76: Need feedback on splitting Microdata into separate specification
- Re: ISSUE-76: Need feedback on splitting Microdata into separate specification
- Re: DOCTYPE versioning change proposal (ISSUE-4)
- Re: DOCTYPE versioning change proposal (ISSUE-4)
- Re: DOCTYPE versioning change proposal (ISSUE-4)
- Re: DOCTYPE versioning change proposal (ISSUE-4)
- Re: DOCTYPE versioning change proposal (ISSUE-4)
- Re: ISSUE-76: Need feedback on splitting Microdata into separate specification
- Re: ISSUE-76: Need feedback on splitting Microdata into separate specification
- Re: ISSUE-76: Need feedback on splitting Microdata into separate specification
- Re: DOCTYPE versioning change proposal (ISSUE-4)
- Re: ISSUE-76: Need feedback on splitting Microdata into separate specification
- Re: ISSUE-76: Need feedback on splitting Microdata into separate specification
- Re: Change proposal: Adding a sprite attribute to img tags
- Re: Change proposal: Adding a sprite attribute to img tags
- Change proposal: Adding a sprite attribute to img tags
- Re: ISSUE-76: Need feedback on splitting Microdata into separate specification
- Re: ISSUE-76: Need feedback on splitting Microdata into separate specification
- Minutes HTML WG 3 December 2009
- Re: ISSUE-76: Need feedback on splitting Microdata into separate specification
Thursday, 3 December 2009
- Re: ISSUE-76: Need feedback on splitting Microdata into separate specification
- Re: ISSUE-76: Need feedback on splitting Microdata into separate specification
- Re: ISSUE-76: Need feedback on splitting Microdata into separate specification
- Re: ISSUE-76: Need feedback on splitting Microdata into separate specification
- Re: ISSUE-76: Need feedback on splitting Microdata into separate specification
- Re: ISSUE-76: Need feedback on splitting Microdata into separate specification
- Re: ISSUE-76: Need feedback on splitting Microdata into separate specification
- Re: ISSUE-76: Need feedback on splitting Microdata into separate specification
- Re: ISSUE-76: Need feedback on splitting Microdata into separate specification
- Re: ISSUE-76: Need feedback on splitting Microdata into separate specification
- Re: ISSUE-76: Need feedback on splitting Microdata into separate specification
- Re: ESW Wiki (was Re: ISSUE-76: Need feedback on splitting Microdata into separate specification)
- Re: change proposal:modification to section 4.8.2.1 the img element
- Re: ISSUE-76: Need feedback on splitting Microdata into separate specification
- Re: ISSUE-76: Need feedback on splitting Microdata into separate specification
- change proposal:modification to section 4.8.2.1 the img element
- Re: ESW Wiki (was Re: ISSUE-76: Need feedback on splitting Microdata into separate specification)
- Re: ESW Wiki (was Re: ISSUE-76: Need feedback on splitting Microdata into separate specification)
- [Entities-last-call] - htmlmath entities collection
- Re: ISSUE-76: Need feedback on splitting Microdata into separate specification
- Re: ISSUE-76: Need feedback on splitting Microdata into separate specification
- Re: ACTION-103 Follow up on the about: scheme Registration
- Re: ISSUE-76: Need feedback on splitting Microdata into separate specification
- Re: ESW Wiki (was Re: ISSUE-76: Need feedback on splitting Microdata into separate specification)
- Re: ESW Wiki (was Re: ISSUE-76: Need feedback on splitting Microdata into separate specification)
- Re: Bug 8404 -- taking it to the lists
Wednesday, 2 December 2009
- Re: Bug 8404 -- taking it to the lists
- Re: ISSUE-76: Need feedback on splitting Microdata into separate specification
- Re: ESW Wiki (was Re: ISSUE-76: Need feedback on splitting Microdata into separate specification)
- Re: Bug 8404 -- taking it to the lists
- Re: Bug 8404 -- taking it to the lists
- Re: Bug 8404 -- taking it to the lists
- Re: Bug 8404 -- taking it to the lists
- Re: Bug 8404 -- taking it to the lists
- Re: Bug 8404 -- taking it to the lists
- Re: Bug 8404 -- taking it to the lists
- Re: Bug 8404 -- taking it to the lists
- Re: ESW Wiki (was Re: ISSUE-76: Need feedback on splitting Microdata into separate specification)
- ESW Wiki (was Re: ISSUE-76: Need feedback on splitting Microdata into separate specification)
- Re: ISSUE-76: Need feedback on splitting Microdata into separate specification
- Re: Bug 8404 -- taking it to the lists
- Re: ISSUE-76: Need feedback on splitting Microdata into separate specification
- Re: Bug 8404 -- taking it to the lists
- Re: ISSUE-76: Need feedback on splitting Microdata into separate specification
- Re: Bug 8404 -- taking it to the lists
- Re: ISSUE-76: Need feedback on splitting Microdata into separate specification
- Re: Bug 8404 -- taking it to the lists
- Re: Bug 8404 -- taking it to the lists
- Re: Bug 8404 -- taking it to the lists
- Re: Bug 8404 -- taking it to the lists
- Re: Bug 8404 -- taking it to the lists
- Re: Bug 8404 -- taking it to the lists
- Re: Bug 8404 -- taking it to the lists
- Re: Bug 8404 -- taking it to the lists
- Re: Bug 8404 -- taking it to the lists
- Re: Bug 8404 -- taking it to the lists
- Re: ISSUE-76: Need feedback on splitting Microdata into separate specification
- Re: ISSUE-83 ACTION-152 Change Proposal for the use of dt/dd in figure and details
- RE: DOCTYPE versioning change proposal (ISSUE-4)
- Re: Bug 8404 -- taking it to the lists
- Re: ISSUE-83 ACTION-152 Change Proposal for the use of dt/dd in figure and details
- RE: DOCTYPE versioning change proposal (ISSUE-4)
- RE: DOCTYPE versioning change proposal (ISSUE-4)
Tuesday, 1 December 2009
- RE: HTML CHANGE PROPOSAL; change definition of URL to normative reference to IRIBIS
- Re: Bug 8404 -- taking it to the lists
- Re: Bug 8404 -- taking it to the lists
- Re: Bug 8404 -- taking it to the lists
- Re: ISSUE-83 ACTION-152 Change Proposal for the use of dt/dd in figure and details
- Re: Bug 8404 -- taking it to the lists
- Re: ISSUE-83 ACTION-152 Change Proposal for the use of dt/dd in figure and details
- Re: Bug 8404 -- taking it to the lists
- Re: ISSUE-83 ACTION-152 Change Proposal for the use of dt/dd in figure and details
- Re: HTML CHANGE PROPOSAL; change definition of URL to normative reference to IRIBIS
- Re: ISSUE-83 ACTION-152 Change Proposal for the use of dt/dd in figure and details
- Re: Bug 8404 -- taking it to the lists
- RE: CHANGE PROPOSAL: Table Summary
- Re: DOCTYPE versioning change proposal (ISSUE-4)
- Re: Bug 8404 -- taking it to the lists
- [Bug 5821] meta/@scheme missing
- Re: CHANGE PROPOSAL: Table Summary
- Re: Bug 8404 -- taking it to the lists
- Re: Bug 8404 -- taking it to the lists
- Re: Bug 8404 -- taking it to the lists
- Re: Bug 8404 -- taking it to the lists
- Re: DOCTYPE versioning change proposal (ISSUE-4)
- Re: Bug 8404 -- taking it to the lists
- Re: Bug 8404 -- taking it to the lists
- Re: Bug 8404 -- taking it to the lists
- Re: Bug 8404 -- taking it to the lists
- Re: Bug 8404 -- taking it to the lists
- Re: Bug 8404 -- taking it to the lists
- Re: Param
- Re: Bug 8404 -- taking it to the lists
- Re: Bug 8404 -- taking it to the lists
- Re: DOCTYPE versioning change proposal (ISSUE-4)
- Re: Bug 8404 -- taking it to the lists
- Re: Bug 8404 -- taking it to the lists
- Re: Bug 8404 -- taking it to the lists
- Re: Bug 8404 -- taking it to the lists
- Re: Bug 8404 -- taking it to the lists
- Re: Bug 8404 -- taking it to the lists
- Re: DOCTYPE versioning change proposal (ISSUE-4)
- Re: Bug 8404 -- taking it to the lists
- Re: Bug 8404 -- taking it to the lists
- Re: Bug 8404 -- taking it to the lists
- Re: DOCTYPE versioning change proposal (ISSUE-4)
- Re: Bug 8404 -- taking it to the lists
- Re: Bug 8404 -- taking it to the lists
- Re: Bug 8404 -- taking it to the lists
- Re: Bug 8404 -- taking it to the lists
- Re: Bug 8404 -- taking it to the lists
- Bug 8404 -- taking it to the lists
- Re: ARIA roles added to the a element should be conforming in HTML5.
- Re: DOCTYPE versioning change proposal (ISSUE-4)
- Re: DOCTYPE versioning change proposal (ISSUE-4)
- Re: DOCTYPE versioning change proposal (ISSUE-4)
- DOCTYPE versioning change proposal (ISSUE-4)