Chrome does not recognize 'as=worker' as valid attribute in preload link; workers thus cannot be preloaded
Reported by
brodhead...@gmail.com,
Dec 30
|
|||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 6.3; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/71.0.3578.98 Safari/537.36 Steps to reproduce the problem: 1. Create a standard HTML page with <link rel=preload as=worker href=anything.js> in head. 2. Open page in Chrome and open Dev Tools 3. The console will display <link rel=preload> must have a valid `as` value. 4. The attached index.html file may be used to test this. What is the expected behavior? Worker scripts should be preloaded with <link rel=preload as=worker href=anything.js>. What went wrong? Chrome does not recognize "as=worker" as valid attribute for preload links, even though they are in the spec. See: 1) https://developer.mozilla.org/en-US/docs/Web/HTML/Preloading_content#What_types_of_content_can_be_preloaded 2) https://w3c.github.io/preload/#as-attribute Worse, I cannot preload my worker scripts at all. Neither as=worker nor as=script will work in preload link for a worker script. Did this work before? N/A Does this work in other browsers? N/A Chrome version: 71.0.3578.98 Channel: stable OS Version: 6.3 Flash Version: This affects my Lighthouse/PageSpeedInsights score, as the false errors reported by Chrome count against the site (they report "errors logged to console" and demerit the score for the site.) Lighthouse complains that the scripts should be preloaded, but they cannot be, as Chrome does not recognize the "as=worker" type nor responds when it is changed (experimentally) to "as=script".
,
Jan 1
Able to reproduce the issue on the reported chrome version #71.0.3578.98 using Windows 10, Ubuntu 17.10 and Mac OS 10.13.6 by following steps as per comment#0. The behaviour is observed from M-60 builds (#60.0.3112.113). This is a non-regression issue hence marking it as untriaged and requesting someone from the dev team to look into the issue. Thanks.!
,
Jan 1
++ correction Able to reproduce the issue on reported chrome version #71.0.3578.98 and latest chrome #73.0.3657.0 using Windows 10, Ubuntu 17.10 and Mac OS 10.13.6 by following steps as per comment#0.
,
Jan 2
|
|||
►
Sign in to add a comment |
|||
Comment 1 by vamshi.kommuri@chromium.org
, Dec 31