Skip to content

Conversation

@theengineear
Copy link
Collaborator

@theengineear theengineear commented Apr 12, 2022

In the future, we may choose to add this test suite to the
custom-elements-everywhere repo. However, we should make sure that our
current test suite covers this need so that we don’t somehow drift as
we make changes.

Closes #106


Here's a visual on the test suite for reference (grabbed from the custom elements everywhere page).

Screen Shot 2022-04-11 at 4 31 27 PM

In the future, we may choose to add this test suite to the
custom-elements-everywhere repo. However, we should make sure that our
current test suite covers this need so that we don’t somehow drift as
we make changes.

Closes #106
@theengineear
Copy link
Collaborator Author

@klebba — Is this more-or-less what you were thinking as a first step here?

@klebba
Copy link
Contributor

klebba commented Apr 12, 2022

Wow, neato — yes I think this looks like the best approach here — I would guess that we score 100% right?

@theengineear
Copy link
Collaborator Author

I would guess that we score 100% right?

Yah, for sure.

@theengineear theengineear deleted the branch master September 2, 2022 21:19
@theengineear
Copy link
Collaborator Author

Moved to #118.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Ensure x-element compatibility with Custom Elements Everywhere test suite

3 participants