RESOLVED FIXED 190801
Don't waste time under -setupInteraction under -initWithFrame for unparented WKWebViews
https://bugs.webkit.org/show_bug.cgi?id=190801
Summary Don't waste time under -setupInteraction under -initWithFrame for unparented ...
Tim Horton
Reported 2018-10-22 12:49:50 PDT
Don't waste time under -setupInteraction under -initWithFrame for unparented WKWebViews
Attachments
Patch (4.13 KB, patch)
2018-10-22 12:50 PDT, Tim Horton
no flags
Tim Horton
Comment 1 2018-10-22 12:50:11 PDT
Tim Horton
Comment 2 2018-10-22 12:50:13 PDT
Megan Gardner
Comment 3 2018-10-22 12:52:19 PDT
Comment on attachment 352902 [details] Patch Assuming all bots pass
WebKit Commit Bot
Comment 4 2018-10-22 14:22:45 PDT
Comment on attachment 352902 [details] Patch Clearing flags on attachment: 352902 Committed r237331: <https://trac.webkit.org/changeset/237331>
WebKit Commit Bot
Comment 5 2018-10-22 14:22:46 PDT
All reviewed patches have been landed. Closing bug.
Ryan Haddad
Comment 6 2018-10-22 15:59:24 PDT
(In reply to WebKit Commit Bot from comment #4) > Committed r237331: <https://trac.webkit.org/changeset/237331> This appears to have caused API test failures on iOS: Failed TestWebKitAPI.WebKit.InteractionDeadlockAfterCrash /Volumes/Data/slave/ios-simulator-12-release/build/Tools/TestWebKitAPI/Tests/WebKitCocoa/InteractionDeadlockAfterCrash.mm:70 Value of: highlightLongPressRecognizer Actual: false Expected: true /Volumes/Data/slave/ios-simulator-12-release/build/Tools/TestWebKitAPI/Tests/WebKitCocoa/InteractionDeadlockAfterCrash.mm:74 Value of: shouldBegin Actual: false Expected: true Timeout TestWebKitAPI.ActionSheetTests.DismissingActionSheetShouldNotDismissPresentingViewController https://build.webkit.org/builders/Apple%20iOS%2012%20Simulator%20Release%20WK2%20(Tests)/builds/491/steps/run-api-tests/logs/stdio
Tim Horton
Comment 7 2018-10-22 16:34:32 PDT
Technically a good change. I’ll fix it (by parenting the view).
Tim Horton
Comment 8 2018-10-22 18:52:26 PDT
(In reply to Tim Horton from comment #7) > Technically a good change. I’ll fix it (by parenting the view). Ryan, https://trac.webkit.org/changeset/237346/webkit should do the trick.
Ryan Haddad
Comment 9 2018-10-23 08:54:43 PDT
(In reply to Tim Horton from comment #8) > (In reply to Tim Horton from comment #7) > > Technically a good change. I’ll fix it (by parenting the view). > > Ryan, https://trac.webkit.org/changeset/237346/webkit should do the trick. That did indeed! We are still seeing TestWebKitAPI.ActionSheetTests.DismissingActionSheetShouldNotDismissPresentingViewController time out, though. Sorry for not making it clear that both were caused by this change.
Tim Horton
Comment 10 2018-10-23 11:52:58 PDT
(In reply to Ryan Haddad from comment #9) > (In reply to Tim Horton from comment #8) > > (In reply to Tim Horton from comment #7) > > > Technically a good change. I’ll fix it (by parenting the view). > > > > Ryan, https://trac.webkit.org/changeset/237346/webkit should do the trick. > That did indeed! We are still seeing > TestWebKitAPI.ActionSheetTests. > DismissingActionSheetShouldNotDismissPresentingViewController time out, > though. Sorry for not making it clear that both were caused by this change. Interesting! I'll take a peek.
Tim Horton
Comment 11 2018-10-23 13:10:44 PDT
(In reply to Tim Horton from comment #10) > (In reply to Ryan Haddad from comment #9) > > (In reply to Tim Horton from comment #8) > > > (In reply to Tim Horton from comment #7) > > > > Technically a good change. I’ll fix it (by parenting the view). > > > > > > Ryan, https://trac.webkit.org/changeset/237346/webkit should do the trick. > > That did indeed! We are still seeing > > TestWebKitAPI.ActionSheetTests. > > DismissingActionSheetShouldNotDismissPresentingViewController time out, > > though. Sorry for not making it clear that both were caused by this change. > > Interesting! I'll take a peek. Very similar problem, the view isn't in-window. Not sure yet exactly why it's not, since from code inspection it looks like it should be, but it's possible we just have to wait for a transition.
Note You need to log in before you can comment on or make changes to this bug.