Compositing and Blending / canvas
Week 24 (2013-06-17) - WHATWG patches cherry-picked to HTML 5.1
[editorial][textarea] Use consistent terminology when describing textarea element values
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?
- 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?
- 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?
- 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?
- 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?
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?
proposal: modify the figure element
Call for Exclusions (Update): HTML Image Description Extension
header/footer in header/footer
WHATWG cherry picks applied to the HTML 5.1 spec for week 23 (2013-06-10)
Multiple metadata text tracks
DRM in HTML5 A Betrayal of Public Trust
- Re: DRM in HTML5 A Betrayal of Public Trust
- Re: DRM in HTML5 A Betrayal of Public Trust
- Re: DRM in HTML5 A Betrayal of Public Trust
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
Fixes cherry picked this week
<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
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