Re: hit region list

I agree it might be useful to have an API to retrieve the hit region list.
Might I also suggest a lightweight "hitTest" function that lets you test a
point and determine which element would be hit? Presumably you could do
this by constructing a MouseEvent, but this would be more straightforward.

Rich, I don't understand your comment about scrolling or moving the window.
Canvas hit regions are defined canvas-local coordinates, so I don't see any
reason the browser or web author would care if the window scrolls or moves.


On Mon, Oct 6, 2014 at 7:33 AM, Richard Schwerdtfeger <schwer@us.ibm.com>
wrote:

> So, here is another example. When the browser scrolls or the window moves
> the hit region moves. Authors are not going to keep track of all that.
>
> Rich
>
>
> Rich Schwerdtfeger
>
> [image: Inactive hide details for Rik Cabanier ---10/05/2014 09:12:57
> PM---On Sun, Oct 5, 2014 at 5:14 AM, Richard Schwerdtfeger <schwe]Rik
> Cabanier ---10/05/2014 09:12:57 PM---On Sun, Oct 5, 2014 at 5:14 AM,
> Richard Schwerdtfeger <schwer@us.ibm.com> wrote:
>
> From: Rik Cabanier <cabanier@gmail.com>
> To: Richard Schwerdtfeger/Austin/IBM@IBMUS
> Cc: Canvas <public-canvas-api@w3.org>, Jatinder Mann <jmann@microsoft.com>
> Date: 10/05/2014 09:12 PM
> Subject: Re: hit region list
> ------------------------------
>
>
>
>
>
> On Sun, Oct 5, 2014 at 5:14 AM, Richard Schwerdtfeger <*schwer@us.ibm.com*
> <schwer@us.ibm.com>> wrote:
>
>    Jatinder, Rik,
>
>    I am working on the testable statements for hit regions. There is no
>    programmatic way to determine the hit region list. So, when we want to
>    verify that a hit region having the same id is replaced in the list we
>    cannot determine if the old hit region, associated with the id, is removed
>    from the list. A developer will want to be able to look at the hit region
>    list.
>
>    I filed a defect on this:
>    *https://www.w3.org/Bugs/Public/show_bug.cgi?id=26977*
>    <https://www.w3.org/Bugs/Public/show_bug.cgi?id=26977>
>
>    This will need to be a canvas 2.0 item and it does restrict our
>    ability to test all of canvas 1.0 hit region functionality.
>
>
> I don't see why this needs to be a feature in canvas. If a developer wants
> to keep track of the hit regions, he can do that himself.
>
>