mash: Chrome window frame/content painting issues on startup. |
|||||
Issue descriptionmash: Chrome window frame/content painting issues on startup. On ToT @ #549307 build chrome os on linux desktop. (1) Run chrome --enable-features=Mash (with a fresh user-data-dir) (2) Observe maximized browser window. Expected: Window is painted correctly Actual: Window has black areas, client portions are inset too much. Seems like the client portions of the browser window are sized/positioned wrong. (tab strip, location bar, and content are arranged for a smaller window. See attached screenshots. CC'ing folks that might know what's going on.
,
Apr 19 2018
,
Apr 26 2018
This might be a LocalSurfaceId issue. Adding myself as OWNER. I will look at it shortly.
,
Apr 26 2018
,
Apr 26 2018
I think this used to work correctly, so it might be bisect-able.
,
May 30 2018
It's possible this is related to WindowSizer and BrowserFrameMash, see issue 764009 . Sky might make some changes to BrowserFrameMash, so this isn't urgent, and if it doesn't look like a surface id issue, probably not worth working on right now.
,
Aug 13
Passing back to jamescook@. Given ws2 is now happening, is this still an issue?
,
Aug 13
I have not seen this in a long time (months?).
,
Aug 13
I don't see this anymore. The initial window open seems a little janky on device, but I don't see the black areas. |
|||||
►
Sign in to add a comment |
|||||
Comment 1 by jamescook@chromium.org
, Apr 16 2018Components: Internals>Services>Ash