Viewport width client hint value on navigation request should be computed from the UI window size |
||||||
Issue descriptionCurrently, the value of the viewport width on the main frame request is computed from the size of the primary display. However, when the Chrome window is not maximized, this value may be different than the actual viewport width. To compute the correct viewport width on main frame requests, the navigation request has to be tied to the UI window that initiated the request. From there, the navigation request can compute the actual window size.
,
Mar 26 2018
,
Mar 28 2018
,
Mar 29 2018
A consequence of this bug is that the viewport value on main frame requests is incorrect when Chrome Devtools is being used to do device simulation. In that case as well, the viewport size does not match the primary display screen size.
,
Mar 29 2018
Another consequence of the bug is that when multiple monitors are in use, then the viewport size of the tab (aka Chrome window) may not match the primary display screen size.
,
Apr 3 2018
loading triage: tentatively assigned to tbansal since he was fixing similar issues. tbansal@, feel free to release this if you have no plan to work on this.
,
Oct 23
Unassigning myself since I may not have time to work on it in the near future. |
||||||
►
Sign in to add a comment |
||||||
Comment 1 by tbansal@chromium.org
, Mar 26 2018