WebKit Bugzilla
New
Browse
Log In
×
Sign in with GitHub
or
Remember my login
Create Account
·
Forgot Password
Forgotten password account recovery
RESOLVED CONFIGURATION CHANGED
195801
(iOS 12.2) Removing and re-adding pointer-events does not allow element to receive events again
https://bugs.webkit.org/show_bug.cgi?id=195801
Summary
(iOS 12.2) Removing and re-adding pointer-events does not allow element to re...
Liam DeBeasi
Reported
2019-03-15 06:48:36 PDT
Created
attachment 364792
[details]
Scrolling bug xcode project reproduction Current Behavior: When removing and then re-adding pointer events via CSS, the element does not receive events (such as a scroll event) unless there is some other CSS change that causes style recalculations (such as background-color, z-index, etc). Expected Behavior: The element should receive events after having pointer-events re-added. Example: See attached .zip for Xcode project. Steps to reproduce: 1. Run app on any iOS device running the iOS 12.2 beta. 2. Tap "Tap This Button". 3. The app should transition to a new page, a loader should appear, and then a list of names will be rendered. 4. Attempt to scroll the new list (you should not be able to) 5. Tap the "fix scrolling" button. At this point, a CSS recalculation will occur and you will be able to scroll again. Additional Info: This has been tested on iOS 12.2 betas 3-5. Additionally, this issue does not exist on versions of iOS prior to the 12.2 Beta. This issue does not occur in Safari, only in WKWebView. This issue does not occur without "-webkit-overflow-scrolling: touch;" set on the scrollable element.
Attachments
Scrolling bug xcode project reproduction
(5.19 MB, application/zip)
2019-03-15 06:48 PDT
,
Liam DeBeasi
no flags
Details
View All
Add attachment
proposed patch, testcase, etc.
Radar WebKit Bug Importer
Comment 1
2019-03-16 12:07:56 PDT
<
rdar://problem/48955178
>
Antti Koivisto
Comment 2
2019-05-21 10:52:46 PDT
Seems to work fine with trunk.
Note
You need to
log in
before you can comment on or make changes to this bug.
Top of Page
Format For Printing
XML
Clone This Bug