[Webkit-unassigned] [Bug 116046] In Voice over, activating a fragment URL should transfer focus and caret to the destination

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Mon Apr 11 14:06:44 PDT 2016


https://bugs.webkit.org/show_bug.cgi?id=116046

--- Comment #24 from Ryosuke Niwa <rniwa at webkit.org> ---
(In reply to comment #23)
> (In reply to comment #22)
> > (In reply to comment #21)
> > >
> > > I'm following this spec
> > > https://html.spec.whatwg.org/multipage/interaction.html#sequential-focus-
> > > navigation-starting-point
> > > I think it's reasonable to have some fallback node in case the starting node
> > > is removed. We don't want to jump to the top of document, right?
> > 
> > Which part of the spec says how we should deal with a removed node?
> 
> I think there's only fixup rules for focusing. 
> Chrome has this situation covered:
> https://developers.google.com/web/updates/2016/03/focus-start-point?hl=en
> So I thought it would be nice for us to have it too.
> 
> If you don't think it's necessary for us to handle this case based on the
> spec, I can just simply reset the starting node when it has been removed.

In general, we would like our behavior to be interoperable with other browsers. And the way to do that will be following standards as well as improving the standards themselves as needed.

Having some sort of fallback behavior seems useful here but that should probably be precisely specified in the relevant spec (HTML specification in this case) if it's not done so already.  As far as I read the section you mentioned, I can't see any mentioning of what happens when a node is removed.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.webkit.org/pipermail/webkit-unassigned/attachments/20160411/df479551/attachment.html>


More information about the webkit-unassigned mailing list