Re: [w3c/webcomponents] Agenda for W3C TPAC 2017 (Web Components) (#641)

Salutations @annevk. Be careful what you ask for. Just may get it _(especially when my career as an evangelist is starting to depend on the status of this)_ #664. Just dotting all the "I"s and crossing all the "T"(PAC)s 😎 

If accepted as a good curation may want to add #664 along with #661 to the topics of discourse. Otherwise, kill it with fire. I'm a New Yorker. tough skin, won't be upset. 💪 🍎 

I'm not sure of discussion regarding future features however since the last TPAC meeting there seems to be valuable interest in the following. These feel more `v2` ish and prefer leaving them here for fear of the bikeshed. Added my own personal experience and thoughts as well based on the past couple years dealing with custom elements deliberation. Please take as an ephemeral grain of salt _(unless interested)_:

- [ ] Namespacing _(elements and attributes)_
- [ ] Self closing / void tags. _(e.g. `<x-foo> <!-- </x-foo> -->`)_ _([discussion](https://github.com/w3c/webcomponents/issues/113) & https://github.com/w3c/webcomponents/issues/624#issuecomment-292067997)_

Seems to be much related to namespacing _(See https://github.com/w3c/webcomponents/issues/634,
 [Section 4.3](https://w3c.github.io/webcomponents/spec/custom/#html:-creating-and-inserting-nodes) and [Section 4.4](https://w3c.github.io/webcomponents/spec/custom/#html:-parsing-xhtml-documents))_ `<acme-plastic-button>` vs. `<acme:plastic-button>`

It was actually _"fun"_ perusing the specs. Bug trackers not so much. 


-- 
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/641#issuecomment-327779159