Bug 232306

Summary: Regression (r284821) : [ iOS 15 ] fast/events/ios/submit-form-target-blank-using-return-key.html is a timeout
Product: WebKit Reporter: ayumi_kojima
Component: New BugsAssignee: Nobody <webkit-unassigned>
Status: RESOLVED FIXED    
Severity: Normal CC: cdumez, sam, webkit-bot-watchers-bugzilla, webkit-bug-importer
Priority: P2 Keywords: InRadar
Version: WebKit Nightly Build   
Hardware: iPhone / iPad   
OS: Unspecified   

ayumi_kojima
Reported 2021-10-26 08:29:55 PDT
fast/events/ios/submit-form-target-blank-using-return-key.html Is constantly timing out on iOS 15. History: https://results.webkit.org/?suite=layout-tests&test=fast%2Fevents%2Fios%2Fsubmit-form-target-blank-using-return-key.html Result page: https://build.webkit.org/results/Apple-iOS-15-Simulator-Release-WK2-Tests/r284857%20(317)/results.html Diff: --- /Volumes/Data/worker/ios-simulator-15-release-tests-wk2/build/layout-test-results/fast/events/ios/submit-form-target-blank-using-return-key-expected.txt +++ /Volumes/Data/worker/ios-simulator-15-release-tests-wk2/build/layout-test-results/fast/events/ios/submit-form-target-blank-using-return-key-actual.txt @@ -1,10 +1,11 @@ +CONSOLE MESSAGE: TypeError: null is not an object (evaluating 'window.opener.done') +FAIL: Timed out waiting for notifyDone to be called + Tests that pressing the Return key in a text field with an associated form implicitly submits the form. To run this test by hand, focus the text field below and press the Return key. On success, you will see a series of "PASS" messages, followed by "TEST COMPLETE". + PASS event.key is "Enter" -PASS successfullyParsed is true -TEST COMPLETE -
Attachments
Radar WebKit Bug Importer
Comment 1 2021-10-26 08:30:16 PDT
ayumi_kojima
Comment 2 2021-10-26 08:57:39 PDT
I was able to reproduce the timeout locally using run-webkit-tests --ios-simulator fast/events/ios/submit-form-target-blank-using-return-key.html. The test timed out with r284821 and passed with r284820.
Chris Dumez
Comment 3 2021-10-26 09:03:40 PDT
Note You need to log in before you can comment on or make changes to this bug.