Summary: | LayoutTests/fast/events/touch/ios/double-tap-for-double-click* test cases are failing | ||||||||
---|---|---|---|---|---|---|---|---|---|
Product: | WebKit | Reporter: | zalan <zalan> | ||||||
Component: | Layout and Rendering | Assignee: | zalan <zalan> | ||||||
Status: | RESOLVED FIXED | ||||||||
Severity: | Normal | CC: | bfulgham, commit-queue, simon.fraser, webkit-bug-importer, wenson_hsieh, zalan | ||||||
Priority: | P2 | Keywords: | InRadar | ||||||
Version: | WebKit Nightly Build | ||||||||
Hardware: | Unspecified | ||||||||
OS: | Unspecified | ||||||||
Attachments: |
|
Description
zalan
2019-06-11 13:07:02 PDT
Created attachment 371871 [details]
Patch
Comment on attachment 371871 [details] Patch View in context: https://bugs.webkit.org/attachment.cgi?id=371871&action=review r=mews > Source/WebKit/Shared/WebPageCreationParameters.cpp:295 > + if (!decoder.decode(parameters.doubleClickForDoubleTapDelay)) Nit - doubleTapForDoubleClick* sounds a bit more appropriate. > Source/WebKit/Shared/WebPageCreationParameters.h:161 > + double doubleClickForDoubleTapDelay { 350 }; Nit - Seconds > Source/WebKit/WebProcess/WebPage/ios/WebPageIOS.mm:809 > + auto distanceBetweenTaps = sqrtf(pow(m_potentialTapLocation.x() - m_lastCommittedTapLocation.x(), 2) + pow(m_potentialTapLocation.y() - m_lastCommittedTapLocation.y(), 2)); Nit - you could probably just subtract the points and use diagonalLengthSquared. Created attachment 371881 [details]
Patch
Comment on attachment 371881 [details] Patch Clearing flags on attachment: 371881 Committed r246347: <https://trac.webkit.org/changeset/246347> All reviewed patches have been landed. Closing bug. Impressive! Do any TestExpectations files need to be updated? Can’t check them now myself. (In reply to Alexey Proskuryakov from comment #7) > Impressive! > > Do any TestExpectations files need to be updated? Can’t check them now > myself. Oh, right! I'll take a look and will update them. |