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 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
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...
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)
The text was updated successfully, but these errors were encountered: