custom-elements-everywhere icon indicating copy to clipboard operation
custom-elements-everywhere copied to clipboard

Custom Element + Framework Interoperability Tests.

Results 116 custom-elements-everywhere issues
Sort by recently updated
recently updated
newest added

I think it would be useful to test that libraries supporting custom elements include the ability to listen for events from either the capture or the bubble phase. We recently...

Additional Tests

I'm working on a project where we integrate web components into a web application using the preact framework. For the most part, the issues this site have raised have proven...

Additional Tests

Elm was removed in #1198 because of persistent flaky errors on CI due to corruption in the elm-stuff directory. This wasn't fixed by removing the elm-stuff directory before running tests,...

Smart HTML Elements for building Custom Elements: https://www.htmlelements.com/

With the number of frameworks and the height of each framework's section, the home page is quite long now. Also, the alphabetical sorting doesn't surface the frameworks that people are...

Type: Enhancement

Setting `value` as property on a custom element fails. It gets passed as a string [Object Object] instead. ```html ``` ```js new Vue({ el: '#app', data: { message: {'hello': 'world'}...

Additional Tests

There is a known issue with Angular and material-components-web: https://github.com/material-components/material-components-web/issues/4221 Angular template syntax uses colon as a special behavior and event with colon in the name do not work. This...

Additional Tests

I'm currently encountering a problem with svelte and I think it could be interesting to know if other framework has this caveat. The goal of the test is to see...

Additional Tests

It seems to me that libraries do not always appropriately handle camelCase property names the same way. When using Vue and Svelte together, for example, I'm finding the only way...

Additional Tests