-
Notifications
You must be signed in to change notification settings - Fork 353
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Avoid inline-styling to meet tighter content-security-policy #2606
Comments
Interesting... thanks for this! Since you are referencing the table, I took a quick glance at this (although I realize this is a global thing related to current Css-In-JS libs). It looks like it may be easiest to add support for this by using Emotion's Related issues: Emotion |
Hi @KKoukiou is this a blocking issue for you? |
@priley86 - we should be avoiding use of the inject function within react styles wherever possible. Toolbar is being replaced by work happening now (it hasn't made it to react yet), but as for topology and the table packages, those should be importing from a css file so we don't use a style tag. cc: @jeff-phillips-18 since topology is mentioned, too |
@dgutride - ok, good to know. Yes i seem to recall this now (that we can avoid |
@dgutride do you have a suggestion as far as inline css goes? I believe the InlineEdit CSS is currently only impacting those consuming the |
Oh yes, Cockpit has strict CDP, we don't allow inline-styling. In addition, this issue does not appear only when consuming As I mentioned in the issue description, I see this when importing the Table component from patternfly-react-table. But I it's happening with other components from @patternfly/react-core. |
To make use of the patternfly-react in projects with higher security demands, like the Cockpit (www.cockpit-project.org), modifications/use of style HTML element attribute must be avoided.
I tried to import Table component, and I got the following warning in the browser:
Looks like that some of your component are injecting styles into the html.
Can we use css for that?
The text was updated successfully, but these errors were encountered: