Access to script.
Reported by
shoeb.pa...@gmail.com,
Dec 9
|
|||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/70.0.3538.110 Safari/537.36 Steps to reproduce the problem: 1. Navigate to chrome://settings/lazy_load.crisper.js 2. chrome://settings/crisper.js 3. What is the expected behavior? chrome://settings/lazy_load.crisper.js chrome://settings/crisper.js should be located under the chrome://resources which is restricted. What went wrong? chrome://settings/crisper.js chrome://settings/lazy_load.crisper.js is located under the settings directory, whereas it should be located under //resources like all other chrome://resources/polymer/v1_0/polymer/polymer-extracted.js Did this work before? N/A Chrome version: 70.0.3538.110 Channel: n/a OS Version: 10.0 Flash Version:
,
Dec 11
,
Dec 12
Able to reproduce the issue on reported chrome version #70.0.3538.110, latest stable #71.0.3578.80 and latest chrome #73.0.3637.0 using Windows 10, Mac 10.13.6 and Ubuntu 17.10 by following steps as per comment#0. The behaviour is seen from M-60(#60.0.3112.113). This is a non-regression issue, hence marking it as untraiged and requesting someone from the dev team to look into it. Thanks.! |
|||
►
Sign in to add a comment |
|||
Comment 1 by susan.boorgula@chromium.org
, Dec 9