- From: Benjamin Hawkes-Lewis <bhawkeslewis@googlemail.com>
- Date: Tue, 21 Aug 2012 15:57:07 +0100
- To: Charles Pritchard <chuck@jumis.com>
- Cc: Rik Cabanier <cabanier@adobe.com>, Leonard Rosenthol <lrosenth@adobe.com>, Chaals McCathieNevile <w3b@chaals.com>, "public-html@w3.org" <public-html@w3.org>
On Tue, Aug 21, 2012 at 3:52 PM, Charles Pritchard <chuck@jumis.com> wrote: > On 8/19/2012 9:55 PM, Rik Cabanier wrote: >>> >>> A key design goal, as I understand it, was to avoid turning canvas into >>> a retained mode API. The author is responsible for managing any object >>> graph; >>> canvas is just a display. >> >> Isn't the new "current default path" a step towards retained graphics? > > > We went through this discussion at length on public-canvas-api. > > At the point that authors take responsibility for managing the DOM, they've > departed from the strict sense of a bitmap API and are now in the world of > ARIA. > ARIA+DOM is a retained mode API. Yes, effectively authors must manage two representations of their abstract interface: - canvas bitmaps - DOM The WHATWG hit region feature provides the weakest possible binding between the two. -- Benjamin Hawkes-Lewis
Received on Tuesday, 21 August 2012 14:57:58 UTC