Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[scoped-custom-element-registry] Add benchmarks #422

Open
kevinpschaaf opened this issue Jan 26, 2021 · 1 comment
Open

[scoped-custom-element-registry] Add benchmarks #422

kevinpschaaf opened this issue Jan 26, 2021 · 1 comment

Comments

@kevinpschaaf
Copy link
Collaborator

Task: The scoped-custom-element-registry, while building upon native Custom Elements where possible, adds some indirection, which is expected to add some measurable cost to element upgrade. It would be good to have a benchmark that quantifies this cost vs. native CE, so users can be aware of the additional cost of scoping.

@stale
Copy link

stale bot commented Feb 22, 2022

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the wontfix label Feb 22, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants