- From: John Gamble <notifications@github.com>
- Date: Sun, 25 Sep 2022 20:37:00 -0700
- To: WICG/webcomponents <webcomponents@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Monday, 26 September 2022 03:37:14 UTC
There have been a couple of previous tickets created about this but they have been closed: https://github.com/webcomponents/webcomponents.org/issues/1294 https://github.com/WICG/webcomponents/issues/754 This is another use case which has not been brought up before, but an important one. **During unit tests, if we are unable to clean up and reset the browser state, then you break all future unit tests.** Please see my Stack Overflow post for a detailed explanation of the problem: https://stackoverflow.com/questions/73849002/unit-tests-of-angular-elements-registered-with-the-customelementregistry-as-a-h Custom elements are a very powerful feature, but not being able to write tests for using them really undermines their adoption. -- Reply to this email directly or view it on GitHub: https://github.com/WICG/webcomponents/issues/970 You are receiving this because you are subscribed to this thread. Message ID: <WICG/webcomponents/issues/970@github.com>
Received on Monday, 26 September 2022 03:37:14 UTC