Wednesday, 26 June 2013
- RE: Compositing and Blending / canvas
- Re: Compositing and Blending / canvas
- RE: Compositing and Blending / canvas
- Re: During HTML parsing, are *all* named character references replaced by their corresponding glyph?
- Re: During HTML parsing, are *all* named character references replaced by their corresponding glyph?
- Re: During HTML parsing, are *all* named character references replaced by their corresponding glyph?
- Compositing and Blending / canvas
- Re: During HTML parsing, are *all* named character references replaced by their corresponding glyph?
Tuesday, 25 June 2013
- Re: During HTML parsing, are *all* named character references replaced by their corresponding glyph?
- Week 24 (2013-06-17) - WHATWG patches cherry-picked to HTML 5.1
Monday, 24 June 2013
- [editorial][textarea] Use consistent terminology when describing textarea element values
- Re: During HTML parsing, are *all* named character references replaced by their corresponding glyph?
- Re: During HTML parsing, are *all* named character references replaced by their corresponding glyph?
- Re: use cases for figure without figcaption?
- Re: During HTML parsing, are *all* named character references replaced by their corresponding glyph?
- Re: During HTML parsing, are *all* named character references replaced by their corresponding glyph?
- RE: use cases for figure without figcaption?
Saturday, 22 June 2013
- During HTML parsing, are *all* named character references replaced by their corresponding glyph?
- RE: use cases for figure without figcaption?
Friday, 21 June 2013
Thursday, 20 June 2013
- Re: use cases for figure without figcaption?
- RE: use cases for figure without figcaption?
- Re: use cases for figure without figcaption?
- RE: use cases for figure without figcaption?
- RE: use cases for figure without figcaption?
- use cases for figure without figcaption?
- Re: proposal: modify the figure element
- RE: proposal: modify the figure element
- Re: proposal: modify the figure element
- Re: proposal: modify the figure element
- Re: proposal: modify the figure element
- proposal: modify the figure element
Wednesday, 19 June 2013
Monday, 17 June 2013
- header/footer in header/footer
- Re: <subline> becomes <subhead> and other updates
- Re: <subline> becomes <subhead> and other updates
Saturday, 15 June 2013
- WHATWG cherry picks applied to the HTML 5.1 spec for week 23 (2013-06-10)
- Re: Multiple metadata text tracks
Friday, 14 June 2013
- RE: Fixes cherry picked this week
- Multiple metadata text tracks
- Re: A new proposal for how to deal with text track cues
- Re: A new proposal for how to deal with text track cues
- Re: A new proposal for how to deal with text track cues
- Re: DRM in HTML5 A Betrayal of Public Trust
- Re: A new proposal for how to deal with text track cues
- Re: A new proposal for how to deal with text track cues
- Re: A new proposal for how to deal with text track cues
- Re: DRM in HTML5 A Betrayal of Public Trust
Thursday, 13 June 2013
- Re: DRM in HTML5 A Betrayal of Public Trust
- Re: DRM in HTML5 A Betrayal of Public Trust
- Re: A new proposal for how to deal with text track cues
- Re: Fixes cherry picked this week
Wednesday, 12 June 2013
- Re: DRM in HTML5 A Betrayal of Public Trust
- RE: Fixes cherry picked this week
- Re: A new proposal for how to deal with text track cues
- Re: A new proposal for how to deal with text track cues
- Re: DRM in HTML5 A Betrayal of Public Trust
- Re: A new proposal for how to deal with text track cues
- Re: A new proposal for how to deal with text track cues
- Re: A new proposal for how to deal with text track cues
- Re: A new proposal for how to deal with text track cues
- Re: A new proposal for how to deal with text track cues
- Re: Fixes cherry picked this week
Friday, 7 June 2013
Wednesday, 12 June 2013
Tuesday, 11 June 2013
Monday, 10 June 2013
Sunday, 9 June 2013
- Re: <subline> becomes <subhead> and other updates
- Re: <subline> becomes <subhead> and other updates
- Re: <subline> becomes <subhead> and other updates
- Re: <subline> becomes <subhead> and other updates
- Re: <subline> becomes <subhead> and other updates
- Re: <subline> becomes <subhead> and other updates
- Re: <subline> becomes <subhead> and other updates
Saturday, 8 June 2013
- Re: <subline> becomes <subhead> and other updates
- Re: <subline> becomes <subhead> and other updates
- Re: <subline> becomes <subhead> and other updates
- Re: <subline> becomes <subhead> and other updates
- <subline> becomes <subhead> and other updates
Friday, 7 June 2013
- Re: proposal to explicitly forbid <small> use as subheadings
- Re: proposal to explicitly forbid <small> use as subheadings
- Re: proposal to explicitly forbid <small> use as subheadings
- RE: proposal to explicitly forbid <small> use as subheadings
- Re: proposal to explicitly forbid <small> use as subheadings
- RE: proposal to explicitly forbid <small> use as subheadings
- Re: proposal to explicitly forbid <small> use as subheadings
- RE: proposal to explicitly forbid <small> use as subheadings
- Re: proposal to explicitly forbid <small> use as subheadings
- Re: proposal to explicitly forbid <small> use as subheadings
- RE: proposal to explicitly forbid <small> use as subheadings
- Re: proposal to explicitly forbid <small> use as subheadings
- Re: proposal to explicitly forbid <small> use as subheadings
- Re: proposal to explicitly forbid <small> use as subheadings
- Re: proposal to explicitly forbid <small> use as subheadings
- Re: proposal to explicitly forbid <small> use as subheadings
- Re: proposal to explicitly forbid <small> use as subheadings
- proposal to explicitly forbid <small> use as subheadings