custom-elements-everywhere
custom-elements-everywhere copied to clipboard
webcomponents
Custom Element + Framework Interoperability Tests.
While listing which libraries work with custom elements is __extremely__ useful, I'd also like to know which frameworks can produce custom elements. Would this be a useful advanced test? Adding...
Check if frameworks are able to recognize the special meaning of the `is=""`-attribute, and that it cannot be handled like a traditional attribute when it comes to dynamic element creation.
I'm the maintainer of a large private custom element library at work and we we're very excited to see Svelte move to 100% passing tests recently. Several pilot projects had...
I love the utility that custom-elements-everywhere.com provides to web developers, but the biggest issue with the test data is that it only shows the current versions of each framework. Not...
Maybe there's some obvious reason why it isn't needed, but it isn't obvious to me due to my murky understanding -- would it make sense to also test preact with...
Right now primitive values are allowed to be set as either an attribute or a property. Since properties and attributes are two separate APIs, custom elements could require that a...
Should there be a test that covers upgrading elements? Just wondering if the custom element is defined after the framework/library renders the output how It appears that this currently does...
I've been successfully using [Aurelia](http://aurelia.io/) with custom elements for some time now. I would like to attempt a PR for adding Aurelia. Would that be something that is wanted?
Glimmer.js, a component-based library that powers components in Ember.js, is able to [output web components](https://glimmerjs.com/guides/using-glimmer-as-web-components).
As of version 10 of the library, the name of this library has been updated from DIO to Dyo: https://github.com/dyo/dyo/blob/master/CHANGELOG.md#1000-unreleased
Metadata
Owner
Metadata
Custom Element + Framework Interoperability Tests.