RESOLVED FIXED 203178
[iOS WK2] Support hiding iframe scrollbars via ::-webkit-scrollbar style 
https://bugs.webkit.org/show_bug.cgi?id=203178
Summary [iOS WK2] Support hiding iframe scrollbars via ::-webkit-scrollbar style
Simon Fraser (smfr)
Reported 2019-10-18 18:31:44 PDT
[iOS WK2] Support hiding iframe scrollbars via ::-webkit-scrollbar style
Attachments
Patch (20.08 KB, patch)
2019-10-18 18:34 PDT, Simon Fraser (smfr) 		no flags
DetailsFormatted DiffDiff
Patch (20.06 KB, patch)
2019-10-19 10:34 PDT, Simon Fraser (smfr) 		dino: review+
DetailsFormatted DiffDiff
Show Obsolete (1) View All Add attachment proposed patch, testcase, etc.
Simon Fraser (smfr)
Comment 1 2019-10-18 18:34:51 PDT
Created attachment 381361 [details] Patch
Simon Fraser (smfr)
Comment 2 2019-10-19 10:34:42 PDT
Created attachment 381373 [details] Patch
Dean Jackson
Comment 3 2019-10-19 12:16:34 PDT
Comment on attachment 381373 [details] Patch View in context: https://bugs.webkit.org/attachment.cgi?id=381373&action=review > LayoutTests/fast/scrolling/ios/scrollbar-hiding-iframes-expected.txt:17 > + (total content size width=800 height=600) Where does 800x600 come from? > LayoutTests/fast/scrolling/ios/scrollbar-hiding-iframes-expected.txt:42 > + (max layoutViewport origin (708,866)) Where does this number come from?
Simon Fraser (smfr)
Comment 4 2019-10-19 14:13:01 PDT
Comment on attachment 381373 [details] Patch View in context: https://bugs.webkit.org/attachment.cgi?id=381373&action=review >> LayoutTests/fast/scrolling/ios/scrollbar-hiding-iframes-expected.txt:17 >> + (total content size width=800 height=600) > > Where does 800x600 come from? Default WebKitTestRunner window size. >> LayoutTests/fast/scrolling/ios/scrollbar-hiding-iframes-expected.txt:42 >> + (max layoutViewport origin (708,866)) > > Where does this number come from? Scrolling extent.
Simon Fraser (smfr)
Comment 5 2019-10-21 11:59:39 PDT
https://trac.webkit.org/changeset/251369/webkit
Radar WebKit Bug Importer
Comment 6 2019-10-21 12:00:21 PDT
<rdar://problem/56471145>
Note You need to log in before you can comment on or make changes to this bug.