Bug 150974
Summary: | Dynamic content in '-webkit-scrolling-touch' scrollable container breaks scrolling | ||
---|---|---|---|
Product: | WebKit | Reporter: | Thomas Kelly <thomas.kelly> |
Component: | CSS | Assignee: | Nobody <webkit-unassigned> |
Status: | RESOLVED DUPLICATE | ||
Severity: | Normal | CC: | bdakin, simon.fraser, vladymirsch, webkit-bug-importer, webkit |
Priority: | P2 | Keywords: | InRadar |
Version: | Safari 9 | ||
Hardware: | iPhone / iPad | ||
OS: | iOS 9.0 |
Thomas Kelly
Summary:
When the content of a scrollable container using '-webkit-overflow-scrolling: touch' changes height from being smaller then the container to larger, the container is not scrollable.
Steps to Reproduce:
1. Open this CodePen in iOS9 Safari http://s.codepen.io/t-kelly/debug/qOowZR
2. Touch the first container using '-webkit-overflow-scrolling: touch' expand the content.
3. Notice how it cannot be scrolled.
4. Touch the other containers not using '-webkit-overflow-scrolling: touch' and then notice how they are still scrollable.
Expected Results:
A container using '-webkit-overflow-scrolling: touch' should be scrollable when the content inside it changes in height and requires scrolling.
Actual Results:
Content inside a container using '-webkit-overflow-scrolling: touch' is not scrollable
Attachments | ||
---|---|---|
Add attachment proposed patch, testcase, etc. |
Radar WebKit Bug Importer
<rdar://problem/23449687>
Chris Rebert
I can't reproduce this with the given testcase in the Simulator for iOS 9.3.
vladymirsch
Does "scrollable" mean "container not scrollable at all" or "container doesn't have a rendered scrollbar but can be scrolled"?
...if "container doesn't have a rendered scrollbar but can be scrolled" then it may be reproduced not from just one try.
I tapped 8 times and tried to scroll, on 9 time scrollbar disappeared but container could be scrolled.
More info at https://discussions.apple.com/message/32681209#message32681209
Reproduced on iPad, iOS 10.0, 11.0
Simon Fraser (smfr)
Forward dup (sorry).
*** This bug has been marked as a duplicate of bug 158342 ***