W3C home > Mailing lists > Public > public-canvas-api@w3.org > April to June 2015

RE: Chrome has implemented hit region support

From: Paul Cotton <Paul.Cotton@microsoft.com>
Date: Tue, 14 Apr 2015 23:25:09 +0000
To: Rik Cabanier <cabanier@gmail.com>, Jatinder Mann <jmann@microsoft.com>
CC: Sam Ruby <rubys@intertwingly.net>, Janina Sajka <janina@rednote.net>, "public-canvas-api@w3.org" <public-canvas-api@w3.org>, "Philippe Le Hegaret (plh@w3.org)" <plh@w3.org>
Message-ID: <CY1PR0301MB1196B34AE1683FBA0A8A3458EAE60@CY1PR0301MB1196.namprd03.prod.outlook.com>
Given that we now have confirmation that we will have at least two implementations of the new A11Y features in Canvas2D Level 1 we need to execute on our plan [1] from last year's TPAC meeting to re-publish a Canvas2D Level 1 Last Call. 

FTR, the 16  CR bugs are recorded here:
http://tinyurl.com/me3wwzl
and they include the following two bugs:
https://www.w3.org/Bugs/Public/show_bug.cgi?id=27263
https://www.w3.org/Bugs/Public/show_bug.cgi?id=27264
whose changes were made in Dec 2014.

The candidate Last Call draft should identify the CR bug(s) that is significant enough to force the additional Last Call.  See [1].

Can either of you prepare such a candidate Last Call document so that we can do a CfC to get it published?  

I can help you work on the Status of This Document (SOTD) if you need help with this.  And we can get one of the Team contacts to ensure that the document is actually published once it is approved by the HTML WG.

/paulc

[1] http://www.w3.org/2014/10/30-html-wg-minutes.html#item12

Paul Cotton, Microsoft Canada
17 Eleanor Drive, Ottawa, Ontario K2E 6A3
Tel: (425) 705-9596 Fax: (425) 936-7329


-----Original Message-----
From: Janina Sajka [mailto:janina@rednote.net] 
Sent: Tuesday, April 14, 2015 11:48 AM
To: public-canvas-api@w3.org
Cc: Paul Cotton; Sam Ruby
Subject: Chrome has implemented hit region support

Colleagues:


Reproduced below are key portions of recent email exchanges with Dominic Mazzoni of Google, who has implemented hit region support in Chrome.


This should give us two independent hit region implementations, which we very much need for low-vision/magnification support in Canvas.

Janina


-------------------------------------------------------------------------------
Date: Tue, 24 Mar 2015 07:47:38 -0700
From: Dominic Mazzoni <dmazzoni@google.com>

Chrome has hit region support implemented now. You can try it by visiting this url and clicking "Enable" next to "Enable experimental canvas features", and then restarting Chrome.

chrome://flags/#enable-experimental-canvas-features

Do you know if anyone would be interested in helping to test our implementation against the spec for compliance? I think we can probably ship it if it looks like there's broad consensus and other browsers are shipping or actively working on it.
 
-------------------------------------------------------------------------------
Date: Tue, 24 Mar 2015 15:58:33 -0500
From: Richard Schwerdtfeger <schwer@us.ibm.com>

Hi Dominic,

We found some defects with canvas hit testing over a month ago in test
cases:

https://www.w3.org/wiki/HTML/Canvas_Task_Force/CR-Test#drawFocusIfNeeded_when_a_default_path_is_provided_and_the_associated_fallback_element_is_descendant_of_the_element_with_+focus._Scroll_the_window_so_that_the_canvas_moves

See test cases 2.12 on for Chrome Canary. Were these issues fixed?
 

-- 

Janina Sajka,	Phone:	+1.443.300.2200
			sip:janina@asterisk.rednote.net
		Email:	janina@rednote.net

Linux Foundation Fellow
Executive Chair, Accessibility Workgroup:	http://a11y.org

The World Wide Web Consortium (W3C), Web Accessibility Initiative (WAI)
Chair,	Protocols & Formats	http://www.w3.org/wai/pf
	Indie UI			http://www.w3.org/WAI/IndieUI/
Received on Tuesday, 14 April 2015 23:25:39 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 14 April 2015 23:25:39 UTC