-
Notifications
You must be signed in to change notification settings - Fork 46.6k
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
Server side rendering: "Warning: <linearGradient /> is using uppercase HTML. Always use lowercase HTML tags in React." #10415
Labels
Comments
Looks like server side is missing the namespace check. |
sophiebits
added a commit
to sophiebits/react
that referenced
this issue
Aug 13, 2017
sophiebits
added a commit
to sophiebits/react
that referenced
this issue
Aug 13, 2017
sophiebits
added a commit
to sophiebits/react
that referenced
this issue
Aug 13, 2017
sophiebits
added a commit
that referenced
this issue
Aug 13, 2017
Oh, seems like I'm getting this issue too. In my case, I'm using Error: React: 16.12.0 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Do you want to request a feature or report a bug?
Report a bug.
What is the current behavior?
Whenever I render SVG elements that are camel cased (e.g.
<linearGradient />
) on the server side, I get the following warning:What is the expected behavior?
Warnings should be consistent with the client side rendering, if possible. In this case, I'd expect no warning, since using camel cased SVG element names is pretty standard.
For client side rendering, there seems to be a check for the current namespace:
react/src/renderers/dom/fiber/ReactDOMFiberComponent.js
Lines 344 to 352 in efcac24
For server side rendering, there seems to be currently no such check in place:
react/src/renderers/shared/server/ReactPartialRenderer.js
Lines 537 to 544 in 81706ee
Which versions of React, and which browser / OS are affected by this issue? Did this work in previous versions of React?
Hitting this on 16.0.0-beta.5. Was not hitting it on 15.6.1, the version I was previously on.
Thanks in advance.
The text was updated successfully, but these errors were encountered: