Client hint Viewport-Width has default 980 in device emulation
Reported by
johannes...@sevenval.com,
Jan 4 2018
|
||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/63.0.3239.108 Safari/537.36 Example URL: http://waldbaer.leute.server.de/ch-bugs/ Steps to reproduce the problem: 1. Load given URL with Device Emulation on 2. See the value for Viewport-Width response header in Network Tab of Developer Tools for ext.css and ext.js What is the expected behavior? The Viewport-Width value for both ext.css and ext.js should be the actual viewport width (as with ext.js) What went wrong? The Viewport-Width value for ext.css is the width of the "default" viewport (980) Did this work before? N/A Chrome version: 63.0.3239.108 Channel: stable OS Version: 10.0 Flash Version: This is perhaps due to the request for ext.css being initiated (or even sent?) before the meta viewport element is read. But then, how can this be a useful header value?
,
Jan 5 2018
Able to reproduce this issue on Mac 10.12.6, Win-10 and Ubuntu 14.04 using chrome reported version #63.0.3239.108 and latest canary #65.0.3312.0. This is a non-regression issue as it is observed from M50 old builds. Note: On latest chrome version #65.0.3312.0, Viewport-Width response header is not seen. Hence, marking it as untriaged to get more inputs from dev team. Thanks...!!
,
Jan 5 2018
,
Jan 9 2018
tbansal@, can you triage this issue?
,
Jan 9 2018
I do not think this is related to Devtools since I can repro this without Devtools. Somebody from loading team with understanding of frames would be the best fit to fix this.
,
Jan 9 2018
,
Jan 10
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue. Sorry for the inconvenience if the bug really should have been left as Available. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Jan 11
1. I did not mean Viewport-Width _response_ but request header. 2. With the given test case Chrome does not send client hints because client hints are only available with https. (Unfortunately, the server hosting the test case does not support https, yet). 3. Using the same test case on a server supporting https (and requesting it with https), I see the same (correct) Viewport-Width header for both ext.js and ext.css. So I think, this issue can be closed.
,
Jan 11
Thanks for the update! Closing. |
||||||||
►
Sign in to add a comment |
||||||||
Comment 1 by krajshree@chromium.org
, Jan 4 2018