-
Notifications
You must be signed in to change notification settings - Fork 3.4k
panel: new unsafe-inline styles #11941
Comments
Could we introduce a |
That sounds reasonable to me. Though we probably want to give it a more private looking name like |
In fact, it looks like we already have this class material/src/components/panel/panel.scss Lines 13 to 15 in 269b68e
|
And it's used very close to the code in question (in the child) material/src/components/panel/panel.js Lines 1324 to 1325 in 269b68e
|
And removed in a very similar way material/src/components/panel/panel.js Lines 1952 to 1957 in 269b68e
|
…styles - fix broken link to `setNonce()` docs in Theming Intro - improve `setNonce()` documentation - fix some invalid or inaccurate types, JSDoc, and comments - improve type safety and IDE support by using `@types/angular` more - fix dgeni complaining about dangling links - fix typos Fixes #11941
I was able to remove these new inline styles, but I wasn't able to verify in a separate app that this solves the issue because I wasn't able to reproduce the problem (i.e. I got the same CSP violations with |
…styles - fix broken link to `setNonce()` docs in Theming Intro - improve `setNonce()` documentation - fix some invalid or inaccurate types, JSDoc, and comments - improve type safety and IDE support by using `@types/angular` more - fix dgeni complaining about dangling links - fix typos Fixes #11941
Bug
Demo and steps to reproduce the issue
This blank StackBlitz demo can be used to create a reproduction that demonstrates your issue.
Demo URL (required)*: https://github.com/angular/material/pull/11390/files#diff-b71bb3e10759daf665e48e9bc558dc99R1324
Detailed Reproduction Steps
HEAD
:Or install via NPM with
npm install http://github.com/angular/bower-material#master
Explain the expected behavior
Explain the current behavior
unsafe-inline
forstyle-src
.Discuss the use-case or motivation for changing the existing behavior
Support existing apps using a CSP for security.
List the affected versions of AngularJS, Material, OS, and browsers
Add anything else we should know
This was introduced in PR #11390.
Related Chrome bug that can make the error a bit hard to understand:
https://bugs.chromium.org/p/chromium/issues/detail?id=546106
The text was updated successfully, but these errors were encountered: