RESOLVED FIXED 113899
DOM not visually updating with iOS -webkit-overflow-scrolling:touch
https://bugs.webkit.org/show_bug.cgi?id=113899
Summary DOM not visually updating with iOS -webkit-overflow-scrolling:touch
Charles Carver
Reported 2013-04-03 14:51:09 PDT
Overview If you have a container with -webkit-overflow-scrolling:touch appended to it, a set height, and a span element with a background color that is within the content but outside of the viewport, and then you remove the span element but keep the text, then scroll so that the element is now in the viewport, the background color is still visible. Steps to Reproduce 1) Visit any webpage that meets the conditions above on an iOS device/iOS simulator. For testing purposes, here is an example: http://jsfiddle.net/charlescarver/rdZq4/4/ 2) Drag the container to verify that there is a single span element within the container 3) Drag so that the viewport is back to its original position, then tap the a link that removes the span element 4) Drag down once again and you will see that there is an artifact of the span element, but the span element itself is removed from the DOM Actual Results The span element's background is still present, but the span element is removed from the DOM Expected Results The container is visually updated and the background color is gone along with the span element Build Date & Platform Latest iOS Mobile Safari simulator/Latest iOS Mobile Safari (both tested on 04/03/2013) Additional Builds and Platforms Hasn't been tested on other iOS versions, does not happen in latest Mac OSX 10.8 Safari. Additional Information The bug can be fixed by either removing the -webkit-overflow-scrolling:touch CSS attribute, or adding some code to briefly change the CSS then back again, like so: $(".text").scroll(function () { $(".text").css("color", "blue"); setTimeout(function () { $(".text").css("color", "#000"); }, 1) }); (Note, the examples used on the page and for the fix use jQuery)
Attachments
Radar WebKit Bug Importer
Comment 1 2017-06-02 11:45:54 PDT
Simon Fraser (smfr)
Comment 2 2017-11-09 18:49:06 PST
This got fixed at some point; I can no longer reproduce in iOS 11.
Note You need to log in before you can comment on or make changes to this bug.