Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Non-string types are handled inconsistently between javascript and html escaping #802

Open
tomalexander opened this issue May 24, 2020 · 0 comments
Open

Non-string types are handled inconsistently between javascript and html escaping #802

tomalexander opened this issue May 24, 2020 · 0 comments

Comments

@tomalexander
Copy link

With the template

{name|h|js}{~n}
{name|j|js}{~n}

and the context

{"name": true}

You get the output

"true"
true

So it seems that html escaping turns non-string types into string, but javascript escaping does not.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@tomalexander