<html>
<head>
<base href="https://bugs.webkit.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - <body> with overflow:hidden CSS is scrollable on iOS"
href="https://bugs.webkit.org/show_bug.cgi?id=153852#c3">Comment # 3</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - <body> with overflow:hidden CSS is scrollable on iOS"
href="https://bugs.webkit.org/show_bug.cgi?id=153852">bug 153852</a>
from <span class="vcard"><a class="email" href="mailto:webkit@chrisrebert.com" title="Chris Rebert <webkit@chrisrebert.com>"> <span class="fn">Chris Rebert</span></a>
</span></b>
<pre>Android Chrome already made the behavior change and blazed the trail here:
<a href="https://bugs.chromium.org/p/chromium/issues/detail?id=175502">https://bugs.chromium.org/p/chromium/issues/detail?id=175502</a>
They tracked broken sites in <a href="https://bugs.chromium.org/p/chromium/issues/detail?id=444581">https://bugs.chromium.org/p/chromium/issues/detail?id=444581</a> (and its dupes).
They communicated with several sites and got some to fix their CSS.
In comments 24-25 & 28, they acknowledge some breakage, but don't think there's enough of it to justify switching back:
<a href="https://bugs.chromium.org/p/chromium/issues/detail?id=444581#c24">https://bugs.chromium.org/p/chromium/issues/detail?id=444581#c24</a>
<a href="https://bugs.chromium.org/p/chromium/issues/detail?id=444581#c28">https://bugs.chromium.org/p/chromium/issues/detail?id=444581#c28</a>
I couldn't find any signs of any subsequent revert.
----
If WebKit were to disagree with Chrome's analysis and fear too much breakage,
what would be the path forward?
A new "yes, I really truly want 'hidden' here!" value for the CSS 'overflow' property?</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>