Bug 13970 - <mask> (and <pattern> and <filter>) should better handle large buffer requests
Summary: <mask> (and <pattern> and <filter>) should better handle large buffer requests
Status: RESOLVED FIXED
Alias: None
Product: WebKit
Classification: Unclassified
Component: SVG (show other bugs)
Version: 523.x (Safari 3)
Hardware: Mac OS X 10.4
: P2 Normal
Assignee: Nobody
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-06-01 14:10 PDT by Eric Seidel (no email)
Modified: 2011-05-18 10:35 PDT (History)
1 user (show)

See Also:


Attachments
simple test case (opera passes) (462 bytes, image/svg+xml)
2007-06-01 14:10 PDT, Eric Seidel (no email)
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Eric Seidel (no email) 2007-06-01 14:10:10 PDT
<mask> (and <pattern> and <filter>) should better handle large buffer requests

It's possible for a user to inadvertently request a intermediate buffer for <mask>, <pattern>, <filter>, etc. *way* larger than they need.  See the simple <mask> example attached to this bug.

We should be able to build some simple ways to avoid hard failure in these instances.  Some examples:

1.  Always restrict the buffer size to the current clip size.
2.  Pre-caculate the real drawn bounding box of all the contained items before allocating the buffer.

there are probably others.  This bug should cover doing at least something minor to make this test case work.
Comment 1 Eric Seidel (no email) 2007-06-01 14:10:50 PDT
Created attachment 14832 [details]
simple test case (opera passes)
Comment 2 Dirk Schulze 2011-05-18 10:35:52 PDT
A lot changed last year. All three resources are a lot more smarter. The images are just as big as they need to be.