-
Notifications
You must be signed in to change notification settings - Fork 34
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
Error when meta content includes quote #44
Comments
My workaround:
Only for MPA without front-ending routing |
@tizmagik Seems like there is something wrong with selector builder |
Yea, this is the same issue as #16 -- I think we just need to escape the selector |
Using content as query isn't quite smart( content can be various and very long) |
We need some kind of deterministic key that we are aware of/control on both server and client side — open to suggestions! Edit: Hm, actually maybe we only need to know that react-head places the tags, so maybe we don’t need such a deterministic key? |
Seems buildSelector is used to remove SSR tags only, Need to select a name that will not be used by others, like "__ssr__" (kind of python style) |
We already use |
So just delete all |
I think so, that should work. Would you be able to submit a PR and try it out? |
Ref #44 In this diff I remove selector builder in favour of querying and removing all SSR tags. This should fix the problem with language characters and unescaped quotes.
Ref #44 In this diff I remove selector builder in favour of querying and removing all SSR tags. This should fix the problem with language characters and unescaped quotes.
This is now fixed with the latest v3.0.0 release. Please feel free to open a new issue if there's still any problems. |
Version: v3.0.0
Error stack:
Quite serious that page just gone white.
It seems cause of meta content which include double quote mark(")
Maybe do not use content as part of querySelector? (or perform suitable escaping before query)
And, I only want head tags performs on server, and leave it alone at client side (My MPA do not use front-ending routing), Maybe add some option to do this.
The text was updated successfully, but these errors were encountered: