Bug 155215 – Element with maximum tabIndex cannot be returned by nextElementWithGreaterTabIndex()

• Status: RESOLVED
• Resolution: FIXED
• Component: DOM

[Chris Dumez]

Element with maximum tabIndex cannot be returned by nextElementWithGreaterTabIndex() due to a bug in <http://trac.webkit.org/changeset/197726>.

[Chris Dumez]

Created attachment 273384 [details]
Patch

[WebKit Commit Bot]

Comment on attachment 273384 [details]
Patch

Clearing flags on attachment: 273384

Committed r197835: <http://trac.webkit.org/changeset/197835>

[WebKit Commit Bot]

All reviewed patches have been landed.  Closing bug.

[Alexey Proskuryakov]

The new test always times out on iOS. Can it be rewritten to work in a cross-platform way?

[Chris Dumez]

(In reply to comment #4)
> The new test always times out on iOS. Can it be rewritten to work in a
> cross-platform way?

In EventSenderProxyIOS.mm:
void EventSenderProxy::keyDown(WKStringRef key, WKEventModifiers modifiers, unsigned keyLocation)
{
    // Write me.
}

iOS does not support EventSender.keydown() :/

[Darin Adler]

But you don’t move focus to the next element by pressing a "tab key" on iOS either. I’m not sure that WebKit on iOS has code that understands the tab character. We might have to write something different to test tabIndex on that platform. Not sure there is a platform independent way of walking through the tab loop.