[Webkit-unassigned] [Bug 17450] in page anchor and keyboard navigation

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Tue Feb 28 17:38:13 PST 2012


--- Comment #14 from chris fleizach <cfleizach at apple.com>  2012-02-28 17:38:12 PST ---
(In reply to comment #13)
> (In reply to comment #12)
> > [...]
> > Why does this need to be a platform decision? It seems like all we'd want to do is, if a in page link is activated 
> > and focus was on that link, move setFocusedNode() to the anchor if it accepts keyboard focus...
> Makes sense. I just wrote that, "looking at the code, it seemed to me this is a problem that must be addressed in every port separately", but perhaps I'm wrong.
> The root of my guessing is that I've quickly skimmed through the code and saw there were platform specific implementations for chromium and windows, and that made me think there could be some reason for that.
> But maybe (hopefully!) you're right and this can be addressed in one take in cross-platform code.

Mario, are you actively working on this one. I too agree that it's a really bad experience and we should fix it soon

Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

More information about the webkit-unassigned mailing list