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.

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

BEMTREE should never escape content #500

Open
tadatuta opened this issue Feb 4, 2018 · 1 comment
Open

BEMTREE should never escape content #500

tadatuta opened this issue Feb 4, 2018 · 1 comment

Comments

@tadatuta
Copy link
Member

tadatuta commented Feb 4, 2018

I think there's no reason to use escaping in BEMTREE at all, is there?

At least we should switch it off by default.

// cc @miripiruni @zxqfox @veged

@miripiruni
Copy link
Contributor

miripiruni commented Feb 5, 2018

I think there's no reason to use escaping in BEMTREE at all, is there?

Nope. Let's take it away from BEMTREE.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants