- From: stonerboy410 <notifications@github.com>
- Date: Tue, 03 Mar 2020 11:35:18 -0800
- To: w3c/webcomponents <webcomponents@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Tuesday, 3 March 2020 19:35:30 UTC
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 https://github.com/w3c/webcomponents/issues/113#issuecomment-112107526_ -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/w3c/webcomponents/issues/867
Received on Tuesday, 3 March 2020 19:35:30 UTC