You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am passing an & character in my openGraph.basic.title field. I verified that the char is correctly passed as a prop into the SEO component, but in my final output it is changed to: <meta property="og:title" content="[...] & [...]">
Any ideas?
The text was updated successfully, but these errors were encountered:
Hey @trueter, thank you for your feedback! I'll need a bit more context for this, though. Does the escaping have any unintended consequences where it doesn't get rendered correctly?
Hey @jonasmerlin - thanks for taking the time to look at this.
I've had another look at it. Some platforms correctly show the ampersand in the preview, others, like https://opengraph.dev/ don't. I would sleep better at night knowing the output is consistent across platforms. In my research I found this thread on the react repo highlighting some use cases of why fine grained control of escaping in open graph strings may be beneficial (like image urls).
I am passing an
&
character in my openGraph.basic.title field. I verified that the char is correctly passed as a prop into the SEO component, but in my final output it is changed to:<meta property="og:title" content="[...] & [...]">
Any ideas?
The text was updated successfully, but these errors were encountered: