Skip to content

Conversation

gaearon
Copy link
Collaborator

@gaearon gaearon commented Oct 10, 2017

Fixes #10772.

I opted for the fix suggested by @webcarrot in #10772 (comment).

It seems like the easiest and I don’t see a realistic situation in which it wouldn’t work. I guess it could break if you rendered <femorphology> on the server but <feMorphology> on the client, but who would possibly do that?

@gaearon
Copy link
Collaborator Author

gaearon commented Oct 10, 2017

@sebmarkbage

@gaearon gaearon mentioned this pull request Oct 10, 2017
19 tasks
Copy link
Collaborator

@sebmarkbage sebmarkbage left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think this makes sense. We are assuming that any other incorrect casing would not work as expected and therefore would get fixed.

@gaearon gaearon merged commit f42dfcd into facebook:master Oct 10, 2017
@gaearon gaearon deleted the svg-bugfix branch October 10, 2017 18:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Unexpected SSR difference warning with SVG <filter> primitives
3 participants