Rob Dodson

To clarify a bit more. I've tried to base the test rules on the behavior observed from the built-in elements and their [reflection rules](https://html.spec.whatwg.org/#reflecting-content-attributes-in-idl-attributes).

> Creating an element that needs a property, and not an attribute, set is as easy as It's true, you can do that. But I might argue that you've made...

I guess I've been trying to encourage folks to also build their custom elements so they comply with these best practices: https://developers.google.com/web/fundamentals/web-components/best-practices and I'd like to the site to help...

Following up on this. I noticed just now that Dojo will always set string data as an attribute, even if my element only has a property defined. So I agree...

I would love to add Glimmer. Would you have any interest in working on a PR to help land it?

@knownasilya if you're interested in taking it on I can help talk you through doing a PR.

Hm that's an interesting idea. It also brings into question what sorts of behaviors do those libraries imbue into their elements. For example, do they create corresponding properties and attributes?...

I have a bot that keeps most dependencies up to date. But aside from that I havent had time to write new tests or update tests for frameworks that have...

oh interesting! Sorry for not catching this in the original set of tests, but this is also one of the reasons I wanted to create the site—to help identify really...

I started to write tests for that here: https://github.com/webcomponents/custom-elements-everywhere/blob/master/libraries/react/src/component-tests.js#L134 We could totally check this to see what they do if the property is undefined on the element.