[Webkit-unassigned] [Bug 141653] New: Huge blur request causes WebKit to treat blur as a no-op

[bugzilla-daemon at webkit.org]

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

            Bug ID: 141653
           Summary: Huge blur request causes WebKit to treat blur as a
                    no-op
    Classification: Unclassified
           Product: WebKit
           Version: 528+ (Nightly build)
          Hardware: All
                OS: All
            Status: NEW
          Severity: Normal
          Priority: P2
         Component: Layout and Rendering
          Assignee: webkit-unassigned at lists.webkit.org
          Reporter: bfulgham at webkit.org

The test case "css3/filters/huge-blur-value.html" is treated as a no-op in ToT WebKit. Instead of performing a blur operation, WebKit incorrectly determines that the blur region does not intersect with the dirty rect for the paint operation.

In the safari-600.5-branch branch, we correctly determine that the two regions do intersect, and attempt to perform he blur operation -- though we time out due to the massive size of the blur operation.

Therefore, we have two problems:

1. In ToT, we incorrectly determine that there is no work to be done. The test "css3/filters/huge-blur-value.html" does not notice this and treats it as a pass.
2. In the "safari-600.5-branch", we correctly determine that a blur operation must be done, but it takes so long to perform that the test times out.

We need to correct the layout arithmetic in ToT so that we recognize that work must be done. We must also determine an upper bound for our blur operations so that a malformed blur request does not result in a timeout/locked up system.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.webkit.org/pipermail/webkit-unassigned/attachments/20150216/138ed17e/attachment-0002.html>