Daniel

This feature will also enable running e2e tests on Firefox: https://pptr.dev/faq#q-what-is-the-status-of-cross-browser-support @rwaskiewicz Your link to the discussion is broken.

Hi. Yes correct. (nice graphic). Related to "breaking change": This is already breaking at our consumers of our stencil lib: They are using a "sdx-select" element with disabled prop. Now...

> It seems as if Stencil is setting disabled on the component regardless of its value, but as the whatwg document says, an element should be disabled (functionally) if: Stencil...

So I can not run the test in my reproducer repo without adding classes or something like that? What if I dont just have this simple component in component setup?...

Thanks for the workaround! But would be cool to have an E2EElement to do something like `expect(await label.isVisible()).toBe(true)`. A last idea regarding "looking in all shadow doms" logic: A webcomponent...

Sure: We have the sdx-teaser component. It has sdx-tag as a child in its shadow. Everything which has to do with sdx-tag is tested in tag.e2e. This component should be...

3 years later :-D

@Logesh08 This will not fix media queries used in css like `@media (hover: hover)`, just if your own script uses `window.matchMedia`, right?

My question just refers to the `input` event: A angular consumer normally uses [(ngModel)] to bind values to a form element like . So i added `@Event() input` to my...

I can confirm what @PMudra wrote: We have not checked in "components.d.ts". 1. running `stencil test --e2e` --> no TypeScript errors although we have unused imports --> components.d.ts is created...