-
Notifications
You must be signed in to change notification settings - Fork 46.4k
-
Notifications
You must be signed in to change notification settings - Fork 46.4k
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
React and legacy/custom elements/attributes #2657
Labels
Comments
Currently, unknown attributes don't get passed down to DOM nodes. This is because things like transferring props (https://gist.github.com/sebmarkbage/a6e220b7097eb3c79ab7) would result in too many unknown/noisy properties being passed to the DOM elements. We're aware of the issue, and a solution to the unknown-attribute issue is on the todo list. Duplicate of: #140 |
This was referenced Apr 12, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I noticed that legacy attributes like align, cellpadding, cellspacing wasn't rendered by React (at least on the server side).
It is annoying for me since i was trying to convert our email templating system to use React in order to be able to display them in our frontend app.
The fact is that i'm unable to complete this task with React. It led to another question. How am i supposed to make React and WebComponents work together if custom element/attributes names are filtered by React rendering engine ?
The text was updated successfully, but these errors were encountered: