Re: hit regions Firefox support update

On Fri, Feb 14, 2014 at 9:40 AM, Jay Munro <jaymunro@microsoft.com> wrote:

>  Do we have a 2nd implementation of hitRegions?
>

We do not.
They are listed as at-risk so we can still go to CR with them.

We should probably update the at-risk list to state that *part* or all of
hit regions might be removed.


> *From:* Rik Cabanier [mailto:cabanier@gmail.com]
> *Sent:* Friday, February 14, 2014 9:33 AM
> *To:* Alexander Surkov
> *Cc:* public-canvas-api@w3.org; Mark Sadecki
> *Subject:* Re: hit regions Firefox support update
>
>
>
> I just requested that the patches are checked into firefox.
>
> If all goes well, this means that the upcoming nightly build will have
> basic support for hit regions.
>
>
>
> If people had earlier tests for drawFocusIfNeeded, they can simply update
> them as follows.
>
> old code:
>
>  ctx.drawFocusIfNeeded(element);
>
> new code:
>
>  ctx.drawFocusIfNeeded(element);
>
>  ctx.addHitRegion({control: element};
>
>
>
> Alex, how can we turns hit regions and focus rings on by default?
>
>
>
> On Thu, Feb 13, 2014 at 10:40 AM, Alexander Surkov <
> surkov.alexander@gmail.com> wrote:
>
> Hi. Here's an update of hit region implementation in Firefox in case if
> you're curious .
>
> This week we've got a prototype of hit regions which can be used to change
> accessible boundaries. The work hasn't been landed into Firefox Nightly yet
> but there's a try build [2].
>
> There's no plans to continue the work on drawFocusIfNeeded to fit it for
> accessible boundaries setting since hit regions looks promising. It's worth
> to notice though that drawFocusIfNeeded (used to draw the focus) is part of
> Firefox and there's no actions to undo this.
>
>
>
> You can follow hit regions work by watching Mozilla bug [1].
>
> Thanks.
> Alexander.
>
>
> [1] https://bugzilla.mozilla.org/show_bug.cgi?id=966591
> [2] https://tbpl.mozilla.org/?tree=Try&rev=a0775f0bf042
>
>
>