[webcomponents] self-documenting component.html files

Hi all, a short while back I'd been working on a web components demo, with one result being a components.html that also acted as its own documentation (since as a components.html anything that isn't 'more components', script, or element, gets ignored), which sparked a small discussion on how

Re: [webcomponents] self-documenting component.html files

Mutation Events (or rather, mutation observers) when we have Object.defineProperty getter/setters don't make the most sense. The getter/setter incur virtually no overhead, being baked into JS at the lowest possible level, compared to mutation observers, which are rather heavy hitting things for

[webcomponents] style hooks for custom elements

Hey all, are style hooks still part of any spec relating to web components? Someone pointed out an older demo mentioning them (http://html5-demos.appspot.com/static/webcomponents/index.html) and I can't seem to find mention of them any more. (I like the idea, although the syntax from the demo is

[webcomponents] writing some pages that use webcomponents, and blogging along the way

Hey all, I've been playing with web components and custom elements for a bit, blogging about my understanding of it at http://pomax.nihongoresources.com/index.php?entry=1364168314 and writing a demo for the Mozilla webmaker dev group to see what we can do with them, which is hosted at

[webcomponents] linking using link rel=components href=...?

Hey all, I searched the archive at http://lists.w3.org/Archives/Public/public-webapps/ and checked out the https://dvcs.w3.org/hg/webcomponents/raw-file/tip/spec/templates/index.html#definitions and https://dvcs.w3.org/hg/webcomponents/raw-file/tip/spec/custom/index.html specs, but couldn't find