<html>
<head>
<base href="https://bugs.webkit.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - REGRESSION(r188659): Non main frame scrollable areas don't work for pages restored from the page cache"
href="https://bugs.webkit.org/show_bug.cgi?id=153404#c7">Comment # 7</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - REGRESSION(r188659): Non main frame scrollable areas don't work for pages restored from the page cache"
href="https://bugs.webkit.org/show_bug.cgi?id=153404">bug 153404</a>
from <span class="vcard"><a class="email" href="mailto:cgarcia@igalia.com" title="Carlos Garcia Campos <cgarcia@igalia.com>"> <span class="fn">Carlos Garcia Campos</span></a>
</span></b>
<pre>Created <span class=""><a href="attachment.cgi?id=271347&action=diff" name="attach_271347" title="Different WIP approach">attachment 271347</a> <a href="attachment.cgi?id=271347&action=edit" title="Different WIP approach">[details]</a></span>
Different WIP approach
So, according to <a class="bz_bug_link
bz_status_RESOLVED bz_closed"
title="RESOLVED FIXED - Scrollable area container is not properly cleared when page is going into the PageCache"
href="show_bug.cgi?id=148182">bug #148182</a> crashes happen when restoring from page cache because of pointers to ScrollableAreas that has already been removed. So, I think the actual bug is that those ScrollableAreas haven't been unregistered themselves when they were destroyed. RenderListBox and RenderLayer already do that, so I think the bug is in Mac PDFPlugin, and maybe in FrameView. This patch could also fix the crash without having to clear/restore scrollable areas when entering/restoring from the page cache. What do you think?</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>