viz: Reject HW overlays with nearest filter
Canvas can have an "image-rendering: pixelated" css property. In those cases, nearest neighbor filter will be used instead of bilinear. Since we don't do nearest neighbor filter when scanning out buffers via HW overlays, this CL simply rejects the HW overlay path in those cases and always falls back to GPU compositing. Test: SingleOverlayOnTopTest.RejectNearestNeighbor Change-Id: I907998f5a23ed2888ff0b3c53b9d7a938164acdc Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2510649Reviewed-by:Khushal <khushalsagar@chromium.org> Commit-Queue: Daniele Castagna <dcastagna@chromium.org> Cr-Commit-Position: refs/heads/master@{#823414}
Showing
Please register or sign in to comment