- From: Mark Sadecki <mark.sadecki@gmail.com>
- Date: Thu, 5 Feb 2015 10:59:23 -0500
- To: Paul Cotton <Paul.Cotton@microsoft.com>
- Cc: Richard Schwerdtfeger <schwer@us.ibm.com>, Sam Ruby <rubys@intertwingly.net>, "public-canvas-api@w3.org" <public-canvas-api@w3.org>, Judy Brewer <jbrewer@w3.org>
- Message-ID: <CAOego5NMkWoG4qCdNvm0Y3XZioytZqW8AgxGLVUq1FThq1DG0g@mail.gmail.com>
There is currently one bug open in Chrome on drawFocusIfNeeded() [1]. There has been no movement since it was opened on 2014-10-14 I left a comment requesting an update today [2] [1] https://code.google.com/p/chromium/issues/detail?id=425149 [2] https://code.google.com/p/chromium/issues/detail?id=425149#c2 I will send dominic a follow-up email as well. Mark On Wed, Jan 28, 2015 at 5:44 PM, Paul Cotton <Paul.Cotton@microsoft.com> wrote: > Can you please add your browser contacts directly to this thread so the > progress is clear? > > Sent from my Windows Phone > ------------------------------ > From: Mark Sadecki > Sent: 28/01/2015 5:17 PM > To: Richard Schwerdtfeger > Cc: Sam Ruby; public-canvas-api@w3.org; Paul Cotton; Judy Brewer > Subject: Re: HTML Canvas 2D Context progress is stalled; time to drop > features? (resending) > > > I will follow up with browser vendors with regards to any defects on > drawFocusIfNeeded() > > Mark > > On Wed, Jan 28, 2015 at 4:45 PM, Richard Schwerdtfeger <schwer@us.ibm.com> > wrote: > >> all the tests for drawFocusIfNeeded are done. >> >> addHitRegion is the implementations have too long to go whereas >> drawFocusIfNeeded has some minor bugs that need to be fixed in the >> browsers. >> >> Mark has agreed to finish these getting those bugs fixed with the browser >> manufacturers. >> >> Rich Schwerdtfeger >> >> [image: Inactive hide details for Sam Ruby ---01/28/2015 02:36:15 >> PM---Background: HTML Canvas 2D Context is in Candidate Recommendatio]Sam >> Ruby ---01/28/2015 02:36:15 PM---Background: HTML Canvas 2D Context is in >> Candidate Recommendation: http://www.w3.org/TR/2dcontext >> >> From: Sam Ruby <rubys@intertwingly.net> >> To: "public-canvas-api@w3.org" <public-canvas-api@w3.org> >> Date: 01/28/2015 02:36 PM >> Subject: HTML Canvas 2D Context progress is stalled; time to drop >> features? >> ------------------------------ >> >> >> >> Background: HTML Canvas 2D Context is in Candidate Recommendation: >> >> http://www.w3.org/TR/2dcontext/ >> >> The plan, as of September 2014, was to have "All tests will be written >> and run by the end of the month": >> >> >> >> https://lists.w3.org/Archives/Public/public-canvas-api/2014JulSep/0033.html >> >> The status, as of January 2015, is that a number of tests have yet to be >> written (search for TODO): >> >> https://www.w3.org/wiki/HTML/Canvas_Task_Force/CR-Test >> >> Additionally, many of the tests that are currently written are failing. >> >> After discussions with my co-chair (Paul Cotton) and the W3C domain lead >> (PLH), the time has come to recommend that features for which we don't >> have passing tests be deferred to HTML Canvas level 2. >> >> I encourage everybody who would like to propose an alternate plan do so >> now. >> >> - Sam Ruby >> >> >> >
Attachments
- image/gif attachment: graycol.gif
Received on Thursday, 5 February 2015 16:00:17 UTC