Summary: | [ContentChangeObserver] Gmail text editing controls require two taps | ||||||
---|---|---|---|---|---|---|---|
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, zalan | ||||
Priority: | P2 | Keywords: | InRadar | ||||
Version: | WebKit Nightly Build | ||||||
Hardware: | Unspecified | ||||||
OS: | Unspecified | ||||||
Attachments: |
|
Description
zalan
2019-06-04 13:33:15 PDT
Created attachment 371336 [details]
Patch
Comment on attachment 371336 [details] Patch View in context: https://bugs.webkit.org/attachment.cgi?id=371336&action=review > Source/WebCore/page/ios/ContentChangeObserver.cpp:98 > + return element.Element::willRespondToMouseClickEvents(); Ugh. Would it be nicer to add an argument to willRespondToMouseClickEvents() saying whether it's for the touch callout? (In reply to Simon Fraser (smfr) from comment #2) > Comment on attachment 371336 [details] > Patch > > View in context: > https://bugs.webkit.org/attachment.cgi?id=371336&action=review > > > Source/WebCore/page/ios/ContentChangeObserver.cpp:98 > > + return element.Element::willRespondToMouseClickEvents(); > > Ugh. Would it be nicer to add an argument to willRespondToMouseClickEvents() > saying whether it's for the touch callout? Let me think about it. Comment on attachment 371336 [details] Patch Clearing flags on attachment: 371336 Committed r246096: <https://trac.webkit.org/changeset/246096> All reviewed patches have been landed. Closing bug. |