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

I sort of feel like the default parsing should be <template>, since that can appear anywhere. Definitely not <div>, we don't want to close <p> and such. #867

Closed
stonerboy410 opened this issue Mar 3, 2020 · 0 comments

Comments

@stonerboy410
Copy link

I sort of feel like the default parsing should be <template>, since that can appear anywhere. Definitely not <div>, we don't want to close <p> and such.

While <script> has some complexity, it's not clear to me that introducing a new parser class is better than simply reusing the path <script> already takes.

I agree that <template> inertness is a different feature. Inheritance seems reasonable for that, though might also be composition in part since the parser then puts elements elsewhere. And if <template> ever gains data binding you might want all the parsing implications of <template>, but not data binding...

Originally posted by @annevk in #113 (comment)

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

No branches or pull requests

1 participant