Summary: | "display: contents" Content click does not trigger | ||||||
---|---|---|---|---|---|---|---|
Product: | WebKit | Reporter: | 709922234 | ||||
Component: | CSS | Assignee: | Antoine Quint <graouts> | ||||
Status: | RESOLVED FIXED | ||||||
Severity: | Normal | CC: | cdumez, cmarcelo, commit-queue, dbates, esprehn+autocc, ews-watchlist, graouts, kangil.han, koivisto, rniwa, webkit-bug-importer, zalan | ||||
Priority: | P2 | Keywords: | InRadar | ||||
Version: | Safari 12 | ||||||
Hardware: | iPhone / iPad | ||||||
OS: | iOS 12 | ||||||
See Also: | https://bugs.webkit.org/show_bug.cgi?id=218923 | ||||||
Attachments: |
|
Description
709922234
2019-06-05 04:14:03 PDT
I can reproduce on an iPhone with shipping iOS, taps indeed are recognized inconsistently. Moreover, on an iPad Pro with iOS 13 beta, they are not recognized as clicks at all. In WebPage::commitPotentialTap() we bail early because m_potentialTapNode->renderer() is false. It might be that we need to also check whether renderOrDisplayContentsStyle() returns something. Created attachment 372052 [details]
Patch
Comment on attachment 372052 [details] Patch Clearing flags on attachment: 372052 Committed r246404: <https://trac.webkit.org/changeset/246404> All reviewed patches have been landed. Closing bug. |