RESOLVED FIXED Bug 198275
[Pointer Events] Test at pointerevents/ios/touch-action-none-in-overflow-scrolling-touch.html times out 
https://bugs.webkit.org/show_bug.cgi?id=198275
Summary [Pointer Events] Test at pointerevents/ios/touch-action-none-in-overflow-scro...
Antoine Quint
Reported 2019-05-27 08:31:29 PDT
The test at pointerevents/ios/touch-action-none-in-overflow-scrolling-touch.html is timing out since we switched to the new touch-action implementation with paint-time data.
Attachments
Patch (2.04 KB, patch)
2019-05-27 08:34 PDT, Antoine Quint 		no flags
DetailsFormatted DiffDiff
View All Add attachment proposed patch, testcase, etc.
Antoine Quint
Comment 1 2019-05-27 08:31:41 PDT
<rdar://problem/50618496>
Antoine Quint
Comment 2 2019-05-27 08:34:36 PDT
Created attachment 370692 [details] Patch
Antti Koivisto
Comment 3 2019-05-27 08:40:33 PDT
Comment on attachment 370692 [details] Patch Test?
Antoine Quint
Comment 4 2019-05-27 08:50:14 PDT
(In reply to Antti Koivisto from comment #3) > Comment on attachment 370692 [details] > Patch > > Test? This fixes an existing test :)
WebKit Commit Bot
Comment 5 2019-05-27 09:19:12 PDT
Comment on attachment 370692 [details] Patch Clearing flags on attachment: 370692 Committed r245795: <https://trac.webkit.org/changeset/245795>
WebKit Commit Bot
Comment 6 2019-05-27 09:19:14 PDT
All reviewed patches have been landed. Closing bug.
Antti Koivisto
Comment 7 2019-05-27 10:59:23 PDT
> This fixes an existing test :) Was expecting removal from TestExpectations or something.
Antoine Quint
Comment 8 2019-05-28 00:46:21 PDT
(In reply to Antti Koivisto from comment #7) > > This fixes an existing test :) > > Was expecting removal from TestExpectations or something. It was timing out but this had never been marked in TestExpectations which were still expecting a consistent PASS. This is addressed now.
WebKit Commit Bot
Comment 9 2019-05-28 16:21:49 PDT
Re-opened since this is blocked by bug 198310
Tim Horton
Comment 10 2019-05-28 17:06:36 PDT
I stopped the rollout
Note You need to log in before you can comment on or make changes to this bug.