[Webkit-unassigned] [Bug 30055] Bad DOM performance in large SVG files

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Sun Dec 13 12:59:52 PST 2009


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





--- Comment #26 from Oliver Hunt <oliver at apple.com>  2009-12-13 12:59:51 PST ---
(In reply to comment #25)
> (In reply to comment #23)
> > (From update of attachment 41379 [details] [details])
> > I found another testcase where we get pathologically bad perf due to this issue
> > which would imply that there's just too much cost in not clipping prior to
> > calling the graphics library -- my test case just created many many many
> > (~50000 odd) nodes mostly off the screen and this patch represents a huge
> > improvement in that case.
> 
> offscreen:
> It depends. If the SVG size is also bigger than the screensize, we shouldn't
> clip to the currently visible area. smfr remind me, that we can include a SVG
> into a HTML-file and make some 3D transformations (via CSS3) with it. That
> might not work correctly, if the SVG is clipped.

We should simply be clipping to the region that is going to actually be drawn
to, assuming everything is working correctly that is correct -- if i can apply
a 3d transform and that will result in incorrect clipping area then thats a
serious bug in the 3d transform paths

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