- From: Richard Schwerdtfeger <schwer@us.ibm.com>
- Date: Mon, 6 Oct 2014 09:32:30 -0500
- To: Rik Cabanier <cabanier@gmail.com>
- Cc: Jatinder Mann <jmann@microsoft.com>, Canvas <public-canvas-api@w3.org>
- Message-ID: <OF910DC0E1.BE6BB99A-ON86257D69.004FABDF-86257D69.004FE165@us.ibm.com>
Rik. Hit testing is managed by the user agent. When you do things like clearRect () it is supposed to delete some of the hit regions. What you are suggesting is comparable to developers trying to keep track of focus changes. I don't agree with your assertion. So, once you set a hit region it is given to the browser and it has its own copy of it that it operates off of. What are the odds of staying in synch with that over time? Rich Rich Schwerdtfeger 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> 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 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.
Attachments
- image/gif attachment: graycol.gif
Received on Monday, 6 October 2014 14:33:04 UTC