| commit | e09244d463695cd9d2b089794ca18f59f1e4a621 | [log] [tgz] |
|---|---|---|
| author | senorblanco@chromium.org <senorblanco@chromium.org@2bbb7eff-a529-9590-31e7-b0007b416f81> | Tue Mar 04 19:05:25 2014 +0000 |
| committer | senorblanco@chromium.org <senorblanco@chromium.org@2bbb7eff-a529-9590-31e7-b0007b416f81> | Tue Mar 04 19:05:25 2014 +0000 |
| tree | cea059927b5908df4fc8f98aa2af4163cc3769cb | |
| parent | 707bd60203ba6d89aaa3061efdba09cefd5b5575 [diff] |
Apply the CTM to the offset in the slow SkOffsetImageFilter path. This was being done in the fast path, but not the slow path. Since I had to rebaseline the offsetimagefilter GM anyway (to accomodate the new test case), I added a red border around the intersection of the (transformed) crop rect and clip rect in each sample, beyond which no pixels should be drawn. Chrome bug: https://code.google.com/p/chromium/issues/detail?id=346362 BUG=skia: R=sugoi@google.com Review URL: https://codereview.chromium.org/186643003 git-svn-id: http://skia.googlecode.com/svn/trunk@13656 2bbb7eff-a529-9590-31e7-b0007b416f81