Re: [webcomponents] Add "why upgrades" document to proposals section (#112)

This is starting to get off-topic for this particular discussion, but would love to get a better handle on parser extensibility. Should this even be a design goal? It seems that most element-specific parser strategies are things that we would like to avoid in the future. The requests that I've seen are all "make my element behave like a `<template>` element", which seems like it should just be solved by sub-classing. It might be good to just say "parser is done" and avoid complicating things.

---
Reply to this email directly or view it on GitHub:
https://github.com/w3c/webcomponents/pull/112#issuecomment-111529629