<html>
<head>
<base href="https://bugs.webkit.org/" />
</head>
<body><span class="vcard"><a class="email" href="mailto:skobes@chromium.org" title="Steve Kobes <skobes@chromium.org>"> <span class="fn">Steve Kobes</span></a>
</span> changed
<a class="bz_bug_link
bz_status_NEW "
title="NEW - stop propagating custom scrollbar styles across iframe boundaries"
href="https://bugs.webkit.org/show_bug.cgi?id=149489">bug 149489</a>
<br>
<table border="1" cellspacing="0" cellpadding="8">
<tr>
<th>What</th>
<th>Removed</th>
<th>Added</th>
</tr>
<tr>
<td style="text-align:right;">CC</td>
<td>
</td>
<td>skobes@chromium.org
</td>
</tr></table>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - stop propagating custom scrollbar styles across iframe boundaries"
href="https://bugs.webkit.org/show_bug.cgi?id=149489#c5">Comment # 5</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - stop propagating custom scrollbar styles across iframe boundaries"
href="https://bugs.webkit.org/show_bug.cgi?id=149489">bug 149489</a>
from <span class="vcard"><a class="email" href="mailto:skobes@chromium.org" title="Steve Kobes <skobes@chromium.org>"> <span class="fn">Steve Kobes</span></a>
</span></b>
<pre>FYI, we discussed this in Blink on <a href="http://crbug.com/450577">http://crbug.com/450577</a> and in <a href="https://groups.google.com/a/chromium.org/forum/#!topic/blink-dev/ULUvtsZ-YQY">https://groups.google.com/a/chromium.org/forum/#!topic/blink-dev/ULUvtsZ-YQY</a>.
Consistency between Chrome and Safari was a particular concern since custom scrollbar styles are webkit-prefixed. If WebKit changed this, Blink would probably follow.
The current behavior makes it possible to detect overflow in a cross-origin iframe, which may have security implications (<a href="http://sirdarckcat.blogspot.com/2013/09/matryoshka-wrapping-overflow-leak-on.html">http://sirdarckcat.blogspot.com/2013/09/matryoshka-wrapping-overflow-leak-on.html</a>).</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>