Sunday, 31 January 2010
- Re: Understanding the "applicable specifications" clause (was: Re: Decentralised extensibility idea (ISSUE-41))
- Re: New round of Working Drafts (was Re: New split-out drafts)
- Re: ISSUE-95 hidden - Chairs Solicit Proposals - off topic object
Saturday, 30 January 2010
- Re: ISSUE-95 hidden - Chairs Solicit Proposals - off topic object
- RE: New round of Working Drafts (was Re: New split-out drafts)
- RE: New round of Working Drafts (was Re: New split-out drafts)
- RE: HTML+RDFa Heartbeat Draft publishing request
- Re: ISSUE-95 hidden - Chairs Solicit Proposals - off topic object
- Re: New round of Working Drafts (was Re: New split-out drafts)
- Re: ISSUE-95 hidden - Chairs Solicit Proposals
- Re: Next issues to move forward on
- Re: Next issues to move forward on
- Re: ISSUE-95 hidden - Chairs Solicit Proposals - off topic object
- Re: New round of Working Drafts (was Re: New split-out drafts)
- Re: New round of Working Drafts (was Re: New split-out drafts)
- Re: New round of Working Drafts (was Re: New split-out drafts)
- Re: ISSUE-95 hidden - Chairs Solicit Proposals
- Re: New round of Working Drafts (was Re: New split-out drafts)
- Re: ISSUE-95 hidden - Chairs Solicit Proposals
- Re: ISSUE-95 hidden - Chairs Solicit Proposals
Friday, 29 January 2010
- Re: ISSUE-95 hidden - Chairs Solicit Proposals
- Re: ISSUE-95 hidden - Chairs Solicit Proposals
- RE: New round of Working Drafts (was Re: New split-out drafts)
- Re: ISSUE-95 hidden - Chairs Solicit Proposals
- Re: ISSUE-95 hidden - Chairs Solicit Proposals
- Re: ISSUE-95 hidden - Chairs Solicit Proposals
- Re: ISSUE-95 hidden - Chairs Solicit Proposals
- Re: ISSUE-95 hidden - Chairs Solicit Proposals
- Re: ISSUE-95 hidden - Chairs Solicit Proposals
- Re: ISSUE-95 hidden - Chairs Solicit Proposals
- Re: ISSUE-95 hidden - Chairs Solicit Proposals
- Re: ISSUE-95 hidden - Chairs Solicit Proposals
- Re: ISSUE-95 hidden - Chairs Solicit Proposals
- Re: ISSUE-95 hidden - Chairs Solicit Proposals
- Re: ISSUE-95 hidden - Chairs Solicit Proposals
- Re: ISSUE-95 hidden - Chairs Solicit Proposals
- Re: Next issues to move forward on
- Re: New round of Working Drafts (was Re: New split-out drafts)
- Re: Microdata to RDF conversion
- Re: Pending tracker issues
- RE: Comparison between <sandbox> and @sandbox
- Re: Comparison between <sandbox> and @sandbox
- RE: Comparison between <sandbox> and @sandbox
Thursday, 28 January 2010
- Comparison between <sandbox> and @sandbox
- Re: over specification is anti-competitive (blog post)
- [Bug 5821] meta/@scheme missing
- Re: Pending tracker issues
- Re: Next issues to move forward on
- Re: Next issues to move forward on
- Re: <summary> not for table (was Re: Next issues to move forward on)
- Re: <summary> not for table (was Re: Next issues to move forward on)
- <summary> not for table (was Re: Next issues to move forward on)
- Re: Suggestion for Microdata to RDF conversion
- Re: Next issues to move forward on
- Re: Next issues to move forward on
- Pending tracker issues
- [Bug 8088] Change back the meaning of <meta http-equiv="Content-Language" content="FOO, BAR">
- [Bug 8003] line breaks in attributes (especially title)
- [Bug 8000] ARIA roles added to the a element should be conforming in HTML5
- Next issues to move forward on
- Extension granted on some Change Proposals
- Re: ISSUE-93 details - Call for Change Proposals
- Re: would like more time on ACTION-172 (ISSUE-4 and ISSUE-84)
- W3C document license Re: ISSUE-27: rel-ownership - Chairs Solicit Proposals
- Re: HTML WG F2F meeting
- Re: What defines a "plugin"? WRT sandboxing?
- Re: Suggestion for Microdata to RDF conversion
- Re: Suggestion for Microdata to RDF conversion
Wednesday, 27 January 2010
- Re: What defines a "plugin"? WRT sandboxing?
- would like more time on ACTION-172 (ISSUE-4 and ISSUE-84)
- over specification is anti-competitive (blog post)
- RE: What defines a "plugin"? WRT sandboxing?
- Re: What defines a "plugin"? WRT sandboxing?
- Re: What defines a "plugin"? WRT sandboxing?
- Re: RETRACTION: ISSUE-98 canvas2d - Call for Change Proposals
- Re: HTML WG F2F meeting
- Re: HTML WG F2F meeting
- Reminder: WAI-ARIA review deadline 2 February 2010
- Re: HTML WG F2F meeting
- RE: HTML WG F2F meeting
- Re: HTML WG F2F meeting
- Re: HTML WG F2F meeting
- Re: HTML WG F2F meeting
- RE: HTML WG F2F meeting
Tuesday, 26 January 2010
- ISSUE-96 progress - Call for Change Proposals
- RETRACTION: ISSUE-98 canvas2d - Call for Change Proposals
- Re: HTML WG F2F meeting
- ISSUE-98 canvas2d - Call for Change Proposals
- ISSUE-97 meter - Call for Change Proposals
- ISSUE-94 webcoresplit - Call for Proposals
- ISSUE-93 details - Call for Change Proposals
- Re: What defines a "plugin"? WRT sandboxing?
- Re: What defines a "plugin"? WRT sandboxing?
- HTML WG F2F meeting
- Re: What defines a "plugin"? WRT sandboxing?
- Re: What defines a "plugin"? WRT sandboxing?
- RE: What defines a "plugin"? WRT sandboxing?
- Re: What defines a "plugin"? WRT sandboxing?
- RE: What defines a "plugin"? WRT sandboxing?
- Re: comments on draft-barth-mime-sniffing
- Re: What defines a "plugin"? WRT sandboxing?
- RE: What defines a "plugin"? WRT sandboxing?
- Re: removing the srcdoc
- Re: removing the srcdoc
- Re: removing the srcdoc
- Re: removing the srcdoc
- Re: removing the srcdoc
- Re: removing the srcdoc
- Re: removing the srcdoc
- Re: What defines a "plugin"? WRT sandboxing?
- Re: removing the srcdoc
- RE: What defines a "plugin"? WRT sandboxing?
- Re: removing the srcdoc
- Re: Canvas Accessibility Next steps
- [Bug 8818] Remove the srcdoc attribute
- removing the srcdoc
- Re: Trying to use <iframe srcdoc= >
- Re: Request for group input on ISSUE-83 (figure and details captions)
- Re: <iframe doc="">
- Re: Request for group input on ISSUE-83 (figure and details captions)
- Re: Request for group input on ISSUE-83 (figure and details captions)
- Re: <iframe doc="">
- Re: <iframe doc="">
Monday, 25 January 2010
- Re: Trying to use <iframe srcdoc= >
- Re: Trying to use <iframe srcdoc= >
- Re: Trying to use <iframe srcdoc= >
- Re: Trying to use <iframe srcdoc= >
- Re: Trying to use <iframe srcdoc= >
- Re: Trying to use <iframe srcdoc= >
- Re: Trying to use <iframe srcdoc= >
- Re: Request for group input on ISSUE-83 (figure and details captions)
- Re: <iframe doc="">
- Re: Trying to use <iframe srcdoc= >
- Trying to use <iframe srcdoc= >
- Re: [whatwg] some thoughts on sandboxed IFRAMEs
- Re: <iframe doc="">
- Re: <iframe doc="">
- Re: Proposal: Canvas accessibility and a media querries approach for alternative content (Action Item 6 in the HTML Accessibility Task Force)
- Re: What defines a "plugin"? WRT sandboxing?
- Re: <iframe doc="">
- Re: <iframe doc="">
- Re: <iframe doc="">
- Re: <iframe doc="">
- Re: <iframe doc="">
- Re: <iframe doc="">
- Re: <iframe doc="">
- Re: <iframe doc="">
- Re: <iframe doc="">
- RE: What defines a "plugin"? WRT sandboxing?
- Re: <iframe doc="">
- Re: <iframe doc="">
- Re: <iframe doc="">
- Re: <iframe doc="">
- Re: <iframe doc="">
- Re: <iframe doc="">
- wiki pages for CANVAS accessibility meetings & minutes
- Re: <iframe doc="">
- Re: <iframe doc="">
- Re: <iframe doc="">
- Re: Request for group input on ISSUE-83 (figure and details captions)
- Re: <iframe doc="">
- Re: <iframe doc="">
- Re: <iframe doc="">
- Re: <iframe doc="">
- Re: <iframe doc="">
- Re: <iframe doc="">
- Re: <iframe doc="">
- Re: <iframe doc="">
- Re: <iframe doc="">
- Re: <iframe doc="">
- Re: <iframe doc="">
- Re: <iframe doc="">
- Re: <iframe doc="">
- Re: <iframe doc="">
- Re: <iframe doc="">
- Re: <iframe doc="">
- Re: <iframe doc="">
- Re: <iframe doc="">
- Re: <iframe doc="">
- Re: <iframe doc="">
- Re: <iframe doc="">
- Re: <iframe doc="">
- Re: <iframe doc="">
- Re: What defines a "plugin"? WRT sandboxing?
- Re: ISSUE-27: rel-ownership - Chairs Solicit Proposals
- Re: <iframe doc="">
- Re: <iframe doc="">
- Re: Suggestion for Microdata to RDF conversion
- Re: Suggestion for Microdata to RDF conversion
- Re: <iframe doc="">
- Re: Request for group input on ISSUE-83 (figure and details captions)
- Re: Request for group input on ISSUE-83 (figure and details captions)
- Re: What defines a "plugin"? WRT sandboxing?
- Re: What defines a "plugin"? WRT sandboxing?
- Re: What defines a "plugin"? WRT sandboxing?
- Re: Request for group input on ISSUE-83 (figure and details captions)
- Re: Request for group input on ISSUE-83 (figure and details captions)
- public-html-bugzilla list [was: ISSUE 93 (details): Return Details Element [HTML 5 spec]]
- Re: Request for group input on ISSUE-83 (figure and details captions)
- Re: Request for group input on ISSUE-83 (figure and details captions)
- Re: Proposal: Canvas accessibility and a media querries approach for alternative content (Action Item 6 in the HTML Accessibility Task Force)
- Re: Canvas Accessibility Next steps
- Re: <iframe doc="">
Sunday, 24 January 2010
- Re: <iframe> operation
- Re: <iframe doc="">
- Re: Proposal: Canvas accessibility and a media querries approach for alternative content (Action Item 6 in the HTML Accessibility Task Force)
- RE: What defines a "plugin"? WRT sandboxing?
- Re: <iframe doc="">
- Re: Canvas Accessibility Next steps
- Re: <summary> element and Issue 32
- Re: <iframe doc="">
- Re: <summary> element and Issue 32
- Re: <iframe> operation
- Re: What defines a "plugin"? WRT sandboxing?
- Re: IRI working group approved by IETF, call for volunteers for co-chair with W3C/IETF experience
- Re: <iframe> operation
- <iframe> operation
- IRI working group approved by IETF, call for volunteers for co-chair with W3C/IETF experience
- Re: <iframe doc="">
- Re: <iframe doc="">
- Re: <iframe doc="">
- Re: <iframe doc="">
- Re: Request for group input on ISSUE-83 (figure and details captions)
- Re: <iframe doc="">
- Re: <iframe doc="">
- Re: What defines a "plugin"? WRT sandboxing?
- Re: <iframe doc="">
- RE: <iframe doc="">
- RE: What defines a "plugin"? WRT sandboxing?
- Re: <iframe doc="">
- Re: Discussion on Change Proposal for ISSUE-66
- Re: <iframe doc="">
- Re: Discussion on Change Proposal for ISSUE-66
- Re: What defines a "plugin"? WRT sandboxing?
- RE: What defines a "plugin"? WRT sandboxing?
- Re: <iframe doc="">
- Re: What defines a "plugin"? WRT sandboxing?
- Re: <iframe doc="">
- Re: <iframe doc="">
- Re: <iframe doc="">
- Re: <iframe doc="">
- Re: What defines a "plugin"? WRT sandboxing?
- Re: <iframe doc="">
- Re: <iframe doc="">
- Re: Discussion on Change Proposal for ISSUE-66
- Re: What defines a "plugin"? WRT sandboxing?
- Re: <iframe doc="">
- Re: Disallow plug-ins in text/html-sandboxed? (was: Re: text/sandboxed-html)
- Re: HTML+RDFa Heartbeat Draft publishing request
- Re: Discussion on Change Proposal for ISSUE-66
- Re: <summary> element and Issue 32
- Re: Disallow plug-ins in text/html-sandboxed? (was: Re: text/sandboxed-html)
- Re: <iframe doc="">
- Re: Discussion on Change Proposal for ISSUE-66
- RE: Disallow plug-ins in text/html-sandboxed? (was: Re: text/sandboxed-html)
- Re: Discussion on Change Proposal for ISSUE-66
- Re: Disallow plug-ins in text/html-sandboxed? (was: Re: text/sandboxed-html)
- Re: Request for group input on ISSUE-83 (figure and details captions)
- Re: <iframe doc="">
- Re: <iframe doc="">
- Re: Discussion on Change Proposal for ISSUE-66
- Re: What defines a "plugin"? WRT sandboxing?
- Re: <iframe doc="">
- What defines a "plugin"? WRT sandboxing?
- RE: Disallow plug-ins in text/html-sandboxed? (was: Re: text/sandboxed-html)
- RE: <iframe doc="">
- Re: Request for group input on ISSUE-83 (figure and details captions)
- <summary> element and Issue 32
- Re: Discussion on Change Proposal for ISSUE-66
- Re: Discussion on Change Proposal for ISSUE-66
- Re: Request for group input on ISSUE-83 (figure and details captions)
- Re: Request for group input on ISSUE-83 (figure and details captions)
- RE: Discussion on Change Proposal for ISSUE-66
- Re: Discussion on Change Proposal for ISSUE-66
- Re: Discussion on Change Proposal for ISSUE-66
- Re: spec verbosity and algorithms
- Re: spec verbosity and algorithms
Saturday, 23 January 2010
- RE: Discussion on Change Proposal for ISSUE-66
- Re: spec verbosity and algorithms
- Re: Proposal: Canvas accessibility and a media querries approach for alternative content (Action Item 6 in the HTML Accessibility Task Force)
- Re: spec verbosity and algorithms
- Re: spec verbosity and algorithms
- Re: spec verbosity and algorithms
- Re: ISSUE-27: rel-ownership - Chairs Solicit Proposals
- Re: Proposal: Canvas accessibility and a media querries approach for alternative content (Action Item 6 in the HTML Accessibility Task Force)
- Re: Proposal: Canvas accessibility and a media querries approach for alternative content (Action Item 6 in the HTML Accessibility Task Force)
- Re: spec verbosity and algorithms
- Re: spec verbosity and algorithms
- Re: spec verbosity and algorithms
- Re: Proposal: Canvas accessibility and a media querries approach for alternative content (Action Item 6 in the HTML Accessibility Task Force)
- Re: Proposal: Canvas accessibility and a media querries approach for alternative content (Action Item 6 in the HTML Accessibility Task Force)
- 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: Proposal: Canvas accessibility and a media querries approach for alternative content (Action Item 6 in the HTML Accessibility Task Force)
- Re: ISSUE-27: rel-ownership - Chairs Solicit Proposals
- Re: Proposal: Canvas accessibility and a media querries approach for alternative content (Action Item 6 in the HTML Accessibility Task Force)
- Re: Canvas Accessibility Next steps
- Re: ISSUE-27: rel-ownership - Chairs Solicit Proposals
Friday, 22 January 2010
- 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: ISSUE-27: rel-ownership - Chairs Solicit Proposals
- Re: Proposal: Canvas accessibility and a media querries approach for alternative content (Action Item 6 in the HTML Accessibility Task Force)
- Re: Proposal: Canvas accessibility and a media querries approach for alternative content (Action Item 6 in the HTML Accessibility Task Force)
- Re: Proposal: Canvas accessibility and a media querries approach for alternative content (Action Item 6 in the HTML Accessibility Task Force)
- Re: Proposal: Canvas accessibility and a media querries approach for alternative content (Action Item 6 in the HTML Accessibility Task Force)
- Re: Proposal: Canvas accessibility and a media querries approach for alternative content (Action Item 6 in the HTML Accessibility Task Force)
- Re: Canvas Accessibility Next steps
- Re: Proposal: Canvas accessibility and a media querries approach for alternative content (Action Item 6 in the HTML Accessibility Task Force)
- Re: Proposal: Canvas accessibility and a media querries approach for alternative content (Action Item 6 in the HTML Accessibility Task Force)
- Re: Proposal: Canvas accessibility and a media querries approach for alternative content (Action Item 6 in the HTML Accessibility Task Force)
- Re: Canvas Accessibility Next steps
- Re: Proposal: Canvas accessibility and a media querries approach for alternative content (Action Item 6 in the HTML Accessibility Task Force)
- Re: Proposal: Canvas accessibility and a media querries approach for alternative content (Action Item 6 in the HTML Accessibility Task Force)
- Re: Proposal: Canvas accessibility and a media querries approach for alternative content (Action Item 6 in the HTML Accessibility Task Force)
- Re: Suggestion for Microdata to RDF conversion
- Re: Suggestion for Microdata to RDF conversion
- Re: spec verbosity and algorithms
- Re: Suggestion for Microdata to RDF conversion
- RE: Canvas Accessibility Next steps
- RE: Canvas Accessibility Next steps
- RE: ISSUE-27: rel-ownership - Chairs Solicit Proposals
- Re: spec verbosity and algorithms
- Re: spec verbosity and algorithms
- spec verbosity and algorithms
- Re: Discussion on Change Proposal for ISSUE-66
- Re: Discussion on Change Proposal for ISSUE-66
- Re: Discussion on Change Proposal for ISSUE-66
- Re: Canvas Accessibility Next steps
- Re: HTML+RDFa Heartbeat Draft publishing request
- Re: Discussion on Change Proposal for ISSUE-66
- Re: ISSUE-27: rel-ownership - Chairs Solicit Proposals
- Re: ISSUE-27: rel-ownership - Chairs Solicit Proposals
- Re: ISSUE-85 - anchor-roles - Chairs Solicit Proposals
- Re: Discussion on Change Proposal for ISSUE-66
- Re: ACTION-138 ARIA matrix (was: Re: [VER 2] {agenda} HTML WG telcon 2010-01-21: AIs, CfC/CfPs, and heartbeat docs)
- Re: ISSUE-27: rel-ownership - Chairs Solicit Proposals
- Re: Suggestion for Microdata to RDF conversion
- Re: ISSUE-27: rel-ownership - Chairs Solicit Proposals
- Opera investigating implementation of image map on canvas
- Re: Suggestion for Microdata to RDF conversion
- Re: Discussion on Change Proposal for ISSUE-66
- Re: Suggestion for Microdata to RDF conversion
- Re: ACTION-138 ARIA matrix (was: Re: [VER 2] {agenda} HTML WG telcon 2010-01-21: AIs, CfC/CfPs, and heartbeat docs)
- Re: Discussion on Change Proposal for ISSUE-66
- Re: Suggestion for Microdata to RDF conversion
- ACTION-138 ARIA matrix (was: Re: [VER 2] {agenda} HTML WG telcon 2010-01-21: AIs, CfC/CfPs, and heartbeat docs)
- RE: Discussion on Change Proposal for ISSUE-66
- Re: Discussion on Change Proposal for ISSUE-66
- Re: Discussion on Change Proposal for ISSUE-66
- Re: Discussion on Change Proposal for ISSUE-66
- Re: Discussion on Change Proposal for ISSUE-66
- Re: Discussion on Change Proposal for ISSUE-66
- Re: Discussion on Change Proposal for ISSUE-66
- Re: Discussion on Change Proposal for ISSUE-66
- Re: Canvas Accessibility Next steps
- Re: Discussion on Change Proposal for ISSUE-66
- Re: Discussion on Change Proposal for ISSUE-66
- Re: ACTION-161 / ISSUE 88: Multiple content languages
- RE: Discussion on Change Proposal for ISSUE-66
- Re: Discussion on Change Proposal for ISSUE-66
- RE: Discussion on Change Proposal for ISSUE-66
- Re: ISSUE-27: rel-ownership - Chairs Solicit Proposals
- Re: ISSUE-27: rel-ownership Change Proposal discussion
- Re: Discussion on Change Proposal for ISSUE-66
- RE: INVALID_STATE_ERR or INVALID_ACCESS_ERR when attempting to write into XML documents
- RE: INVALID_STATE_ERR or INVALID_ACCESS_ERR when attempting to write into XML documents
- Re: Canvas Accessibility Next steps
- Re: INVALID_STATE_ERR or INVALID_ACCESS_ERR when attempting to write into XML documents
- Re: Discussion on Change Proposal for ISSUE-66
- Re: Discussion on Change Proposal for ISSUE-66
- Re: ISSUE-27: rel-ownership - Chairs Solicit Proposals
- Re: Discussion on Change Proposal for ISSUE-66
Thursday, 21 January 2010
- Re: Canvas Accessibility Next steps
- Re: Request for group input on ISSUE-83 (figure and details captions)
- Re: Request for group input on ISSUE-83 (figure and details captions)
- Re: ACTION-161 / ISSUE 88: Multiple content languages
- RE: HTML+RDFa Heartbeat Draft publishing request
- Re: Request for group input on ISSUE-83 (figure and details captions)
- Re: Suggestion for Microdata to RDF conversion
- Re: Suggestion for Microdata to RDF conversion
- Re: Suggestion for Microdata to RDF conversion
- Invitation to connect on LinkedIn
- Re: Suggestion for Microdata to RDF conversion
- Re: Canvas Accessibility Next steps
- Re: Suggestion for Microdata to RDF conversion
- Re: Canvas Accessibility Next steps
- Re: Canvas Accessibility Next steps
- Re: Understanding the "applicable specifications" clause (was: Re: Decentralised extensibility idea (ISSUE-41))
- Re: Request for group input on ISSUE-83 (figure and details captions)
- Re: Request for group input on ISSUE-83 (figure and details captions)
- Re: Request for group input on ISSUE-83 (figure and details captions)
- INVALID_STATE_ERR or INVALID_ACCESS_ERR when attempting to write into XML documents
- Re: Understanding the "applicable specifications" clause (was: Re: Decentralised extensibility idea (ISSUE-41))
- Re: Request for group input on ISSUE-83 (figure and details captions)
- Re: Understanding the "applicable specifications" clause (was: Re: Decentralised extensibility idea (ISSUE-41))
- Re: Discussion on Change Proposal for ISSUE-66
- Re: FYI: review of draft-abarth-mime-sniff-03
- Re: Discussion on Change Proposal for ISSUE-66
- Re: Proposal: Canvas accessibility and a media querries approach for alternative content (Action Item 6 in the HTML Accessibility Task Force)
- FYI for minutes: irc - [18:05] <Zakim> + +1.613.998.aabb
- RE: ACTION-161 / ISSUE 88: Multiple content languages
- Re: ACTION-103 Follow up on the about: scheme Registration
- Re: Discussion on Change Proposal for ISSUE-66
- [VER 2] {agenda} HTML WG telcon 2010-01-21: AIs, CfC/CfPs, and heartbeat docs
- Re: Understanding the "applicable specifications" clause (was: Re: Decentralised extensibility idea (ISSUE-41))
- Re: Discussion on Change Proposal for ISSUE-66
- Re: ISSUE-27: rel-ownership - Chairs Solicit Proposals
- Re: Discussion on Change Proposal for ISSUE-66
- Re: Discussion on Change Proposal for ISSUE-66
- RE: Discussion on Change Proposal for ISSUE-66
- Re: Registries, meta/name=keyword, head/@profile (ISSUE-27, ISSUE-55 and ISSUE-79)
- Re: Discussion on Change Proposal for ISSUE-66
- Re: Request for group input on ISSUE-83 (figure and details captions)
- Re: Discussion on Change Proposal for ISSUE-66
- Re: Request for group input on ISSUE-83 (figure and details captions)
- Re: Discussion on Change Proposal for ISSUE-66
- Re: Understanding the "applicable specifications" clause (was: Re: Decentralised extensibility idea (ISSUE-41))
- Re: Proposal: Canvas accessibility and a media querries approach for alternative content (Action Item 6 in the HTML Accessibility Task Force)
- Re: Understanding the "applicable specifications" clause (was: Re: Decentralised extensibility idea (ISSUE-41))
- Re: Suggestion for Microdata to RDF conversion
- Re: FYI: review of draft-abarth-mime-sniff-03
- Re: Discussion on Change Proposal for ISSUE-66
- Re: ISSUE-27: rel-ownership - Chairs Solicit Proposals
- RE: Discussion on Change Proposal for ISSUE-66
- Re: Proposal: Canvas accessibility and a media querries approach for alternative content (Action Item 6 in the HTML Accessibility Task Force)
- Re: Discussion on Change Proposal for ISSUE-66
- Re: Discussion on Change Proposal for ISSUE-66
- Re: Canvas Accessibility Next steps
- Re: ISSUE-27: rel-ownership Change Proposal discussion
- Re: ISSUE-27: rel-ownership Change Proposal discussion
- Re: Request for group input on ISSUE-83 (figure and details captions)
- New round of Working Drafts (was Re: New split-out drafts)
- ISSUE-85 - anchor-roles - Chairs Solicit Proposals
- ISSUE-86 - atom-id-stability - Chairs Solicit Proposals
- ISSUE-82 - profile-disambiguation - Chairs Solicit Proposals
- ISSUE-55 - head-profile
- RE: Discussion on Change Proposal for ISSUE-66
- Re: HTML CHANGE PROPOSAL; change definition of URL to normative reference to IRIBIS
- Re: ISSUE-27: rel-ownership Change Proposal discussion
- RE: Fieldset disabled attribute and descendants
- Re: Legacy Doctype and Doctype Versioning
- Re: Legacy Doctype and Doctype Versioning
- Re: ISSUE-27: rel-ownership Change Proposal discussion
- Discussion on Change Proposal for ISSUE-66
- Re: ISSUE-81: representation-vs-resource - Chairs Solicit Proposals
- ISSUE-27: rel-ownership Change Proposal discussion
- Re: FYI: review of draft-abarth-mime-sniff-03
- Re: Understanding the "applicable specifications" clause (was: Re: Decentralised extensibility idea (ISSUE-41))
Wednesday, 20 January 2010
- Re: Suggestion for Microdata to RDF conversion
- FYI: review of draft-abarth-mime-sniff-03
- Re: ISSUE-27: rel-ownership - Chairs Solicit Proposals
- Re: Understanding the "applicable specifications" clause
- Re: Microdata to RDF conversion
- Re: Proposal: Canvas accessibility and a media querries approach for alternative content (Action Item 6 in the HTML Accessibility Task Force)
- Re: Understanding the "applicable specifications" clause (was: Re: Decentralised extensibility idea (ISSUE-41))
- Re: draft HTML5: Techniques for the provision of text alternatives
- Re: Understanding the "applicable specifications" clause (was: Re: Decentralised extensibility idea (ISSUE-41))
- Re: draft HTML5: Techniques for the provision of text alternatives
- Re: XHTML Syntax Served as text/html (Was: Decentralized poetry markup (language))
- Re: XHTML Syntax Served as text/html (Was: Decentralized poetry markup (language))
- Re: Decentralized poetry markup (language) (ISSUE-41)
- {agenda} HTML WG telcon 2010-01-21: AIs, CfC/CfPs, and heartbeat docs
- Re: Understanding the "applicable specifications" clause (was: Re: Decentralised extensibility idea (ISSUE-41))
- Re: XHTML Syntax Served as text/html (Was: Decentralized poetry markup (language))
- Re: Understanding the "applicable specifications" clause (was: Re: Decentralised extensibility idea (ISSUE-41))
- Re: XHTML Syntax Served as text/html (Was: Decentralized poetry markup (language))
- Re: Understanding the "applicable specifications" clause (was: Re: Decentralised extensibility idea (ISSUE-41))
- Re: Proposal: Canvas accessibility and a media querries approach for alternative content (Action Item 6 in the HTML Accessibility Task Force)
- Re: Proposal: Canvas accessibility and a media querries approach for alternative content (Action Item 6 in the HTML Accessibility Task Force)
- Re: Proposal: Canvas accessibility and a media querries approach for alternative content (Action Item 6 in the HTML Accessibility Task Force)
- Re: Proposal: Canvas accessibility and a media querries approach for alternative content (Action Item 6 in the HTML Accessibility Task Force)
- Re: XHTML Syntax Served as text/html (Was: Decentralized poetry markup (language))
- Re: Proposal: Canvas accessibility and a media querries approach for alternative content (Action Item 6 in the HTML Accessibility Task Force)
- Re: draft HTML5: Techniques for the provision of text alternatives
- Re: Proposal: Canvas accessibility and a media querries approach for alternative content (Action Item 6 in the HTML Accessibility Task Force)
- Re: Decentralized poetry markup (language) (ISSUE-41)
- Re: Proposal: Canvas accessibility and a media querries approach for alternative content (Action Item 6 in the HTML Accessibility Task Force)
- Re: Proposal: Canvas accessibility and a media querries approach for alternative content (Action Item 6 in the HTML Accessibility Task Force)
- Re: Proposal: Canvas accessibility and a media querries approach for alternative content (Action Item 6 in the HTML Accessibility Task Force)
- Re: Understanding the "applicable specifications" clause (was: Re: Decentralised extensibility idea (ISSUE-41))
- Re: Proposal: Canvas accessibility and a media querries approach for alternative content (Action Item 6 in the HTML Accessibility Task Force)
- Re: Proposal: Canvas accessibility and a media querries approach for alternative content (Action Item 6 in the HTML Accessibility Task Force)
- Re: Proposal: Canvas accessibility and a media querries approach for alternative content (Action Item 6 in the HTML Accessibility Task Force)
- Re: Proposal: Canvas accessibility and a media querries approach for alternative content (Action Item 6 in the HTML Accessibility Task Force)
- Re: Understanding the "applicable specifications" clause (was: Re: Decentralised extensibility idea (ISSUE-41))
- Re: Understanding the "applicable specifications" clause
- Re: Proposal: Canvas accessibility and a media querries approach for alternative content (Action Item 6 in the HTML Accessibility Task Force)
- Re: Proposal: Canvas accessibility and a media querries approach for alternative content (Action Item 6 in the HTML Accessibility Task Force)
- Re: Proposal: Canvas accessibility and a media querries approach for alternative content (Action Item 6 in the HTML Accessibility Task Force)
- Re: Proposal: Canvas accessibility and a media querries approach for alternative content (Action Item 6 in the HTML Accessibility Task Force)
- Re: Proposal: Canvas accessibility and a media querries approach for alternative content (Action Item 6 in the HTML Accessibility Task Force)
- Re: Proposal: Canvas accessibility and a media querries approach for alternative content (Action Item 6 in the HTML Accessibility Task Force)
- Re: Understanding the "applicable specifications" clause (was: Re: Decentralised extensibility idea (ISSUE-41))
- Re: Proposal: Canvas accessibility and a media querries approach for alternative content (Action Item 6 in the HTML Accessibility Task Force)
- Re: Proposal: Canvas accessibility and a media querries approach for alternative content (Action Item 6 in the HTML Accessibility Task Force)
- Re: Proposal: Canvas accessibility and a media querries approach for alternative content (Action Item 6 in the HTML Accessibility Task Force)
- Re: Proposal: Canvas accessibility and a media querries approach for alternative content (Action Item 6 in the HTML Accessibility Task Force)
- Re: Proposal: Canvas accessibility and a media querries approach for alternative content (Action Item 6 in the HTML Accessibility Task Force)
- Re: Understanding the "applicable specifications" clause (was: Re: Decentralised extensibility idea (ISSUE-41))
- Re: Proposal: Canvas accessibility and a media querries approach for alternative content (Action Item 6 in the HTML Accessibility Task Force)
- Re: draft HTML5: Techniques for the provision of text alternatives
- Re: Proposal: Canvas accessibility and a media querries approach for alternative content (Action Item 6 in the HTML Accessibility Task Force)
- Re: Fwd: New Version Notification - draft-nottingham-http-link-header-07.txt
- Re: Decentralized poetry markup (language)
- Understanding the "applicable specifications" clause (was: Re: Decentralised extensibility idea (ISSUE-41))
- Re: Decentralized poetry markup (language)
- Re: Proposal: Canvas accessibility and a media querries approach for alternative content (Action Item 6 in the HTML Accessibility Task Force)
- Re: HTML+RDFa Heartbeat Draft publishing request
- Re: Proposal: Canvas accessibility and a media querries approach for alternative content (Action Item 6 in the HTML Accessibility Task Force)
- Re: Disallow plug-ins in text/html-sandboxed? (was: Re: text/sandboxed-html)
- Re: Disallow plug-ins in text/html-sandboxed? (was: Re: text/sandboxed-html)
- Re: Disallow plug-ins in text/html-sandboxed? (was: Re: text/sandboxed-html)
- Re: Disallow plug-ins in text/html-sandboxed? (was: Re: text/sandboxed-html)
- Re: Disallow plug-ins in text/html-sandboxed? (was: Re: text/sandboxed-html)
- Re: Disallow plug-ins in text/html-sandboxed? (was: Re: text/sandboxed-html)
- Re: Disallow plug-ins in text/html-sandboxed? (was: Re: text/sandboxed-html)
- Re: Remove .played from media elements
- Re: Decentralized poetry markup (language)
- Re: Legacy Doctype and Doctype Versioning
- Legacy Doctype and Doctype Versioning
- Re: Change Proposals and Counter-Proposals (was Re: Issues 89 through 97)
Tuesday, 19 January 2010
- RE: Re: HTML CHANGE PROPOSAL; change definition of URL to normative reference to IRIBIS
- Re: HTML CHANGE PROPOSAL; change definition of URL to normative reference to IRIBIS
- Re: Proposal: Canvas accessibility and a media querries approach for alternative content (Action Item 6 in the HTML Accessibility Task Force)
- Re: Canvas Accessibility Next steps
- Re: Proposal: Canvas accessibility and a media querries approach for alternative content (Action Item 6 in the HTML Accessibility Task Force)
- RE: ISSUE-81: representation-vs-resource - Chairs Solicit Proposals
- RE: HTML+RDFa Heartbeat Draft publishing request
- Re: text/sandboxed-html
- Re: Decentralized poetry markup (language)
- Re: Decentralized poetry markup (language)
- Re: Decentralized poetry markup (language)
- Re: Decentralized poetry markup (language)
- Re: draft HTML5: Techniques for the provision of text alternatives
- Fw: Canvas Accessibility Next steps
- Re: Decentralized poetry markup (language)
- Re: Decentralised extensibility idea (ISSUE-41)
- Re: Decentralized poetry markup (language)
- Re: draft HTML5: Techniques for the provision of text alternatives
- Decentralized poetry markup (language) (ISSUE-41)
- Decentralized poetry markup (language)
- Re: draft HTML5: Techniques for the provision of text alternatives
- RE: Change Proposals and Counter-Proposals (was Re: Issues 89 through 97)
- Re: text/sandboxed-html
- Suggestion for Microdata to RDF conversion
- Re: draft HTML5: Techniques for the provision of text alternatives
- Re: draft HTML5: Techniques for the provision of text alternatives
- Remove .played from media elements
- Re: text/sandboxed-html
- Re: draft HTML5: Techniques for the provision of text alternatives
- Re: draft HTML5: Techniques for the provision of text alternatives
- Re: Microdata to RDF conversion
- Re: ISSUE-81: representation-vs-resource - Chairs Solicit Proposals
- Re: <iframe doc="">
- Re: <iframe doc="">
- Re: Change Proposals and Counter-Proposals (was Re: Issues 89 through 97)
- Re: <iframe doc="">
- Re: Change Proposals and Counter-Proposals (was Re: Issues 89 through 97)
- Re: Change Proposals and Counter-Proposals (was Re: Issues 89 through 97)
- Re: Change Proposals and Counter-Proposals (was Re: Issues 89 through 97)
- Re: <iframe doc="">
- Re: <iframe doc="">
- Re: The harm that can come if the W3C supports publication of competing specs
- Re: Change Proposals and Counter-Proposals (was Re: Issues 89 through 97)
- Re: The harm that can come if the W3C supports publication of competing specs
- Re: Change Proposals and Counter-Proposals (was Re: Issues 89 through 97)
- Re: Change Proposals and Counter-Proposals (was Re: Issues 89 through 97)
- Re: The harm that can come if the W3C supports publication of competing specs
- Re: Change Proposals and Counter-Proposals (was Re: Issues 89 through 97)
- Re: Change Proposals and Counter-Proposals (was Re: Issues 89 through 97)
- Re: Inadequate rationales (Was: Change Proposals and Counter-Proposals)
- Re: Inadequate rationales (Was: Change Proposals and Counter-Proposals)
- Re: Change Proposals and Counter-Proposals (was Re: Issues 89 through 97)
- Re: Inadequate rationales (Was: Change Proposals and Counter-Proposals)
- Re: Change Proposals and Counter-Proposals (was Re: Issues 89 through 97)
- Re: Inadequate rationales (Was: Change Proposals and Counter-Proposals)
- Re: Change Proposals and Counter-Proposals (was Re: Issues 89 through 97)
- Re: Change Proposals and Counter-Proposals (was Re: Issues 89 through 97)
- Inadequate rationales (Was: Change Proposals and Counter-Proposals)
- Re: Change Proposals and Counter-Proposals (was Re: Issues 89 through 97)
- Re: ISSUE-81: representation-vs-resource - Chairs Solicit Proposals
- Re: <iframe doc="">
- Re: Change Proposals and Counter-Proposals (was Re: Issues 89 through 97)
- Re: Change Proposals and Counter-Proposals (was Re: Issues 89 through 97)
- Re: <iframe doc="">
- Re: Change Proposals and Counter-Proposals (was Re: Issues 89 through 97)
- Re: Change Proposals and Counter-Proposals (was Re: Issues 89 through 97)
- Re: <iframe doc="">
Monday, 18 January 2010
- Re: <iframe doc="">
- Re: Change Proposals and Counter-Proposals (was Re: Issues 89 through 97)
- Re: Change Proposals and Counter-Proposals (was Re: Issues 89 through 97)
- Re: Change Proposals and Counter-Proposals (was Re: Issues 89 through 97)
- Re: <iframe doc="">
- Re: ISSUE-81: representation-vs-resource - Chairs Solicit Proposals
- Re: Change Proposals and Counter-Proposals (was Re: Issues 89 through 97)
- Re: Change Proposals and Counter-Proposals (was Re: Issues 89 through 97)
- Re: Minutes: HTML 5 Canvas Accessibility Call January 18, 2010 (text version)
- Re: The harm that can come if the W3C supports publication of competing specs
- Re: Change Proposals and Counter-Proposals (was Re: Issues 89 through 97)
- Re: The harm that can come if the W3C supports publication of competing specs
- Minutes: HTML 5 Canvas Accessibility Call
- Re: The harm that can come if the W3C supports publication of competing specs
- Re: text/sandboxed-html
- Re: ISSUE-81: representation-vs-resource - Chairs Solicit Proposals
- Change Proposals and Counter-Proposals (was Re: Issues 89 through 97)
- Re: <iframe doc="">
- Re: draft HTML5: Techniques for the provision of text alternatives
- Re: Decentralised extensibility idea (ISSUE-41)
- Re: text/sandboxed-html
- Re: text/sandboxed-html
- Re: text/sandboxed-html
- Re: text/sandboxed-html
- RE: ISSUE-81: representation-vs-resource - Chairs Solicit Proposals
- Re: Fieldset disabled attribute and descendants
- RE: Fieldset disabled attribute and descendants
- Re: <iframe doc="">
- Re: <iframe doc="">
- Re: draft HTML5: Techniques for the provision of text alternatives
- Re: Issues 89 through 97
- Re: <iframe doc="">
- Re: Issues 89 through 97
- Re: <iframe doc="">
- Re: Issues 89 through 97
- Re: <iframe doc="">
- Re: Decentralised extensibility idea (ISSUE-41)
- [Fwd: 2047 in 2388: encoded words in multipart/form-data]
- Re: Issues 89 through 97
- draft HTML5: Techniques for the provision of text alternatives
- Re: <iframe doc="">
- Re: Costs and Benefits of Early Implementations (was Re: The harm that can come if the W3C supports publication of competing specs)
- Re: XSS risk from iframe@doc?
- Re: XSS risk from iframe@doc?
- Re: Decentralised extensibility idea (ISSUE-41)
- Re: <iframe doc="">
- Re: XSS risk from iframe@doc?
- Re: The harm that can come if the W3C supports publication of competing specs
- Re: The harm that can come if the W3C supports publication of competing specs
- Costs and Benefits of Early Implementations (was Re: The harm that can come if the W3C supports publication of competing specs)
- Re: The harm that can come if the W3C supports publication of competing specs
- Re: <iframe doc="">
- Re: <iframe doc="">
- Re: The harm that can come if the W3C supports publication of competing specs
Sunday, 17 January 2010
- Re: Issues 89 through 97
- Re: XSS risk from iframe@doc?
- Re: XSS risk from iframe@doc?
- Re: ISSUE-81: representation-vs-resource - Chairs Solicit Proposals
- Re: Microdata to RDF conversion
- Re: <iframe doc="">
- Re: The harm that can come if the W3C supports publication of competing specs
- Re: <iframe doc="">
- Re: The harm that can come if the W3C supports publication of competing specs
- Re: XSS risk from iframe@doc?
- Re: XSS risk from iframe@doc?
- Re: <iframe doc="">
- Re: XSS risk from iframe@doc?
- Re: <iframe doc="">
- Re: XSS risk from iframe@doc?
- Re: The harm that can come if the W3C supports publication of competing specs
- Re: XSS risk from iframe@doc?
- Re: XSS risk from iframe@doc?
- Microdata to RDF conversion
- Re: ISSUE-81: representation-vs-resource - Chairs Solicit Proposals
- Re: The harm that can come if the W3C supports publication of competing specs
- XSS risk from iframe@doc?
- Re: ISSUE-95 hidden - Chairs Solicit Proposals
- Re: The harm that can come if the W3C supports publication of competing specs
- Re: ISSUE-95 hidden - Chairs Solicit Proposals
- Re: The harm that can come if the W3C supports publication of competing specs
- Re: The harm that can come if the W3C supports publication of competing specs
- Re: Decentralised extensibility idea (ISSUE-41)
- Re: <iframe doc="">
- Re: <iframe doc="">
- Re: Decentralised extensibility idea (ISSUE-41)
- Re: Decentralised extensibility idea (ISSUE-41)
- Re: Decentralised extensibility idea (ISSUE-41)
- Re: Decentralised extensibility idea (ISSUE-41)
- Re: The harm that can come if the W3C supports publication of competing specs
- Re: The harm that can come if the W3C supports publication of competing specs
- Re: <iframe doc="">
- Re: Proposal: Canvas accessibility and a media querries approach for alternative content (Action Item 6 in the HTML Accessibility Task Force)
- Re: The harm that can come if the W3C supports publication of competing specs
- Re: Issues 89 through 97
- Re: The harm that can come if the W3C supports publication of competing specs
- Re: The harm that can come if the W3C supports publication of competing specs
- Re: ISSUE-81: representation-vs-resource - Chairs Solicit Proposals
- Re: <iframe doc="">
- Re: ISSUE-81: representation-vs-resource - Chairs Solicit Proposals
- Re: ISSUE-95 hidden - Chairs Solicit Proposals
- Re: The harm that can come if the W3C supports publication of competing specs
- Re: The harm that can come if the W3C supports publication of competing specs
- Re: The harm that can come if the W3C supports publication of competing specs
- Re: <iframe doc="">
- Re: Decentralised extensibility idea (ISSUE-41)
- Re: ISSUE-95 hidden - Chairs Solicit Proposals
- Re: <iframe doc="">
- Re: <iframe doc="">
- Re: The harm that can come if the W3C supports publication of competing specs
- Re: The harm that can come if the W3C supports publication of competing specs
- Re: The harm that can come if the W3C supports publication of competing specs
- Re: <iframe doc="">
- Re: The harm that can come if the W3C supports publication of competing specs
- Re: <iframe doc="">
- Re: <iframe doc="">
- Re: Decentralised extensibility idea (ISSUE-41)
- Re: <iframe doc="">
- @profile and HTML spec experimenting
- Re: <iframe doc="">
- Re: ISSUE-81: representation-vs-resource - Chairs Solicit Proposals
- RE: The harm that can come if the W3C supports publication of competing specs
- RE: The harm that can come if the W3C supports publication of competing specs
- Re: The harm that can come if the W3C supports publication of competing specs
- Re: The harm that can come if the W3C supports publication of competing specs
- Re: Decentralised extensibility idea (ISSUE-41)
- Re: <iframe doc="">
- RE: The harm that can come if the W3C supports publication of competing specs
- Re: Decentralised extensibility idea (ISSUE-41)
- Re: ISSUE-95 hidden - Chairs Solicit Proposals
- Re: Request for group input on ISSUE-83 (figure and details captions)
- Re: ISSUE-95 hidden - Chairs Solicit Proposals
- Re: <iframe doc="">
- Re: Request for group input on ISSUE-83 (figure and details captions)
- Re: The harm that can come if the W3C supports publication of competing specs
- Re: Request for group input on ISSUE-83 (figure and details captions)
- Re: The harm that can come if the W3C supports publication of competing specs
- Re: The harm that can come if the W3C supports publication of competing specs
- Re: <iframe doc="">
- Re: Change Proposal for ISSUE-66
- Request for group input on ISSUE-83 (figure and details captions)
- Re: Issues 89 through 97
- Re: <iframe doc="">
- Re: ISSUE-95 hidden - Chairs Solicit Proposals
- RE: The harm that can come if the W3C supports publication of competing specs
- Re: <iframe doc="">
- Re: The harm that can come if the W3C supports publication of competing specs
- Re: <iframe doc="">
- Re: Decentralised extensibility idea (ISSUE-41)
- Re: The harm that can come if the W3C supports publication of competing specs
- Re: <iframe doc="">
- Re: ISSUE-95 hidden - Chairs Solicit Proposals
- Re: ISSUE-95 hidden - Chairs Solicit Proposals
- Re: <iframe doc="">
- Re: <iframe doc="">
- Re: <iframe doc="">
- Re: Decentralised extensibility idea (ISSUE-41)
- Re: Decentralised extensibility idea (ISSUE-41)
Saturday, 16 January 2010
- Re: <iframe doc="">
- Re: Decentralised extensibility idea (ISSUE-41)
- Re: Decentralised extensibility idea (ISSUE-41)
- Re: The harm that can come if the W3C supports publication of competing specs
- Re: The harm that can come if the W3C supports publication of competing specs
- Re: The harm that can come if the W3C supports publication of competing specs
- Re: The harm that can come if the W3C supports publication of competing specs
- Re: <iframe doc="">
- Re: The harm that can come if the W3C supports publication of competing specs
- Re: Decentralised extensibility idea (ISSUE-41)
- The harm that can come if the W3C supports publication of competing specs
- Re: <iframe doc="">
- Re: Issue 83 Change Proposal - caption attribute
- Re: <iframe doc="">
- Re: Decentralised extensibility idea (ISSUE-41)
- Re: <iframe doc="">
- Re: Issue 83 Change Proposal - caption attribute
- Re: Issues 89 through 97
- Re: <iframe doc="">
- Re: <iframe doc="">
- Re: <iframe doc="">
- Re: <iframe doc="">
- Re: <iframe doc="">
- Re: ISSUE-95 hidden - Chairs Solicit Proposals
Friday, 15 January 2010
- Re: hidden versus discoverable meta-data
- Re: Issue 83 Change Proposal - caption attribute
- Change Proposal for ISSUE-66
- Re: hidden versus discoverable meta-data
- Re: hidden versus discoverable meta-data
- Re: Decentralised extensibility idea (ISSUE-41)
- Re: Proposal: Canvas accessibility and a media querries approach for alternative content (Action Item 6 in the HTML Accessibility Task Force)
- Re: Proposal: Canvas accessibility and a media querries approach for alternative content (Action Item 6 in the HTML Accessibility Task Force)
- Re: text/sandboxed-html
- Re: Decentralised extensibility idea (ISSUE-41)
- Re: text/sandboxed-html
- Re: text/sandboxed-html
- Re: text/sandboxed-html
- Re: text/sandboxed-html
- Re: Issues 89 through 97
- Re: Decentralised extensibility idea (ISSUE-41)
- Issues 89 through 97
- Re: Decentralised extensibility idea (ISSUE-41)
- Re: Decentralised extensibility idea (ISSUE-41)
- Re: Decentralised extensibility idea (ISSUE-41)
- Re: Decentralised extensibility idea (ISSUE-41)
- Re: Decentralised extensibility idea (ISSUE-41)
- Re: Decentralised extensibility idea (ISSUE-41)
- Re: Decentralised extensibility idea (ISSUE-41)
- Re: Decentralised extensibility idea (ISSUE-41)
- Re: Decentralised extensibility idea (ISSUE-41)
- Re: Decentralised extensibility idea (ISSUE-41)
- Re: Decentralised extensibility idea (ISSUE-41)
- Re: text/sandboxed-html
- Re: <iframe doc="">
- Re: ISSUE-95 hidden - Chairs Solicit Proposals
- Re: ISSUE-95 hidden - Chairs Solicit Proposals
- Re: ISSUE-95 hidden - Chairs Solicit Proposals
- Re: text/sandboxed-html
- Re: Decentralised extensibility idea (ISSUE-41)
- Re: text/sandboxed-html
- Re: ISSUE-95 hidden - Chairs Solicit Proposals
- Re: <iframe doc="">
- Re: Decentralised extensibility idea (ISSUE-41)
- Re: ITS in html Re: HTML+RDFa Heartbeat Draft publishing request
- Re: <iframe doc="">
- Re: <iframe doc="">
- Re: Decentralised extensibility idea (ISSUE-41)
- Re: (not really) Re: Alternate proposals for ISSUE-83
- Re: <iframe doc="">
- Re: <iframe doc="">
- Re: Alternate proposals for ISSUE-83
- (not really) Re: Alternate proposals for ISSUE-83
- Re: <iframe doc="">
- Re: <iframe doc="">
- Re: Alternate proposals for ISSUE-83
- Re: <iframe doc="">
- Re: <iframe doc="">
- Re: Alternate proposals for ISSUE-83
- [Bug 8736] Decision to playback for media should be left to the user agent
- [Bug 8659] Media events to indicate captions and audio descriptions
- [Bug 8658] Availability of captions or additional audio tracks
- Re: <iframe doc="">
- [Bug 8657] Allow UA to reload fallback content if it fails to load
- [Bug 8187] Section 4.8.7 on video makes no reference to audio description
- [Bug 5758] insufficient accessibility fallback for <audio> or <video>
- Re: Alternate proposals for ISSUE-83
- ITS in html Re: HTML+RDFa Heartbeat Draft publishing request
- Re: ISSUE-95 hidden - Chairs Solicit Proposals
Thursday, 14 January 2010
- Re: Alternate proposals for ISSUE-83
- Re: Alternate proposals for ISSUE-83
- Re: hidden versus discoverable meta-data
- Re: Alternate proposals for ISSUE-83
- Re: hidden versus discoverable meta-data
- Decentralised extensibility idea (ISSUE-41)
- Re: Alternate proposals for ISSUE-83
- Re: Alternate proposals for ISSUE-83
- Re: Alternate proposals for ISSUE-83
- Re: Alternate proposals for ISSUE-83
- Re: ISSUE-95 hidden - Chairs Solicit Proposals
- Re: <iframe doc="">
- Re: ISSUE-95 hidden - Chairs Solicit Proposals
- Re: <iframe doc="">
- Re: <iframe doc="">
- Re: Chairs Solicit Proposals for 89, 90, 91, 92, 95 **CORRECTION**
- Re: <iframe doc="">
- Re: Alternate proposals for ISSUE-83
- Re: Alternate proposals for ISSUE-83
- Re: hidden versus discoverable meta-data
- Re: <iframe doc="">
- Re: hidden versus discoverable meta-data
- Re: hidden versus discoverable meta-data
- Re: Alternate proposals for ISSUE-83
- Re: Alternate proposals for ISSUE-83
- RE: hidden versus discoverable meta-data
- Re: Alternate proposals for ISSUE-83
- Re: Proposal: Canvas accessibility and a media querries approach for alternative content (Action Item 6 in the HTML Accessibility Task Force)
- Re: hidden versus discoverable meta-data
- Re: Proposal: Canvas accessibility and a media querries approach for alternative content (Action Item 6 in the HTML Accessibility Task Force)
- Re: <iframe doc="">
- Alternate proposals for ISSUE-83
- ISSUE-84 / ISSUE-4 Change Proposal (was Re: {agenda} HTML WG telecon 2010-01-07)
- Re: hidden versus discoverable meta-data
- Re: ISSUE-1 and ISSUE-2 - Chairs Solicit Alternate Proposals or Counter-Proposals
- Re: Proposal: Canvas accessibility and a media querries approach for alternative content (Action Item 6 in the HTML Accessibility Task Force)
- Re: ISSUE-30: longdesc - Chairs Solicit Alternate Proposals or Counter-Proposals
- Re: <iframe doc="">
- Re: Chairs Solicit Proposals for 89, 90, 91, 92, 95 **CORRECTION**
- RE: hidden versus discoverable meta-data
- hidden versus discoverable meta-data
- Re: ISSUE-79: meta-keywords - Chairs Solicit Proposals
- Re: Proposal: Canvas accessibility and a media querries approach for alternative content (Action Item 6 in the HTML Accessibility Task Force)
- Re: Fw: Proposal: Canvas accessibility and a media querries approach for alternative content (Action Item 6 in the HTML Accessibility Task Force)
- Re: Dublin Core review of HTML5
- order of arguments in window.postMessage()
- Re: Dublin Core review of HTML5
- Re: Dublin Core review of HTML5
- Call for Exclusions (Update): HTML+RDFa
- RE: {agenda} HTML WG telecon 2010-01-07
- Dublin Core review of HTML5
- Re: Proposal: Canvas accessibility and a media querries approach for alternative content (Action Item 6 in the HTML Accessibility Task Force)
- Re: Proposal: Canvas accessibility and a media querries approach for alternative content (Action Item 6 in the HTML Accessibility Task Force)
- Re: Proposal: Canvas accessibility and a media querries approach for alternative content (Action Item 6 in the HTML Accessibility Task Force)
- Re: Proposal: Canvas accessibility and a media querries approach for alternative content (Action Item 6 in the HTML Accessibility Task Force)
Wednesday, 13 January 2010
- Re: Fieldset disabled attribute and descendants
- Re: ISSUE-1 and ISSUE-2 - Chairs Solicit Alternate Proposals or Counter-Proposals
- Re: ISSUE-1 and ISSUE-2 - Chairs Solicit Alternate Proposals or Counter-Proposals
- Re: ISSUE-1 and ISSUE-2 - Chairs Solicit Alternate Proposals or Counter-Proposals
- Re: ISSUE-83 alternate Change Proposal - fcaption and dlabel elements (or similar)
- Issue 83 Change Proposal - <fbody>, <dbody>
- Re: Disallow plug-ins in text/html-sandboxed? (was: Re: text/sandboxed-html)
- Re: ISSUE-83 alternate Change Proposal - fcaption and dlabel elements (or similar)
- ISSUE-83 alternate Change Proposal - fcaption and dlabel elements (or similar)
- Re: HTML+RDFa Heartbeat Draft publishing request
- Issue 83 Change Proposal - caption attribute
- Re: <iframe doc="">
- Re: <iframe doc="">
- Re: text/sandboxed-html
- Re: charter and votes to publish documents
- RE: Disallow plug-ins in text/html-sandboxed? (was: Re: text/sandboxed-html)
- RE: text/sandboxed-html
- Re: HTML+RDFa Heartbeat Draft publishing request
- Disallow plug-ins in text/html-sandboxed? (was: Re: text/sandboxed-html)
- Re: Fieldset disabled attribute and descendants
- Re: text/sandboxed-html
- Re: text/sandboxed-html
- Re: text/sandboxed-html
- Re: text/sandboxed-html
- Fieldset disabled attribute and descendants
- Publishing HTML+RDFa WD
- [Bug 8404] Refocus the figure element back to being a figure
- [Bug 8449] Remove extraneous material from Table section
- [Bug 8379] Remove Section 4.11.1 The Details Element
- charter and votes to publish documents
- Re: ISSUE-79: meta-keywords - Chairs Solicit Proposals
- Re: ISSUE-30: longdesc - Chairs Solicit Alternate Proposals or Counter-Proposals
- Re: ISSUE-30: longdesc - Chairs Solicit Alternate Proposals or Counter-Proposals
- Re: ISSUE-30: longdesc - Chairs Solicit Alternate Proposals or Counter-Proposals
- ISSUE-30: longdesc - Chairs Solicit Alternate Proposals or Counter-Proposals
- ISSUE-1 and ISSUE-2 - Chairs Solicit Alternate Proposals or Counter-Proposals
- Re: text/sandboxed-html
- RE: text/sandboxed-html
- Chairs Solicit Proposals for 89, 90, 91, 92, 95 **CORRECTION**
- ISSUE-95 hidden - Chairs Solicit Proposals
- Re: HTML+RDFa Heartbeat Draft publishing request
- ISSUE-92 cleanuptable - Chairs Solicit Proposals
- ISSUE-91 aside - Chairs Solicit Proposals
- ISSUE-90 figure - Chairs Solicit Proposals
- Re: text/sandboxed-html
- ISSUE-89 idioms - Chairs Solicit Proposals
- Re: HTML+RDFa Heartbeat Draft publishing request
- Re: <iframe doc="">
- Re: CHANGE PROPOSAL: Remove ping and hyperlink auditing (ISSUE-1 and ISSUE-2)
- Re: text/sandboxed-html
- RE: <iframe doc="">
- RE: text/sandboxed-html
- Re: HTML+RDFa Heartbeat Draft publishing request
- Re: CHANGE PROPOSAL: Remove ping and hyperlink auditing (ISSUE-1 and ISSUE-2)
- Re: HTML+RDFa Heartbeat Draft publishing request
- Re: Should <video> buffer control be tri-state?
- Re: text/sandboxed-html
- Re: text/sandboxed-html
- Re: text/sandboxed-html
- Re: Getting lots of out-of-process plugin hangs
- Getting lots of out-of-process plugin hangs
- RE: HTML+RDFa Heartbeat Draft publishing request
- Re: text/sandboxed-html
- Re: text/sandboxed-html
- Re: text/sandboxed-html
- Re: text/sandboxed-html
- Re: text/sandboxed-html
- Re: text/sandboxed-html
- Re: <iframe doc="">
- Re: ISSUE-81: representation-vs-resource - Chairs Solicit Proposals
- Re: text/sandboxed-html
- Re: text/sandboxed-html
- Re: <iframe doc="">
- Re: text/sandboxed-html
- Re: text/sandboxed-html
- Re: text/sandboxed-html
- Re: <iframe doc="">
- <iframe doc="">
- text/sandboxed-html
Tuesday, 12 January 2010
- Re: CHANGE PROPOSAL: Remove ping and hyperlink auditing (ISSUE-1 and ISSUE-2)
- Re: Fw: Proposal: Canvas accessibility and a media querries approach for alternative content (Action Item 6 in the HTML Accessibility Task Force)
- Re: New split-out drafts
- Re: CfC: Publish HTML5 Microdata as First Public Working Draft and a new HTML5 Working Draft
- Re: New split-out drafts
- Re: HTML+RDFa Heartbeat Draft publishing request
- Re: CfC: Publish HTML5 Microdata as First Public Working Draft and a new HTML5 Working Draft
- Re: HTML+RDFa Heartbeat Draft publishing request
- Re: HTML+RDFa Heartbeat Draft publishing request
- HTML+RDFa Heartbeat Draft publishing request
- Re: CfC: Publish HTML5 Microdata as First Public Working Draft and a new HTML5 Working Draft
- Re: CfC: Publish HTML5 Microdata as First Public Working Draft and a new HTML5 Working Draft
- Re: CfC: Publish HTML5 Microdata as First Public Working Draft and a new HTML5 Working Draft
- Re: CfC: Publish HTML5 Microdata as First Public Working Draft and a new HTML5 Working Draft
- Re: CfC: Publish HTML5 Microdata as First Public Working Draft and a
- Re: Registries, meta/name=keyword, head/@profile (ISSUE-27, ISSUE-55 and ISSUE-79)
- Registries, meta/name=keyword, head/@profile (ISSUE-27, ISSUE-55 and ISSUE-79)
- Re: CfC: Publish HTML5 Microdata as First Public Working Draft and a new HTML5 Working Draft
- 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: CfC: Publish HTML5 Microdata as First Public Working Draft and a new HTML5 Working Draft
- Re: ISSUE-74: canvas-accessibility - Chairs Solicit Proposals
- Re: ISSUE-88: content-language-multiple - Chairs Solicit Proposals
- Re: CfC: Publish HTML5 Microdata as First Public Working Draft and a new HTML5 Working Draft
- Re: Work on Alternate Proposals for ISSUE-83 dt-dd-semantics
- Re: Work on Alternate Proposals for ISSUE-83 dt-dd-semantics
- Re: CfC: Publish HTML5 Microdata as First Public Working Draft and a new HTML5 Working Draft
- Re: Fw: Proposal: Canvas accessibility and a media querries approach for alternative content (Action Item 6 in the HTML Accessibility Task Force)
- RE: The Canvas 2D API split
- Re: CfC: Publish HTML5 Microdata as First Public Working Draft and a new HTML5 Working Draft
- Re: CfC: Publish HTML5 Microdata as First Public Working Draft and a new HTML5 Working Draft
- Re: CfC: Publish HTML5 Microdata as First Public Working Draft and a new HTML5 Working Draft
- Re: CfC: Publish HTML5 Microdata as First Public Working Draft and a new HTML5 Working Draft
- Re: CfC: Publish HTML5 Microdata as First Public Working Draft and a new HTML5 Working Draft
Monday, 11 January 2010
- Re: Work on Alternate Proposals for ISSUE-83 dt-dd-semantics
- Re: Work on Alternate Proposals for ISSUE-83 dt-dd-semantics
- Work on Alternate Proposals for ISSUE-83 dt-dd-semantics
- Re: CfC: Publish HTML5 Microdata as First Public Working Draft and a new HTML5 Working Draft
- Re: CfC: Publish HTML5 Microdata as First Public Working Draft and a new HTML5 Working Draft
- Re: The Canvas 2D API split
- Re: CfC: Publish HTML5 Microdata as First Public Working Draft and a new HTML5 Working Draft
- Re: CfC: Publish HTML5 Microdata as First Public Working Draft and a new HTML5 Working Draft
- Re: CfC: Publish HTML5 Microdata as First Public Working Draft and a new HTML5 Working Draft
- RE: The Canvas 2D API split
- Re: The Canvas 2D API split
- Re: The Canvas 2D API split
- Re: The Canvas 2D API split
- Re: The Canvas 2D API split
- Re: The Canvas 2D API split
- Re: New split-out drafts vs. modular design
- Re: The Canvas 2D API split
- Re: The Canvas 2D API split
- Re: The Canvas 2D API split
- Re: The Canvas 2D API split
- [Bug 8331] Move the Canvas 2D context API into a separate spec
- Re: The Canvas 2D API split
- [Bug 8331] Move the Canvas 2D context API into a separate spec
- Re: CfC: Publish HTML5 Microdata as First Public Working Draft and a new HTML5 Working Draft
- Thanks Maciej!
- Re: The Canvas 2D API split
- [Bug 8555] Remove the Meter Element
- [Bug 8552] Remove the Progress Element
- [Bug 8118] Remove the Hidden Attribute
- [Bug 7386] SharedWorkerGlobalScope
- Re: The Canvas 2D API split
- Re: CfC: Publish HTML5 Microdata as First Public Working Draft and a new HTML5 Working Draft
- Re: The Canvas 2D API split
- Re: New split-out drafts vs. modular design
- Re: New split-out drafts vs. modular design
- Re: New split-out drafts vs. modular design
- Re: New split-out drafts vs. modular design
- Re: CfC: Publish HTML5 Microdata as First Public Working Draft and a new HTML5 Working Draft
- Re: The Canvas 2D API split
- Re: New split-out drafts
- Re: CfC: Publish HTML5 Microdata as First Public Working Draft and a new HTML5 Working Draft
- Re: Splitting out Communication Section
- Re: CfC: Publish HTML5 Microdata as First Public Working Draft and a new HTML5 Working Draft
- Re: New split-out drafts
- Re: CfC: Publish HTML5 Microdata as First Public Working Draft and a new HTML5 Working Draft
- Re: New split-out drafts vs. modular design
- Re: CfC: Publish HTML5 Microdata as First Public Working Draft and a new HTML5 Working Draft
- Re: CfC: Publish HTML5 Microdata as First Public Working Draft and a new HTML5 Working Draft
- Re: CfC: Publish HTML5 Microdata as First Public Working Draft and a new HTML5 Working Draft
- Re: New split-out drafts vs. modular design
- Re: CfC: Publish HTML5 Microdata as First Public Working Draft and a new HTML5 Working Draft
- Re: CfC: Publish HTML5 Microdata as First Public Working Draft and a new HTML5 Working Draft
- Re: New split-out drafts vs. modular design
- Re: New split-out drafts vs. modular design
- Re: New split-out drafts vs. modular design
- Re: New split-out drafts vs. modular design
- Re: New split-out drafts vs. modular design
- Re: New split-out drafts vs. modular design
- Re: CfC: Publish HTML5 Microdata as First Public Working Draft and a new HTML5 Working Draft
Sunday, 10 January 2010
- Re: New split-out drafts
- Re: New split-out drafts vs. modular design
- Re: CfC: Publish HTML5 Microdata as First Public Working Draft and a new HTML5 Working Draft
- Re: CfC: Publish HTML5 Microdata as First Public Working Draft and a new HTML5 Working Draft
- Re: details should be a child
- Re: CfC: Publish HTML5 Microdata as First Public Working Draft and a new HTML5 Working Draft
- Splitting out Communication Section
- The Canvas 2D API split
- Re: New split-out drafts
- new bug add conformance criteria info to header/banner
- Re: Should <video> buffer control be tri-state?
- Re: splits, discussions, and manic behavior
- Re: New split-out drafts vs. modular design
- Re: New split-out drafts vs. modular design
- Re: Fw: Proposal: Canvas accessibility and a media querries approach for alternative content (Action Item 6 in the HTML Accessibility Task Force)
- Re: Should <video> buffer control be tri-state?
- Re: Fw: Proposal: Canvas accessibility and a media querries approach for alternative content (Action Item 6 in the HTML Accessibility Task Force)
- Re: Should <video> buffer control be tri-state?
- Re: New split-out drafts vs. modular design
- Re: Should <video> buffer control be tri-state?
- Re: Should <video> buffer control be tri-state?
- details should be a child
- Re: Fw: Proposal: Canvas accessibility and a media querries approach for alternative content (Action Item 6 in the HTML Accessibility Task Force)
- RE: New split-out drafts vs. modular design
- Re: splits, discussions, and manic behavior
- Re: New split-out drafts
Saturday, 9 January 2010
- Re: New split-out drafts
- Re: splits, discussions, and manic behavior
- Re: New split-out drafts
- Re: ISSUE-27: rel-ownership - Chairs Solicit Proposals
- Re: New split-out drafts
- Re: splits, discussions, and manic behavior
- Re: New split-out drafts
- Re: splits, discussions, and manic behavior
- Re: splits, discussions, and manic behavior
- Re: CfC: Publish HTML5 Microdata as First Public Working Draft and a new HTML5 Working Draft
- Re: splits, discussions, and manic behavior
- Re: splits, discussions, and manic behavior
- Re: splits, discussions, and manic behavior
- RE: CfC: Publish HTML5 Microdata as First Public Working Draft and a new HTML5 Working Draft
- Re: splits, discussions, and manic behavior
- Re: Should <video> buffer control be tri-state?
- Re: sections removed, current and ongoing
- Re: sections removed, current and ongoing
- Re: splits, discussions, and manic behavior
- Re: splits, discussions, and manic behavior
- Re: New split-out drafts
- Re: sections removed, current and ongoing
- [Bug 8365] Remove the Web Browsers Section 5
- Re: splits, discussions, and manic behavior
- Re: CfC: Publish HTML5 Microdata as First Public Working Draft and a new HTML5 Working Draft
- Re: New split-out drafts
- Re: splits, discussions, and manic behavior
- splits, discussions, and manic behavior
- Re: sections removed, current and ongoing
- Re: sections removed, current and ongoing
- Re: [Bug 8365] Remove the Web Browsers Section 5
- Re: New split-out drafts
- Re: ISSUE-93 (details): Return Details Element [HTML 5 spec]
Friday, 8 January 2010
- Re: ISSUE-93 (details): Return Details Element [HTML 5 spec]
- Re: ISSUE-93 (details): Return Details Element [HTML 5 spec]
Saturday, 9 January 2010
- Re: New split-out drafts
- Re: New split-out drafts
- Re: New split-out drafts
- Re: New split-out drafts
- Re: New split-out drafts
- Re: New split-out drafts
- Re: New split-out drafts
- Re: New split-out drafts
- Re: CfC: Publish HTML5 Microdata as First Public Working Draft and a new HTML5 Working Draft
- Re: CfC: Publish HTML5 Microdata as First Public Working Draft and a new HTML5 Working Draft
- Re: CfC: Publish HTML5 Microdata as First Public Working Draft and a new HTML5 Working Draft
- Re: New split-out drafts
- Re: CfC: Publish HTML5 Microdata as First Public Working Draft and a new HTML5 Working Draft
- Re: New split-out drafts
- Re: New split-out drafts
- New split-out drafts
Friday, 8 January 2010
- Re: CfC: Publish HTML5 Microdata as First Public Working Draft and a new HTML5 Working Draft
- Re: Fw: Proposal: Canvas accessibility and a media querries approach for alternative content (Action Item 6 in the HTML Accessibility Task Force)
- Re: Fw: Proposal: Canvas accessibility and a media querries approach for alternative content (Action Item 6 in the HTML Accessibility Task Force)
- RE: CfC: Publish HTML5 Microdata as First Public Working Draft and a new HTML5 Working Draft
- RE: Publish HTML5 Microdata as First Public Working Draft and a new HTML5 Working Draft
- Re: Should <video> buffer control be tri-state?
- Re: Should <video> buffer control be tri-state?
- Re: remove the meter element
- Re: remove the meter element
- Re: Should <video> buffer control be tri-state?
- Re: CfC: Publish HTML5 Microdata as First Public Working Draft and a new HTML5 Working Draft
- Re: ISSUE-93 (details): Return Details Element [HTML 5 spec]
- Re: Fw: Proposal: Canvas accessibility and a media querries approach for alternative content (Action Item 6 in the HTML Accessibility Task Force)
- Re: remove the meter element
- Re: ISSUE-93 (details): Return Details Element [HTML 5 spec]
- Re: ISSUE-93 (details): Return Details Element [HTML 5 spec]
- Re: Fw: Proposal: Canvas accessibility and a media querries approach for alternative content (Action Item 6 in the HTML Accessibility Task Force)
- Re: ISSUE-93 (details): Return Details Element [HTML 5 spec]
- Re: remove the meter element
- Re: ISSUE-93 (details): Return Details Element [HTML 5 spec]
- Re: sections removed, current and ongoing
- Re: Removing Sections
- Re: Should <video> buffer control be tri-state?
- Re: ISSUE-93 (details): Return Details Element [HTML 5 spec]
- Re: Updated DOCTYPE versioning change proposal (ISSUE-4)
- label is now associated with progress and meter
- Re: ISSUE-93 (details): Return Details Element [HTML 5 spec]
- Re: sections removed, current and ongoing
- Re: sections removed, current and ongoing
- Re: sections removed, current and ongoing
- Re: ISSUE-93 (details): Return Details Element [HTML 5 spec]
- Re: ISSUE-93 (details): Return Details Element [HTML 5 spec]
- Re: sections removed, current and ongoing
- Re: sections removed, current and ongoing
- Re: ISSUE-93 (details): Return Details Element [HTML 5 spec]
- Re: ISSUE-93 (details): Return Details Element [HTML 5 spec]
- Re: remove the meter element
- remove the meter element
- Re: sections removed, current and ongoing
- remove the progress element
- Remove Hidden Attribute
- Re: ISSUE-93 (details): Return Details Element [HTML 5 spec]
- Re: ISSUE-93 (details): Return Details Element [HTML 5 spec]
- Re: sections removed, current and ongoing
- Re: sections removed, current and ongoing
- Re: sections removed, current and ongoing
- Re: sections removed, current and ongoing
- Re: sections removed, current and ongoing
- [Bug 8379] Remove Section 4.11.1 The Details Element
- Re: sections removed, current and ongoing
- [Bug 8449] Remove extraneous material from Table section
- Re: sections removed, current and ongoing
- [Bug 8447] Tighter definition on the aside element
- Re: Removing Sections
- [Bug 8404] Refocus the figure element back to being a figure
- Re: CfC: Publish HTML5 Microdata as First Public Working Draft and a new HTML5 Working Draft
- sections removed, current and ongoing
- Re: Removing Sections
- Re: Removing Sections
- [Bug 8401] Remove section 4.12 regarding idioms
- Removing Sections
- Re: Taking another round at @summary
- Re: CfC: Publish HTML5 Microdata as First Public Working Draft and a new HTML5 Working Draft
- Re: Taking another round at @summary
- Re: CfC: Publish HTML5 Microdata as First Public Working Draft and a new HTML5 Working Draft
- Re: Taking another round at @summary
- [Bug 8449] Remove extraneous material from Table section
- Re: CfC: Publish HTML5 Microdata as First Public Working Draft and a new HTML5 Working Draft
- [Bug 8447] Tighter definition on the aside element
- [Bug 8404] Refocus the figure element back to being a figure
- [Bug 8401] Remove section 4.12 regarding idioms
- Re: polyglot XHTML/HTML and <!DOCTYPE html about:legacy-compat>
- Re: CfC: Publish HTML5 Microdata as First Public Working Draft and a new HTML5 Working Draft
- Re: Should <video> buffer control be tri-state?
- Re: Should <video> buffer control be tri-state?
- Re: Should <video> buffer control be tri-state?
- Re: Should <video> buffer control be tri-state?
- Re: Should <video> buffer control be tri-state?
- Re: CfC: Publish HTML5 Microdata as First Public Working Draft and a new HTML5 Working Draft
- RE: Publish HTML5 Microdata as First Public Working Draft and a new HTML5 Working Draft
- Re: CfC: Publish HTML5 Microdata as First Public Working Draft and a new HTML5 Working Draft
- Re: CfC: Publish HTML5 Microdata as First Public Working Draft and a new HTML5 Working Draft
- Re: Working Group Decision on ISSUE-76 Microdata/RDFa
- CfC: Publish HTML5 Microdata as First Public Working Draft and a new HTML5 Working Draft
- Re: Fw: Proposal: Canvas accessibility and a media querries approach for alternative content (Action Item 6 in the HTML Accessibility Task Force)
- Re: Taking another round at @summary
- Re: Working Group Decision on ISSUE-76 Microdata/RDFa
- RE: Updated DOCTYPE versioning change proposal (ISSUE-4)
- Re: Should <video> buffer control be tri-state?
- [Bug 7510] Allow elements beyond just HTML, MathML, and SVG into SVG element
- RE: Taking another round at @summary
- Re: Should <video> buffer control be tri-state?
- Re: Should <video> buffer control be tri-state?
- Re: Taking another round at @summary
Thursday, 7 January 2010
- Re: Should <video> buffer control be tri-state?
- Re: Should <video> buffer control be tri-state?
- Re: Working Group Decision on ISSUE-76 Microdata/RDFa
- Re: Fw: Proposal: Canvas accessibility and a media querries approach for alternative content (Action Item 6 in the HTML Accessibility Task Force)
- Fw: Proposal: Canvas accessibility and a media querries approach for alternative content (Action Item 6 in the HTML Accessibility Task Force)
- Re: [Bug 8671] Requiring the label attribute
- [Bug 7542] Remove Section 5. Microdata
- Working Group Decision on ISSUE-76 Microdata/RDFa
- [Bug 8671] Requiring the label attribute
- [Bug 8674] Add popup as a value for the type attribute for menu element
- RE: ISSUE-27: rel-ownership - Chairs Solicit Proposals
- ACTION-166: Recheck status of issues 10 and 73
- obsoleting and the text/html MIME type (re Taking another round at @summary)
- Proposed accessible name and description calculations for TABLE markup
- RE: Taking another round at @summary
- Re: Taking another round at @summary
- RE: Taking another round at @summary
Wednesday, 6 January 2010
- Re: ISSUE-81: representation-vs-resource - Chairs Solicit Proposals
- RE: Taking another round at @summary
- Re: ISSUE-88: content-language-multiple - Chairs Solicit Proposals
- Re: "HTML5, it is a changin" performed
- Re: Taking another round at @summary
- Re: Taking another round at @summary
- Re: Taking another round at @summary
- Re: Taking another round at @summary
- Re: Taking another round at @summary
- Re: Taking another round at @summary
- Re: Taking another round at @summary
- Re: Taking another round at @summary
- RE: Taking another round at @summary
- "HTML5, it is a changin" performed
- Re: HTML5 Recommendation Additions for Integrating X3D Graphics
- Re: Taking another round at @summary
- Re: Browser implementations, prior to rec, used for justification
- Re: [Bug 8611] Consider adding a full schema to H:TML
- Re: Browser implementations, prior to rec, used for justification
- Re: Taking another round at @summary
- Re: Taking another round at @summary
- Re: Should <video> buffer control be tri-state?
- Re: Should <video> buffer control be tri-state?
- RE: Browser implementations, prior to rec, used for justification
- Re: Taking another round at @summary
- Re: Taking another round at @summary
- Re: Taking another round at @summary
- Re: Taking another round at @summary
- Re: Taking another round at @summary
- Re: Taking another round at @summary
- Re: [Bug 8611] Consider adding a full schema to H:TML
- Re: [Bug 8611] Consider adding a full schema to H:TML
- Re: Taking another round at @summary
- Re: [Bug 8611] Consider adding a full schema to H:TML
- Re: [Bug 8611] Consider adding a full schema to H:TML
- Re: [Bug 8611] Consider adding a full schema to H:TML
- Re: Taking another round at @summary
- Re: Taking another round at @summary
- Re: Taking another round at @summary
- Re: Taking another round at @summary
- RE: Taking another round at @summary
- Re: Should <video> buffer control be tri-state?
- Re: Should <video> buffer control be tri-state?
- Re: Should <video> buffer control be tri-state?
- RE: Microdata
- Re: Should <video> buffer control be tri-state?
- Re: Should <video> buffer control be tri-state?
- Re: Should <video> buffer control be tri-state?
- Re: Should <video> buffer control be tri-state?
Tuesday, 5 January 2010
- Bob Dylan meets HTML5
- Re: Taking another round at @summary
- Re: Should <video> buffer control be tri-state?
- Re: Taking another round at @summary
- Re: Taking another round at @summary
- Re: [Bug 8611] Consider adding a full schema to H:TML
- RE: Browser implementations, prior to rec, used for justification
- Re: Taking another round at @summary
- Re: Taking another round at @summary
- HTML5 Recommendation Additions for Integrating X3D Graphics
- Microdata
- Re: Browser implementations, prior to rec, used for justification
- Re: Browser implementations, prior to rec, used for justification
- Re: [Bug 8611] Consider adding a full schema to H:TML
- Re: Should <video> buffer control be tri-state?
- Re: Browser implementations, prior to rec, used for justification
- Taking another round at @summary
- Taking another round at @summary
- Re: Browser implementations, prior to rec, used for justification
- Re: Should <video> buffer control be tri-state?
- Re: Browser implementations, prior to rec, used for justification
- Re: Should <video> buffer control be tri-state?
- Re: Should <video> buffer control be tri-state?
- RE: Browser implementations, prior to rec, used for justification
- Re: "Controlled environments" in scope for HTML working group
- Recently resolved issues
- Re: "Controlled environments" in scope for HTML working group
- Re: "Controlled environments" in scope for HTML working group
- Re: Browser implementations, prior to rec, used for justification
- Re: Browser implementations, prior to rec, used for justification
- Re: Browser implementations, prior to rec, used for justification
- Re: Should <video> buffer control be tri-state?
- Re: Browser implementations, prior to rec, used for justification
- Re: aged bugs
- Re: Should <video> buffer control be tri-state?
- Re: Browser implementations, prior to rec, used for justification
Wednesday, 6 January 2010
Tuesday, 5 January 2010
- Re: Browser implementations, prior to rec, used for justification
- Re: Browser implementations, prior to rec, used for justification
- Re: Should <video> buffer control be tri-state?
- Re: Browser implementations, prior to rec, used for justification
- Re: Browser implementations, prior to rec, used for justification
- Re: Should <video> buffer control be tri-state?
- Re: Should <video> buffer control be tri-state?
- Re: Browser implementations, prior to rec, used for justification
- Re: Should <video> buffer control be tri-state?
- Re: Should <video> buffer control be tri-state?
- Re: Browser implementations, prior to rec, used for justification
- Re: Browser implementations, prior to rec, used for justification
- Re: Browser implementations, prior to rec, used for justification
- Re: Browser implementations, prior to rec, used for justification
- Re: Browser implementations, prior to rec, used for justification
- Re: Browser implementations, prior to rec, used for justification
- Re: Should <video> buffer control be tri-state?
- Re: Browser implementations, prior to rec, used for justification
- Browser implementations, prior to rec, used for justification
- RE: Should <video> buffer control be tri-state?
- [Bug 8246] what about IE parsing problems? http://html5doctor.com/dd-details-wrong-again/
Monday, 4 January 2010
- Re: Public feedback on HTML5 video
- Re: aged bugs
- [Bug 8118] Remove the Hidden Attribute
- Re: aged bugs
- Re: Public feedback on HTML5 video
- Re: Should <video> buffer control be tri-state?
- Re: "Controlled environments" in scope for HTML working group
- Re: "Controlled environments" in scope for HTML working group
- Re: aged bugs
- Re: Public feedback on HTML5 video
- Re: aged bugs
- Re: aged bugs
- Re: "vastly increases reverse-engineering costs" and version proposal
- Re: ISSUE-87: attr-normalization - Chairs Solicit Proposals
- Re: aged bugs
- Re: ISSUE-87: attr-normalization - Chairs Solicit Proposals
- aged bugs
- Re: Public feedback on HTML5 video
- Re: CfC: Close ISSUE-35 aria-processing (ends 2009-12-17)
- Re: Public feedback on HTML5 video
- Re: Public feedback on HTML5 video
- [Bug 8623] Graceful degradation when using the style element
- [Bug 8622] Activation behaviour and pre-click activation
- [Bug 8621] Orphan nodes in content models
- [Bug 8620] No concept of interoperability beyond the site
- [Bug 8619] Problematic for assistive technologies
- [Bug 8617] Purpose of the icon attribute
- Re: CfC: Close ISSUE-35 aria-processing (ends 2009-12-17)
- Re: Public feedback on HTML5 video
- Re: Public feedback on HTML5 video
- Re: Should <video> buffer control be tri-state?
- Re: Should <video> buffer control be tri-state?
- Re: polyglot XHTML/HTML and <!DOCTYPE html about:legacy-compat>
- Re: Should <video> buffer control be tri-state?
- Re: Should <video> buffer control be tri-state?
- [Bug 8611] Consider adding a full schema to H:TML
- Re: CfC: Close ISSUE-35 aria-processing (ends 2009-12-17)
- Re: ISSUE-87: attr-normalization - Chairs Solicit Proposals
- Re: CfC: Close ISSUE-73 predefined-voc (ends 2009-12-17)
- Re: ISSUE-10: video-smil - Chairs Solicit Proposals
- Re: Should <video> buffer control be tri-state?
- Re: Updated DOCTYPE versioning change proposal (ISSUE-4)
- Re: Should <video> buffer control be tri-state?
- Re: Should <video> buffer control be tri-state?
- Re: Updated DOCTYPE versioning change proposal (ISSUE-4)
- Re: Should <video> buffer control be tri-state?
- Re: ISSUE-30 (Longdesc) Change Proposal
- Re: Updated DOCTYPE versioning change proposal (ISSUE-4)
- Re: Should <video> buffer control be tri-state?
- Re: HTML5 Recommendation document review comments
Sunday, 3 January 2010
- Re: Should <video> buffer control be tri-state?
- Re: Should <video> buffer control be tri-state?
- Re: HTML5 Recommendation document review comments
- Re: Should <video> buffer control be tri-state?
- Re: Should <video> buffer control be tri-state?
- Re: Should <video> buffer control be tri-state?
- Re: Should <video> buffer control be tri-state?
- Re: Should <video> buffer control be tri-state?
- Re: HTML5 Recommendation document review comments
- Re: Updated DOCTYPE versioning change proposal (ISSUE-4)
- Re: Should <video> buffer control be tri-state?
- Re: Should <video> buffer control be tri-state?
- Re: Should <video> buffer control be tri-state?
- Re: Should <video> buffer control be tri-state?
- Re: Should <video> buffer control be tri-state?
- Re: polyglot XHTML/HTML and <!DOCTYPE html about:legacy-compat>
- Re: Should <video> buffer control be tri-state?
- Re: "Controlled environments" in scope for HTML working group
- Re: "Controlled environments" in scope for HTML working group
- Re: Should <video> buffer control be tri-state?
- Re: Should <video> buffer control be tri-state?
- Re: Should <video> buffer control be tri-state?
- Re: Should <video> buffer control be tri-state?
- Re: "vastly increases reverse-engineering costs" and version proposal
- Re: "Controlled environments" in scope for HTML working group
- Re: Should <video> buffer control be tri-state?
- Re: Should <video> buffer control be tri-state?
- Re: "Controlled environments" in scope for HTML working group
- Re: Public feedback on HTML5 video
- Re: HTML Tables Freeze Panes
- Re: Public feedback on HTML5 video
- Re: Public feedback on HTML5 video
- Should <video> buffer control be tri-state?
- Re: HTML5 Recommendation document review comments
- Re: "vastly increases reverse-engineering costs" and version proposal
- HTML5 Recommendation document review comments
- Updated DOCTYPE versioning change proposal (ISSUE-4)
- Re: polyglot XHTML/HTML and <!DOCTYPE html about:legacy-compat>
Saturday, 2 January 2010
- "Controlled environments" in scope for HTML working group
- RE: polyglot XHTML/HTML and <!DOCTYPE html about:legacy-compat>
- "vastly increases reverse-engineering costs" and version proposal
- Re: polyglot XHTML/HTML and <!DOCTYPE html about:legacy-compat>
- Re: polyglot XHTML/HTML and <!DOCTYPE html about:legacy-compat>
- HTML Tables Freeze Panes
- polyglot XHTML/HTML and <!DOCTYPE html about:legacy-compat>