On Mon, Feb 24, 2014 at 3:45 PM, Dominic Mazzoni <dmazzoni@google.com>wrote: > Wait, to clarify, addHitRegion would not actually provide hit testing? > > Is the idea that it'd be added in the next spec revision? It seems odd to > do this, the feature would ship in a way that doesn't really match the > original intent of the spec. > > I thought Mozilla already implemented some of the actual hit testing > features. > No, the only part that is implemented is that you associate a region with a fallback element. We plan to add real hit testing to the mozilla implementation but were contemplating of leaving this out of the spec for now. > On Mon, Feb 24, 2014 at 3:28 PM, Richard Schwerdtfeger <schwer@us.ibm.com>wrote: > >> Hi Dominic, >> >> For version of the canvas 1.0 spec. we would like to have the following >> in the specification. >> >> 1. addHitRegion but only with an optional id and a fallback element to >> associate the element (this will set the location). e.g. >> addHitRegion(id,control) where control would be any fallback element at >> this time. >> 2. drawFocusIfNeeded but remove the step that sets the location. >> >> 1. This would not provide actual hit testing but it would assign the >> location at this time >> >> We would need you to agree and implement this in Chrome now and we would >> work to address the other additions to the addHitRegion spec. (from WhatWG) >> in v2.0. We also want your feedback on the spec. changes. >> >> Rich >> >> Rich Schwerdtfeger >> > >
Received on Tuesday, 25 February 2014 00:06:14 UTC