On Thu, Oct 10, 2013 at 7:19 PM, Ryosuke Niwa <rn...@webkit.org> wrote:
> On Thu, Oct 10, 2013 at 7:14 PM, Rik Cabanier <caban...@gmail.com> wrote: > >> On Thu, Oct 10, 2013 at 7:07 PM, Ryosuke Niwa <rn...@webkit.org> wrote: >> >>> The spec. text is also misleading in saying that >>> >>> The drawSystemFocusRing(element) method, when invoked, must run the >>> following steps: >>> >>> If I understood your reply correctly, these are steps that need to be >>> ran continuously? Or is it that steps 2 & 3 must run upon the currently >>> focused element being changed. The specification needs to revised to >>> clarify this. >>> >> >> I think non-normative text or a note could be added to make this more >> clear. In general, the function should be called when the focus changes or >> the element is relocated and the canvas should be redrawn. >> > ... > >> As is, the specification reads as if the author needs to repaint and >>> call drawSystemFocusRing upon focus change. >>> >> >> That is correct and what should happen. >> >> > That seems to contract what you've said earlier: > >> What is an AT? :-) You don't call drawSystemFocusRing when an element is >> focused. You *always* call it and if it is focused, a ring will be drawn. >> In all cases, the accessibility software is notified of the area. >> > (AT stands for http://en.wikipedia.org/wiki/Assistive_technology). > > Am I correct in saying that the author needs to call this function each > and every time an element "inside" the canvas is focused? > No, he needs to ALWAYS call this function wether it's focused or not. > > If so, there is no way for AT to detect/enumerate all focusable areas > upfront to let users know of which areas are focusable (before focusing any > element). > > - R. Niwa >
_______________________________________________ webkit-dev mailing list webkit-dev@lists.webkit.org https://lists.webkit.org/mailman/listinfo/webkit-dev
