Simon Green

I'm not sold that this provides anything _genuinely_ necessary, not something I'd want to pay a price in terms of bytes and possible performance / complexity for anyway. I hope...

I'm skeptical that it's really required, especially with the extra needs for the different types (props, attributes, events) and because it will impact package sizes + perf (I assume). For...

I don't quite follow - if you're creating a component for public use and want to support the separate attributes then how does the spread operator help _you_? Aren't they...

It works for me, I can't guarantee the API is 100% complete and stable though (although I don't have any changes planned).

It should probably give a more helpful error message to make it clearer though.

That's because I moved my blog from being hosted on GitHub Pages (so the same domain) to a custom blog engine (so the domain is now different). If you go...

The element doesn't generate any tokens itself, it just uses what it's given - that could be a token provided by firebase (with the `auth.getIdToken()` method) or a custom token...

Hard to tell without knowing what else might be on the page. I'm just working to update all my elements to be pure WebComponents so they can be used with...

The `.checked` or `.pressed` properties will give you the current value. Maybe you meant _set_ the initial value instead? You should be able to pass those into the factory function,...

I think the best approach might be to allow control via the event itself (e.g. preventDefault or return false) - I'll have a play around and see what feels right.