- From: Gregory J. Rosmaita <oedipus@hicom.net>
- Date: Thu, 11 Nov 2010 17:35:50 +0000
- To: public-canvas-api@w3.org, public-html-a11y@w3.org
aloha! this is a reminder that the canvas sub-team will be resuming its meetings on monday, 15 november 2010 at 2000h UTC -- meeting logistics can be found at: http://www.w3.org/WAI/PF/HTML/wiki/Canvas/Meetings a preview of what will be discussed can be found in the HTML TF telecon minutes for 11 november 2010, in particular: http://www.w3.org/2010/11/11-html-a11y-minutes.html#item10 excerpted below: RS: re-starting monday calls for canvas to investigate rich text editing -- separated out reqs for using standard controls using APIs -- will address in change proposal ... plan: asked to create individual defects related to RTE -- what needs to be done as far as API changes to 2D context standard controls to define wwhich elements are allowable in canvas sub-tree -- 1st time that used shadow DOM to navigate but not render -- some issues need to be investigated about it -- what constitutes fallback and how to keep in sync ... Rich Text Editing -- will take a lot of time; need to ensure that what is in contenteditable section can be reflected in a CANVAS implementation -- can't do now -- those are the issues we are working on ... re-iterate PaulC's comment -- in mobile TV space, comment made "what would you need for a profile"? canvas + javascript would hit the "sweet spot" -- must address a11y in RTE because Canvas might be only UI one can see in complex apps CS: frankO on board with that? RS: yes ... which "that"? CS: anything to do with RTE RS: said need to define where gaps are -- didn't think could do by last call PC: that is fair portrayal -- FrankO's warning was "this is not a trivial pursuit -- it will take a lot of effort" JS: messages have to be clear -- enough complexity in proposed text ... questions? MK: talked with FrankO -- inside canvas doubled testing effort -- concern: prevent double testing RS: doubletesting of.... ? ... components not being rendered will double? MK: yes, concern was that testing efforts have to be doubled because have 2 diff contexts RS: don't see how can reduce -- there is content now that is not being rendered -- going to be a lot of work MK: so there will be some pain for everyone? RS: yes -- trying to ensure that address all of the canvas issues -- spec allows shadow DOM -- in spec -- needs to be synced with what is in visual rendering RS: next step: make sure that when have shadow DOM what is appropriate behavior of UA in HTML -- how to render IFrame in shadow DOM -- rendering issues -- is CSS allowed ... need to flesh out shadow DOM in HTML5 spec
Received on Thursday, 11 November 2010 17:36:19 UTC