[Webkit-unassigned] [Bug 83721] Framesniffing defense is too aggressive.

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Fri Apr 13 10:56:30 PDT 2012


https://bugs.webkit.org/show_bug.cgi?id=83721





--- Comment #8 from Thomas Sepez <tsepez at chromium.org>  2012-04-13 10:56:30 PST ---
Ok.  I don't think I can make the logging happen in a way that matches visual expectations - in Paul's test case, for example, there is a failure to propagate the scroll across the boundary, but we really don't care because the top frame didn't have to scroll.  Short of asking the frame that didn't scroll whether it or its parents would have had to scroll ... seems hard.  And probably too much of a hit for sites that simulate postmessage with fragment navs.

I'll also go with the reset in the FrameLoader as James suggested as the first fix for simplicity.  The path though Layout() may likely be hard to trigger reliably for exploitation.

-- 
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.



More information about the webkit-unassigned mailing list