<html>
<head>
<base href="https://bugs.webkit.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_ASSIGNED "
title="ASSIGNED - In Voice over, activating a fragment URL should transfer focus and caret to the destination"
href="https://bugs.webkit.org/show_bug.cgi?id=116046#c23">Comment # 23</a>
on <a class="bz_bug_link
bz_status_ASSIGNED "
title="ASSIGNED - In Voice over, activating a fragment URL should transfer focus and caret to the destination"
href="https://bugs.webkit.org/show_bug.cgi?id=116046">bug 116046</a>
from <span class="vcard"><a class="email" href="mailto:n_wang@apple.com" title="Nan Wang <n_wang@apple.com>"> <span class="fn">Nan Wang</span></a>
</span></b>
<pre>(In reply to <a href="show_bug.cgi?id=116046#c22">comment #22</a>)
<span class="quote">> (In reply to <a href="show_bug.cgi?id=116046#c21">comment #21</a>)
> >
> > I'm following this spec
> > <a href="https://html.spec.whatwg.org/multipage/interaction.html#sequential-focus">https://html.spec.whatwg.org/multipage/interaction.html#sequential-focus</a>-
> > 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?</span >
I think there's only fixup rules for focusing.
Chrome has this situation covered:
<a href="https://developers.google.com/web/updates/2016/03/focus-start-point?hl=en">https://developers.google.com/web/updates/2016/03/focus-start-point?hl=en</a>
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.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>