Joe Pea

Maybe this can be closed unless there's a clear benefit. We can avoid designing class decorators in such a way as the linked issue. For example, instead of something like...

[AssemblyScript](http://assemblyscript.org/) is TypeScript that compiles to WebAssembly, but it has some incompatible additional features like decorators for functions (I haven't checked how hoisting works, also don't use AS function decorators...

Another question may be: how do we tell httrack to fetch resources outside of the domain (--near) but to not get the entire sites, just the assets it needs? I...

Well, turns out I don't need the github stuff, so just using `-*github.com*` as a filter works for me.

It's just a ttf file, so I can probably just easily add some post processing to get that one file and modify the URL. Good thing it's not like a...

Yeah, good food for thought. I'm digging into it now. I'll report back if I come up with anything implementation-wise, or if I find some pattern to deal with it...

I wrote an example too, let me post when I get on laptop. We would also need to consider that custom attributes can be defined later, asynchronously, at any point...

I meant, ```js if(doc.contains(element)) { return Promise.resolve(); } ``` would surely tell attributes are ready for the element, but not necessarily Custom Attribute instances. But maybe only the initial attributes...

Here's an initial implementation but not quite working yet: https://github.com/matthewp/custom-attributes/compare/master...trusktr:attribute-ready-promise It's on top of the changes I made in #17, so you'll see those in the diff too. Usage is...

Interestingly, I've used your `custom-attributes` to implement a generic `has=""` attribute that I'm calling "element-behaviors" which I'll publish at https://github.com/trusktr/element-behaviors soon (original idea [here](https://github.com/w3c/webcomponents/issues/662#issuecomment-327945806)).