I marked all custom element next level bugs as RESOLVED+LATER. They are
here: http://bit.ly/GIZamj
On 10/4/13 8:12 PM, ext Dimitri Glazkov wrote:
A better view of bugs is here:
https://www.w3.org/Bugs/Public/showdependencytree.cgi?id=14968hide_resolved=1
The only remaining bug is to coordinate with Math and SVG working
groups to make sure that they don't step on our dashes:
Hi Art,
Arthur Barstow art.bars...@nokia.com, 2013-10-05 08:00 -0400:
On 10/4/13 8:12 PM, ext Dimitri Glazkov wrote:
A better view of bugs is here:
https://www.w3.org/Bugs/Public/showdependencytree.cgi?id=14968hide_resolved=1
The only remaining bug is to coordinate with Math and SVG
On Sat, Oct 5, 2013 at 5:22 AM, Michael[tm] Smith m...@w3.org wrote:
Hi Art,
Arthur Barstow art.bars...@nokia.com, 2013-10-05 08:00 -0400:
On 10/4/13 8:12 PM, ext Dimitri Glazkov wrote:
A better view of bugs is here:
Hi Dimitri,
Dimitri Glazkov dglaz...@chromium.org, 2013-10-05 09:01 -0700:
If I set resolved=later, the target milestone doesn't seem as useful.
It does it you plan to reopen a bug at some later date and work on it then
--Mike
--
Michael[tm] Smith http://people.w3.org/mike
