Bug 129394
| Summary: | Cancel load when image exceeds Settings::maximumDecodedSize() | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Daniel Bates <dbates> |
| Component: | Page Loading | Assignee: | Daniel Bates <dbates> |
| Status: | RESOLVED WONTFIX | ||
| Severity: | Normal | CC: | ap |
| Priority: | P2 | ||
| Version: | 528+ (Nightly build) | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
Daniel Bates
Currently when an image exceeds Settings::maximumDecodedSize() we continue the load. Instead we should cancel the load for such an image.
Note, we may want to differentiate between an image that is loaded as a sub resource of a page from an image loaded as a document (i.e. navigating to an image resource directly) and have different maximum decoded size limits.
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
Daniel Bates
I noticed this bug when analyzing the cause for bug #127029.
Daniel Bates
We decided to remove the setting Settings::maximumDecodedSize() and its related logic in bug #131057 as it has various shortcomings, including the one represented by this bug. Should it turn out that we need such a setting then we should look to implement it again taking care to address this bug among other issues.