New issue
Advanced search Search tips

Issue 902377 link

Starred by 1 user

Issue metadata

Status: Available
Owner: ----
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Windows , Mac
Pri: 2
Type: Bug



Sign in to add a comment

Blur filter is not properly clipped when composited

Project Member Reported by masonfreed@chromium.org, Nov 6

Issue description

Chrome Version: 70.0.3538.77 (Official Build) (64-bit)
OS: Linux

See the attached (proposed) layout test. The red box that is composited escapes the clip, while the same box in non-composited works
correctly.

I believe I have also seen cases (though I'm having a harder time coming up with a simple test case) where it looks like the boundary condition assumption for the blur filter is also different. In the composited case, the filter looks like it brings in white edge pixels, while non-composited assumes that the edge pixel extends past the boundary (?). This comment probably doesn't help, but I wanted to put it somewhere. I have a convoluted example that shows this, and can attach it if desired.
 
blur-composited-vs-noncomposited.html
566 bytes View Download
blur-composited-vs-noncomposited-expected.html
534 bytes View Download
Screenshot.png
14.1 KB View Download
Labels: Needs-Triage-M70
Cc: swarnasree.mukkala@chromium.org
Labels: -Pri-3 Triaged-ET Target-72 M-72 FoundIn-71 FoundIn-70 FoundIn-72 OS-Linux OS-Mac OS-Windows Pri-2
Status: Untriaged (was: Unconfirmed)
Able to reproduce the issue on reported chrome version #70.0.3538.77 and latest chrome #72.0.3604.0 using Windows 10, Mac OS 10.13.6 and Ubuntu 17.10 by following steps as per comment#0.

The behavior is seen from old M-60 builds(#60.0.3112.78). This is a non-regression issue, hence marking it as untriaged and requesting someone from the dev team to look into the issue.
Thanks.!
Status: Available (was: Untriaged)

Sign in to add a comment