-
-
Notifications
You must be signed in to change notification settings - Fork 133
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
important style is not parsed #1302
Comments
@piszczu4 this is expected behavior because this library parses inline styles and inline styles do not support |
Why does not support? Look here: https://codepen.io/degel123/pen/poYOLzE |
@piszczu4 can you provide a reproducible example of this not working for you? |
Here it is: https://codesandbox.io/p/sandbox/parser-hf4g76?file=%2Fsrc%2FApp.tsx%3A30%2C44-30%2C53 If you remove |
@piszczu4 I can't seem to open the CodeSandbox? |
Try this: https://codesandbox.io/p/sandbox/parser-hf4g76?file=%2Fsrc%2FApp.tsx Here is the code:
|
Any feeedbaack? |
Any progress on that one? |
Hello Guys, are you going to fix the issue? |
I've been really busy these days so I haven't had a chance to look into this. If anyone has a solution, feel free to open a PR and I can review it. I did a quick search and it looks like React does not support important inline styles: https://stackoverflow.com/questions/23074748/important-inline-styles-in-react |
Hello @remarkablemark, In our case, the problem is mostly related to some styles being missed after it was processed by the plugin. For instance, we have node: After the conversion becomes: As you can see "color" style is missing. |
@ArtsiomReutovich can replace work as a workaround for you? If it doesn't, a quick hack would be to do a |
Hello @remarkablemark, |
The following is not parsed when using
attributesToProps(domNode.attribs)
:while this is:
Why is that a case?
The text was updated successfully, but these errors were encountered: