Following up from bug #30491, we should make the test cases:
work without using DRT's EventSender. Instead, we should rewrite these tests to use DOM keyboard events.
Created attachment 43241 [details]
Tries to programmatically fire a keypress DOM KeyboardEvent at an HTMLInputElement with keyIdentifier = "Enter" to submit the form (that is, to simulate what equivalent action when the user gives the input focus and then presses the Return/Enter key on the keyboard)
Using a debugger to trace the execution of DOM KeyboardEvents, we need to fix bug #16735 in order to fix this bug.
Running the attachment Example <https://bugs.webkit.org/attachment.cgi?id=43241>, we see that the call flow is as follows (*):
For completeness, before executing (*), the DOM keyboard event is first instantiated via the following call flow:
Note, specifically the constructor KeyboardEvent::KeyboardEvent() is called. Hence, m_keyEvent := 0.
Then, the DOM keyboard event is initialized via the call flow:
'isindex' is removed and now historical.
WPT test showing it as historical - http://wpt.live/html/semantics/forms/historical.html
and both of these tests are now removed (in above commit).
So marking this as 'RESOLVED WONTFIX'.