<trackbot> Date: 06 December 2010

<scribe> meeting: W3C HTML Canvas Accessibility meeting

<scribe> meeting: make log public

http://lists.w3.org/Archives/Public/public-canvas-api/2010OctDec/0055.html

<scribe> scribe: Rich

2D API update for caret and selection

<scribe> ACTION: Rich review Charles draft of the canvas 2D API [recorded in http://www.w3.org/2010/12/06-html-a11y-minutes.html#action01]

<trackbot> Created ACTION-91 - Review Charles draft of the canvas 2D API [on Richard Schwerdtfeger - due 2010-12-13].

Zooming

david: I am not sure if the real issue is about privacy or the author doing the wrong thing
... they want to be shown what the award is and how it outweighs the list

charles: Robert did come up with a solution that fits within the specifications
... this will make things slower
... Robert said it was quick to code.

david: have you had any further discussion

charles: Mozilla internally had made this policy decision a while ago
... the data is actually exposed and you have to do nasty hacks to get it.
... I can't get past the fact that they want to make it difficult
... they don't appear to want to address it
... I have the same issue in webkit
... g
... Google wants the standard
... If Mozilla won't engage they won't comply

david: was there any discussion prior to the canvas context

charles: I believe so.
... we seem stuck

david: I will see them in person next week
... if you want me to contact them quickly I can deal with internally now.

charles: it would be good to not to have to hack this
... I would like to see the mIcrosoft solution in webkit as well

<Downchuck> hi frank

hi Frank

Charles: I can't do the hack on Webkit. When sidebars go in I am stuck on webkit.

<frankolivier> Hello all

Hi Frank

welcome

we are going to get to editing in a minute

charles: they need to give more credence to accessibility experts on this.

Rich: IE provides the logical DPI to JavaScript developers

Charles: on the list they said it was unnecessary to have both X and Y scaling. Is there a use case for X and Y scaling?

Frank: this was in IE 6
... I could not find internal documentation
... I could not see why we would have non-square pixels on the device.

ApI for getting selection, grammar, and spell checking ranges

Rich: there was a concern over exposing the language as a privacy issue

Frank: If you have a custom dictionary you would not want to expose that to web pages
... it is easy for the web page to identify my private dictionary

Charles: it occurs to me that when browsing icognito ...

Frank: this is most acute in private mode.
... this is a general problem in the HTML spec.
... you can actually get a pretty unique fingerprint of those browsing the web

<davidb> david: agree

Rich: we could simply create elements for the <canvas>, <spell>, <grammar>

<spell> foob </spell>

Rich: this could allow the web author the page outside the user's dictionary

charles: this only says this range is misspelled

<davidb> i have to go

<Downchuck> happy fridge day

<Downchuck> :-(

frank: so, the author would have to keep track of visually where the stuff was on the screen
... no platform convention

<scribe> ACTION: Rich write a high level write up of the use of elements to annotate the canvas subtree to support caret, spell and grammar checkers [recorded in http://www.w3.org/2010/12/06-html-a11y-minutes.html#action02]

<trackbot> Created ACTION-92 - Write a high level write up of the use of elements to annotate the canvas subtree to support caret, spell and grammar checkers [on Richard Schwerdtfeger - due 2010-12-13].

Restricting elements used in the canvas subtree

Rich: Charles is suggesting that we not initialize certain elements in the canvas subtree like IFrame

<Downchuck> Descendant elements which require initialization (e.g. img and iframe) MUST NOT be activated during page load.

<frankolivier> <ZZZ> Descendant elements which require initialization (e.g. img and iframe) shall not be initialized on page load. </ZZZ>

http://lists.w3.org/Archives/Public/public-canvas-api/2010OctDec/att-0055/HTML_Canvas_Element.html

Frank: I think we would need to be more crisp on IFrame

Charles: I think IFrame is kind of handled strange by other browsers
... Perhaps writing more would be helpful

Frank: we could say we support the Iframe but the source would be null

charles: what is the security issue

Frank: People override IFrame
... quick jacking

Charles: this would be like an IFrame not actually attached to the DOM

Frank: where is this discussed

Charles: wwdom and whatwg - not exactly sure
... I don't like the idea of getting rid of the src="" ... the data may actually be useful like the image source

Rich: do you think you can improve the language?

Charles: yes
... we need to support something like image with a src we do not want to break it
... will dig into IFrame
... I had one question regarding the test I sent
... when I hit the space bar on a checkbox it sent a mouse event with the coordinates that were off screen

Frank: I am looking at it now. Please send me a note of what you found

Rich: when do you all go on vacation?
... Last meeting in 2010 will be on December 13

<scribe> meeting: W3C HTML Canvas Accessibility Subteam

This is scribe.perl Revision: 1.135  of Date: 2009/03/02 03:52:20  
Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/

Guessing input format: RRSAgent_Text_Format (score 1.00)

Succeeded: s/me to deal with this/me to contact them/
Succeeded: s/they need to be gently shown/they want to be shown/
No ScribeNick specified.  Guessing ScribeNick: richardschwerdtfe
Found Scribe: Rich
Default Present: richardschwerdtfe, David_Bolter, Charles_Pritchard, [Microsoft]
Present: richardschwerdtfe David_Bolter Charles_Pritchard [Microsoft]
Found Date: 06 Dec 2010
Guessing minutes URL: http://www.w3.org/2010/12/06-html-a11y-minutes.html
People with action items: rich

WARNING: Input appears to use implicit continuation lines.
You may need the "-implicitContinuations" option.