fast/events/objc-event-api is sometimes failing, with diffs that look like this: @@ -197,14 +197,13 @@ eventPhase: 3 bubbles: 1 cancelable: 1 -EDITING DELEGATE: shouldChangeSelectedDOMRange:range from 4 of #text > DIV > BODY > HTML > #document to 4 of #text > DIV > BODY > HTML > #document toDOMRange:range from 4 of #text > DIV > BODY > HTML > #document to 0 of P > BODY > HTML > #document affinity:NSSelectionAffinityDownstream stillSelecting:FALSE -EDITING DELEGATE: webViewDidChangeSelection:WebViewDidChangeSelectionNotification +EDITING DELEGATE: shouldChangeSelectedDOMRange:range from 4 of #text > DIV > BODY > HTML > #document to 4 of #text > DIV > BODY > HTML > #document toDOMRange:range from 4 of #text > DIV > BODY > HTML > #document to 4 of #text > DIV > BODY > HTML > #document affinity:NSSelectionAffinityDownstream stillSelecting:FALSE event type: mousedown target: <div> eventPhase: 3 bubbles: 1 cancelable: 1 - detail: 3 + detail: 2 view: OK (document: OK) button: 0 clientX: 400
oops. didn't mean to do that.
Nearest test case when this was raised, I found following commit: https://github.com/WebKit/WebKit/commit/79ac0af0bd3c6480187980effc2aafc9edcb72b2 Which seems to reflect this test was failing due to Webkit Tool not properly sending mouseup event. Additionally, it is not in SKIP list etc. but only in Test Expectations list for WK2: https://github.com/WebKit/WebKit/blob/422c18c5dba37299622f8634c99d776ec1b017f9/LayoutTests/platform/wk2/TestExpectations#L573 ^ Although it seems that it is updated to use test runner by rniwa in this commit: https://github.com/WebKit/WebKit/commit/5fe8b70a0338847b16f9c4ebe6e41668c9a53a9a Do we need to track this old layout test failure? or we can close it since now test is passing.