Re: [webcomponents] Should parser extensibility be a design goal? (#113)

> 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.

Hmm I didn't realize `<div>` and `<asdf>` parsed differently. (I hope `<asdf>` and `<span>` parse the same??) I guess in all above posts when I said `<div>` I meant `<asdf>`. Which raises the question of whether anyone wants `<div>` behavior. Hopefully not.

> 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.

Well, there'd need to be some abstraction at least, to distinguish the character sequence `</script>` from `</custom-thingy>` or whatever. Which seems like it might be enough of a cost to just go with a new mode.

---
Reply to this email directly or view it on GitHub:
https://github.com/w3c/webcomponents/issues/113#issuecomment-112111307