Friday, 30 November 2012
- RE: The Web and Consumer Advocacy
- HTML/XML TF Report glosses over Polyglot Markup (Was: Statement why the Polyglot doc should be informative)
- [respimg] `srcset`/`picture` and CSS `@viewport`
- Re: Formal Objections on REC-track status of polyglot and alt-techniques
- Re: Statement why the Polyglot doc should be informative
- Re: Formal Objections on REC-track status of polyglot and alt-techniques
Thursday, 29 November 2012
- Re: Formal Objections on REC-track status of polyglot and alt-techniques
- Re: Formal Objections on REC-track status of polyglot and alt-techniques
- Formal Objections on REC-track status of polyglot and alt-techniques
Wednesday, 28 November 2012
- Re: CfC: Request transition of HTML Microdata to Candidate Recommendation
- [Bug 20126] New: Description of BDI element needs to be updated after a change in the CSS unicode-bidi:isolate spec
- Editorial patches staged for merge week 49
- Re: CfC: Request transition of HTML Microdata to Candidate Recommendation
- Re: WHATWG patches staged for merge week 47 & update on branches
- [Bug 20118] New: Several clarifications / suggestions for improvement
- [Bug 20117] New: Discoverability should mean "for all users"
- Re: Statement why the Polyglot doc should be informative
- Re: Statement why the Polyglot doc should be informative
- Re: Statement why the Polyglot doc should be informative
Tuesday, 27 November 2012
- Re: CfC: Request transition of HTML Microdata to Candidate Recommendation
- Re: CfC: to publish main element specification as a First Public Working Draft (FPWD)
- Re: Alt-Techniques Formal Objection Rationale
- Re: Statement why the Polyglot doc should be informative
- Re: CfC: Request transition of HTML Microdata to Candidate Recommendation
- Re: CfC: Request transition of HTML Microdata to Candidate Recommendation
- HTML Microdata: Note vs Recommendation Track - Call for Rationale Statements
- Re: CfC: Request transition of HTML5 to Candidate Recommendation
- Re: CfC: Request transition of HTML5 to Candidate Recommendation
- Re: CfC: Request transition of HTML Canvas 2D Context to Candidate Recommendation
- Re: HTML Canvas 2D Context exit criteria (was RE: CfC: Request transition of HTML Canvas 2D Context to Candidate Recommendation)
- Re: CfC: Request transition of HTML Microdata to Candidate Recommendation
- Re: CfC: Request transition of HTML Microdata to Candidate Recommendation
- Re: CfC: Request transition of HTML Microdata to Candidate Recommendation
- Re: CfC: Request transition of HTML Microdata to Candidate Recommendation
- Re: HTML Canvas 2D Context exit criteria (was RE: CfC: Request transition of HTML Canvas 2D Context to Candidate Recommendation)
Monday, 26 November 2012
- CfC: Request transition of HTML Microdata to Candidate Recommendation
- Re: CfC: Request transition of HTML5 to Candidate Recommendation
- Re: CfC: Request transition of HTML Canvas 2D Context to Candidate Recommendation
- Re: Mailing list for Responsive Images
- Re: HTML Canvas 2D Context exit criteria (was RE: CfC: Request transition of HTML Canvas 2D Context to Candidate Recommendation)
- HTML Canvas 2D Context exit criteria (was RE: CfC: Request transition of HTML Canvas 2D Context to Candidate Recommendation)
- Re: CfC: Request transition of HTML5 to Candidate Recommendation
- Re: CfC: Request transition of HTML5 to Candidate Recommendation
- RE: Request transition of HTML5 to Candidate Recommendation
- Re: CfC: Request transition of HTML Canvas 2D Context to Candidate Recommendation
- Re: CfC: Request transition of HTML5 to Candidate Recommendation
- Re: CfC: Request transition of HTML Microdata to Candidate Recommendation
- [Bug 20085] New: Description of BDI element needs to be updated after a change in the CSS unicode-bidi:isolate spec
- Re: CfC: Request transition of HTML5 to Candidate Recommendation
- Re: CfC: Request transition of HTML Canvas 2D Context to Candidate Recommendation
- Re: CfC: Request transition of HTML Microdata to Candidate Recommendation
- Re: CfC: Request transition of HTML5 to Candidate Recommendation
- Re: CfC: Request transition of HTML Microdata to Candidate Recommendation
- Re: CfC: Request transition of HTML5 to Candidate Recommendation
- Re: CfC: Request transition of HTML5 to Candidate Recommendation
- Re: CfC: Request transition of HTML Microdata to Candidate Recommendation
- Re: CfC: Request transition of HTML5 to Candidate Recommendation
- Re: CfC: to publish main element specification as a First Public Working Draft (FPWD)
- Re: CfC: Request transition of HTML Microdata to Candidate Recommendation
- Re: CfC: Request transition of HTML Microdata to Candidate Recommendation
- Re: CfC: Request transition of HTML5 to Candidate Recommendation
- Re: CfC: Request transition of HTML5 to Candidate Recommendation
- Re: CfC: Request transition of HTML5 to Candidate Recommendation
- Re: CfC: Request transition of HTML Microdata to Candidate Recommendation
Sunday, 25 November 2012
- Re: CfC: Request transition of HTML5 to Candidate Recommendation
- Re: CfC: Request transition of HTML Microdata to Candidate Recommendation
- Re: CfC: Request transition of HTML Microdata to Candidate Recommendation
- Re: CfC: Request transition of HTML Microdata to Candidate Recommendation
- Re: CfC: Request transition of HTML Microdata to Candidate Recommendation
- Re: CfC: Request transition of HTML Microdata to Candidate Recommendation
- Re: CfC: Request transition of HTML Microdata to Candidate Recommendation
- Re: CfC: Request transition of HTML Microdata to Candidate Recommendation
- Re: CfC: Request transition of HTML Microdata to Candidate Recommendation
- Re: CfC: Request transition of HTML Microdata to Candidate Recommendation
- Re: CfC: Request transition of HTML Microdata to Candidate Recommendation
- Re: CfC: Request transition of HTML Microdata to Candidate Recommendation
Saturday, 24 November 2012
Friday, 23 November 2012
- Publishing Use Cases and <picture> document through HTMLWG
- Re: Mailing list for Responsive Images
- Usage of Alt
- Re: CfC: Request transition of HTML Microdata to Candidate Recommendation
- [Bug 20063] New: Unclear whether a <track> element's load event should fired if appended to a <video> with no "src" attribute
- Re: CfC: to publish main element specification as a First Public Working Draft (FPWD)
Thursday, 22 November 2012
Friday, 23 November 2012
Thursday, 22 November 2012
- [Bug 20048] New: remove decorative image code example
- Re: request to publish 'Using ARIA in HTML' as a FPWD
- Re: CfC: to publish main element specification as a First Public Working Draft (FPWD)
- Re: request to publish 'Using ARIA in HTML' as a FPWD
- Re: CfC: Request transition of HTML5 to Candidate Recommendation
- Re: CfC: Request transition of HTML Microdata to Candidate Recommendation
- Re: CfC: Request transition of HTML Canvas 2D Context to Candidate Recommendation
Wednesday, 21 November 2012
- Re: request to publish 'Using ARIA in HTML' as a FPWD
- Re: Summary of I18N discussion in HTML WG today
- [Bug 20035] New: broken link on HTML4/5 Differences page: input type="color"
- [Bug 20034] New: canvas getImageData opens security whole for code
- WHATWG patches staged for merge week 47 & update on branches
- [Bug 20033] New: [AAPI]:
Tuesday, 20 November 2012
- Re: request to publish 'Using ARIA in HTML' as a FPWD
- RE: request to publish 'Using ARIA in HTML' as a FPWD
- Re: request to publish 'Using ARIA in HTML' as a FPWD
Monday, 19 November 2012
- Re: Alt-Techniques Formal Objection Rationale
- Re: Summary of I18N discussion in HTML WG today
- Re: Alt-Techniques Formal Objection Rationale
- Alt-Techniques Formal Objection Rationale
- Re: WHATWG patches staged for merge week 46
- Re: WHATWG patches staged for merge week 46
Sunday, 18 November 2012
Saturday, 17 November 2012
Friday, 16 November 2012
- Re: {minutes} HTML WG telecon 2012-11-15- Actions, CR drafts, FPWD for main, Task Force reports
- Re: {minutes} HTML WG telecon 2012-11-15- Actions, CR drafts, FPWD for main, Task Force reports
- Re: CfC: to publish main element specification as a First Public Working Draft (FPWD)
Thursday, 15 November 2012
- Re: CfC: Request transition of HTML Canvas 2D Context to Candidate Recommendation
- Re: CfC: to publish main element specification as a First Public Working Draft (FPWD)
- RE: to publish main element specification as a First Public Working Draft (FPWD)
- Re: CfC: to publish main element specification as a First Public Working Draft (FPWD)
- [Bug 19967] New: definition of body element incorrect
- Re: CfC: to publish main element specification as a First Public Working Draft (FPWD)
- Re: [HTMLWG] CfC: Create a Mailing List for administrative matters and notifications?
- Re: CfC: to publish main element specification as a First Public Working Draft (FPWD)
Wednesday, 14 November 2012
- RE: to publish main element specification as a First Public Working Draft (FPWD)
- CfC: to publish main element specification as a First Public Working Draft (FPWD)
- CfC: Request transition of HTML Microdata to Candidate Recommendation
- CfC: Request transition of HTML Canvas 2D Context to Candidate Recommendation
- CfC: Request transition of HTML5 to Candidate Recommendation
- [Bug 19958] New: [AAPI]: missed items in table of contents
Monday, 12 November 2012
Sunday, 11 November 2012
- WHATWG patches staged for merge week 46
- [Bug 19934] New: Is the argument of setLineDash an array or sequence?
- [Bug 19933] New: Check the version history, and uses of the word "recommended", and of the words "not recommended"... either we should have "not recommended" in the list of words, or we should have neither that nor "recommended".
- Re: WHATWG patches staged for merge week 45
Saturday, 10 November 2012
- [Bug 19932] New: Proposal: Add CanvasRenderingContext2D.fillRule
- [Bug 19931] New: Should not prefer byte order mark with UTF-8
- Re: FW: [NVDA] #809: Support for longdesc in web browsers
- Re: FW: [NVDA] #809: Support for longdesc in web browsers
Friday, 9 November 2012
- Re: FW: [NVDA] #809: Support for longdesc in web browsers
- [Bug 19925] New: Drop XHTML from the title of the document
- RE: FW: [NVDA] #809: Support for longdesc in web browsers
- Re: Statement why the Polyglot doc should be informative
- Re: Summary of I18N discussion in HTML WG today
- Re: Summary of I18N discussion in HTML WG today
- Re: Statement why the Polyglot doc should be informative
- Re: Statement why the Polyglot doc should be informative
- Re: Statement why the Polyglot doc should be informative
- Re: Statement why the Polyglot doc should be informative
- Re: Statement why the Polyglot doc should be informative
- Re: Statement why the Polyglot doc should be informative
- Re: Statement why the Polyglot doc should be informative
- Re: FW: [NVDA] #809: Support for longdesc in web browsers
- Re: FW: [NVDA] #809: Support for longdesc in web browsers
- Re: FW: [NVDA] #809: Support for longdesc in web browsers
- RE: FW: [NVDA] #809: Support for longdesc in web browsers
- Re: FW: [NVDA] #809: Support for longdesc in web browsers
Thursday, 8 November 2012
- RE: FW: [NVDA] #809: Support for longdesc in web browsers
- Re: FW: [NVDA] #809: Support for longdesc in web browsers
- Mailing list for Responsive Images
- FW: [NVDA] #809: Support for longdesc in web browsers
- [Bug 19905] HTML5 Canvas Gradient - new idea, "new Canvas"...
Wednesday, 7 November 2012
- [Bug 19899] New: Support for Break characters should be reconsidered for Textarea
- RE: [HTMLWG] CfC: Create a Mailing List for administrative matters and notifications?
- Re: [HTMLWG] CfC: Create a Mailing List for administrative matters and notifications?
- [Bug 19895] New: mods for main stylesheet speccing
- Re: [HTMLWG] CfC: Create a Mailing List for administrative matters and notifications?
- Announcing New Co-Facilitators for the HTML-A11Y Task Force
- main element parsing behaviour
- Re: maincontent extension - data on use of id=main and id=content in web pages
- Re: Polyglot Markup Formal Objection Rationale
Tuesday, 6 November 2012
- Re: Polyglot Markup Formal Objection Rationale
- additional bugmail suggestion (was Re: [HTMLWG] CfC: Create a Mailing List for administrative matters and notifications?)
- Re: [HTMLWG] CfC: Create a Mailing List for administrative matters and notifications?
- Re: Polyglot Markup Formal Objection Rationale
- [HTMLWG] CfC: Create a Mailing List for administrative matters and notifications?
- Re: Polyglot Markup Formal Objection Rationale
- The Web and Consumer Advocacy
- Re: Polyglot Markup Formal Objection Rationale
- Re: Polyglot Markup Formal Objection Rationale
- Re: Polyglot Markup Formal Objection Rationale
- [Bug 19451] Guidance on when to add ARIA inline vs script is misleading
- Re: Polyglot Markup Formal Objection Rationale
- Re: Polyglot Markup Formal Objection Rationale
- Polyglot Markup Formal Objection Response
- Re: Polyglot Markup Formal Objection Rationale
- Re: Polyglot Markup Formal Objection Rationale
- Re: Polyglot Markup Formal Objection Rationale
- Re: Polyglot Markup Formal Objection Rationale
- Re: Polyglot Markup Formal Objection Rationale
- Re: Polyglot Markup Formal Objection Rationale
- Re: Polyglot Markup Formal Objection Rationale
- Re: Polyglot Markup Formal Objection Rationale
- Re: Polyglot Markup Formal Objection Rationale
- Re: Polyglot Markup Formal Objection Rationale
- Re: Polyglot Markup Formal Objection Rationale
- Re: Polyglot Markup Formal Objection Rationale
- Re: Polyglot Markup Formal Objection Rationale
- Remove scoped stylesheets from html5
- [Bug 19874] New: Drop scoped stylesheets
- Re: Polyglot Markup Formal Objection Rationale
Monday, 5 November 2012
- Re: Fwd: Polyglot Markup Formal Objection Rationale
- Re: Fwd: Polyglot Markup Formal Objection Rationale
- Re: Fwd: Polyglot Markup Formal Objection Rationale
- Re: Fwd: Polyglot Markup Formal Objection Rationale
- Re: Polyglot Markup Formal Objection Rationale
- Re: rationale for keeping alt text spec as normative.
- Re: Fwd: Polyglot Markup Formal Objection Rationale
- Re: Polyglot Markup Formal Objection Rationale
- Re: Summary of I18N discussion in HTML WG today
- Re: Polyglot Markup Formal Objection Rationale
- Re: Polyglot Markup Formal Objection Rationale
- Re: Fwd: Polyglot Markup Formal Objection Rationale
- Re: Polyglot Markup Formal Objection Rationale
- Re: Fwd: Polyglot Markup Formal Objection Rationale
- Re: Polyglot Markup Formal Objection Rationale
- Re: Statement why the Polyglot doc should be informative
- Re: Polyglot Markup Formal Objection Rationale
- Re: Polyglot Markup Formal Objection Rationale
- Re: Statement why the Polyglot doc should be informative
- Re: Polyglot Markup Formal Objection Rationale
- Re: Fwd: Polyglot Markup Formal Objection Rationale
- Re: Fwd: Polyglot Markup Formal Objection Rationale
- Re: Statement why the Polyglot doc should be informative
- Re: Fwd: Polyglot Markup Formal Objection Rationale
- Fwd: Polyglot Markup Formal Objection Rationale
- Re: Polyglot Markup Formal Objection Rationale
- Re: Polyglot Markup Formal Objection Rationale
- Re: Statement why the Polyglot doc should be informative
Sunday, 4 November 2012
- Re: WHATWG patches staged for merge week 45
- Re: Polyglot Markup Formal Objection Rationale
- Re: Statement why the Polyglot doc should be informative
- Re: Polyglot Markup Formal Objection Rationale
- Polyglot Markup Formal Objection Rationale
- Re: WHATWG patches staged for merge week 45
- WHATWG patches staged for merge week 45
- [Bug 19853] New: The media element event task source should probably be ditched and the DOM manipulation task source be used instead. Having some media events have undefined order compared to other tasks is just asking for trouble. (http://www.whatwg.org/specs/web-apps/cu
- [Bug 19852] New: "abort" algorithm being called from the navigate algorithm causes salvagable=false always
- [Bug 19851] New: In the following statement, it is unclear WHICH browsing context is being referred to: "13. The fetch algorithm must delay the load event of the browsing context.". Besides, there is no "load event" for the browsing context, only for document. I believe t
- Re: WHATWG patches staged for merge week 44
Saturday, 3 November 2012
Friday, 2 November 2012
- RE: rationale for keeping alt text spec as normative.
- RE: rationale for keeping alt text spec as normative.
- Re: W3C Mail List traffic for www-style@w3.org and public-html@w3.org during 2012 (year to date).
- W3C Mail List traffic for www-style@w3.org and public-html@w3.org during 2012 (year to date).
- rationale for keeping alt text spec as normative.
- Re: Statement why the Polyglot doc should be informative
- Summary of I18N discussion in HTML WG today
- Statement why the Polyglot doc should be informative