[Webkit-unassigned] [Bug 39427] Increase limit on number of (i)frames from 200 to 1000.

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Thu May 20 09:44:00 PDT 2010


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





--- Comment #4 from hans at chromium.org  2010-05-20 09:43:59 PST ---
Justification is in the patch to WebCore/ChangeLog. Should I also have put it in as a bug comment? (I'm new here.)


In my testing, both Chrome and Safari handles this well. I tried to find a limit on number of frames in IE and Firefox, but could not find one. User experience gets pretty bad with huge amounts of iframes though (and FF crashed trying to render 12k iframes), so having some limit seems reasonable.

The limit of 200 seemed harsh though. For example, the Vim color scheme test page (http://vimcolorschemetest.googlecode.com/svn/html/index-c.html) is broken in WebKit browsers.

In an IRC chat (excerpt on http://crbug.com/16184) between jorlow and mjs, it was said that the O(N^2) algorithms referred to in the original patch (http://trac.webkit.org/changeset/3707) as the reason for this limit are not used anymore.

So since the underlying reason for this limit is said to be gone, some websites would be un-broken by increasing it, and testing shows that WebKit handles it well, I think we should consider bumping the limit to 1000.

-- 
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