W3C home > Mailing lists > Public > public-canvas-api@w3.org > July to September 2011

Re: Reasons of using Canvas for UI design

From: David Singer <singer@apple.com>
Date: Mon, 15 Aug 2011 19:16:24 +0200
Cc: paniz alipour <alipourpaniz@gmail.com>, Cynthia Shelly <cyns@microsoft.com>, Steve Faulkner <faulkner.steve@gmail.com>, Frank Olivier <Frank.Olivier@microsoft.com>, Canvas <public-canvas-api@w3.org>
Message-id: <6DB4A049-0272-4944-A01A-22DEF92CC9EE@apple.com>
To: Richard Schwerdtfeger <schwer@us.ibm.com>

On Aug 15, 2011, at 19:10 , Richard Schwerdtfeger wrote:

>  The browser has all the path transformation information 
> > to do the job
> > All true -- if the assumption holds.
> I am not sure what is missing. Are you concerned about a coding error? That can always happen.
No, I am pointing out your assumption is that there are objects with well-defined path boundaries.  I am not sure that's always true.
> Being able to support the basic accessibility APIs is essential. Right now we do not have that. The need to indicate where an object is on the drawing surface is an essential requirement. 
Again, an assumption of visually discrete objects with well-defined locations and edges.
> What we need to avoid here is the statement that "well you have not fully boiled the ocean so you can't do anything."
But we also need to avoid "you can only solve the use cases when someone uses canvas when they could and probably should have used existing HTML and CSS UI elements". 

David Singer
Multimedia and Software Standards, Apple Inc.

Received on Monday, 15 August 2011 17:17:30 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:10:32 UTC