Re: UI Events with IndieUI

Seems to me that scroll and pan are one of the easiest proof-of-concept items to look at and implement for UI and testing.

The value change events ought to be examined within the context of the IME-API, much a undo should be examined alongside the UndoManager family.

Hit testing ought to be a priority; there is a lot in the pipeline, I just hope it floats to the top.

-Charles



On Feb 4, 2013, at 6:29 PM, Richard Schwerdtfeger <schwer@us.ibm.com> wrote:

> Hi Charles, 
> 
> Yes, I am involved with the Indie UI events work. Indie Ui events should route through the DOM same as other events. However, we need to have hit testing implemented in canvas.
> 
> Can Rick Cabanier/others state where we are on that with the browsers manufacturers? I have been heads down on Indie UI, ARIA 1.0 CR, and SVG accessibility. 
> 
> Rich
> 
> 
> Rich Schwerdtfeger
> 
> <graycol.gif>Charles Pritchard ---02/04/2013 07:04:12 PM---Heads up for Canvas widget developers, in addition to ARIA and semantic html, it seems we will also
> 
> From:	Charles Pritchard <chuck@jumis.com>
> To:	"public-canvas-api@w3.org" <public-canvas-api@w3.org>, 
> Date:	02/04/2013 07:04 PM
> Subject:	UI Events with IndieUI
> 
> 
> 
> Heads up for Canvas widget developers, in addition to ARIA and semantic html, it seems we will also gaij UI events:
> 
> https://dvcs.w3.org/hg/IndieUI/raw-file/tip/src/indie-ui-events.html
> 
> These allow you to let the UA/OS know that your widget supports things like panning, or zoom.
> 
> -Charles
> 
> 
> 
>