Quads with subpixel positioning are never getting promoted to HW overlays. |
|||
Issue descriptionChecking why we don't get HW overlays for non integer scale-factors we noticed that quads display_rects might have subpixel position/size. KMS supports subpixel positioning for planes (with fixed point), but Chrome rejects them. Chrome overlay APIs seem to be using gfx::Rect instead of a gfx::Rectf for overlays rects in many places. If we want to use HW overlays in more scenarios, we should change the APIs to use gfx::Rectf, or we need to make sure that quads are aligned to the display pixel grid.
,
Aug 17 2017
Not sure it's necessary to improve the HW overlay code to support this but it definitely wouldn't hurt. The reason we're seeing sub-pixel coordinates for arc apps can be fixed, I think. It's a side-effect of how we handle dynamic density changes and I think it would be fine to snap window locations to the physical pixel grid on the client side.
,
Aug 17 2017
|
|||
►
Sign in to add a comment |
|||
Comment 1 by dcasta...@chromium.org
, Aug 17 2017