Home > Article > Web Front-end > Why Can\'t I Access CSS Rules from a Local File in Chrome 64?
Recently, web developers have encountered an issue where accessing CSS rules from a local CSS file is not possible in Chrome version 64. This issue can be attributed to security changes implemented in the browser.
In the past, Chrome would allow developers to access CSS rules from local files. However, with version 64, this functionality has been restricted. When attempting to access the cssRules property of a stylesheet, developers encounter an undefined response or an error.
<code class="html"><script> window.onload = function() { try { alert(document.styleSheets[0]); // works alert(document.styleSheets[0].cssRules); // undefined } catch (e) { alert(e); // error } } </script> <link rel='stylesheet' href='myStyle.css'> <!-- myStyle.css --> body { background-color: green; }</code>
To address this issue, developers have identified several workarounds:
The root cause of this issue lies in a change in Chrome's security rules. Chrome now adheres to the Cross-Origin Resource Sharing (CORS) policy, which restricts access to resources from different origins. Since local files have a different origin than the HTML file, accessing CSS rules from these files violates the CORS policy.
While the implementation of the CORS policy in Chrome improves security, it has also created some open issues:
The above is the detailed content of Why Can\'t I Access CSS Rules from a Local File in Chrome 64?. For more information, please follow other related articles on the PHP Chinese website!