We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
In SSR, a prop value that's a literal string has " characters in it HTML-entity escaped when they should not be.
"
I checked a couple of other characters and didn't see any similar behavior with them, so it's possible it's just the double quote character.
https://svelte-5-preview.vercel.app/#H4sIAAAAAAAACo2OwQrCMBBEf2VZhCiU9l5bQfoZxoO0KQaaZEm2goT8u00LCuLB285jZnYijnpSAetLRHszCms8E2GB_KQswkNNrBYd3Oz7TJrQe018klayNuQ8Q3fX0wCjdwZEWa2q3ILiKG1TfRK22bzkHbVCoqgWurQbN-hRqwFr9rNKxXvMav93Tu9sYIhrOyRoYZevsD98r4iZp1-fr-kFHUxOmBIBAAA=
No response
REPL
annoyance
The text was updated successfully, but these errors were encountered:
only escape attribute values for elements, not components - closes #9454
4a16d62
fix: only escape attribute values for elements, not components (#9456)
6f6c3a0
* only escape attribute values for elements, not components - closes #9454 * changeset --------- Co-authored-by: Rich Harris <rich.harris@vercel.com>
Successfully merging a pull request may close this issue.
Describe the bug
In SSR, a prop value that's a literal string has
"
characters in it HTML-entity escaped when they should not be.I checked a couple of other characters and didn't see any similar behavior with them, so it's possible it's just the double quote character.
Reproduction
https://svelte-5-preview.vercel.app/#H4sIAAAAAAAACo2OwQrCMBBEf2VZhCiU9l5bQfoZxoO0KQaaZEm2goT8u00LCuLB285jZnYijnpSAetLRHszCms8E2GB_KQswkNNrBYd3Oz7TJrQe018klayNuQ8Q3fX0wCjdwZEWa2q3ILiKG1TfRK22bzkHbVCoqgWurQbN-hRqwFr9rNKxXvMav93Tu9sYIhrOyRoYZevsD98r4iZp1-fr-kFHUxOmBIBAAA=
Logs
No response
System Info
Severity
annoyance
The text was updated successfully, but these errors were encountered: