[Custom Elements] Add a lazyDefine feature to explore a future spec proposal.
#116
Assignees
Labels
Comments
sorvell
referenced
this issue
in webcomponents/custom-elements
May 31, 2019
Fixes #200 by adding customElements.polyfillDefineLazy(name, constructorGenerator) and adds a preferPerformance option. The customElements.polyfillDefineLazy is an approximation of a potential spec feature to allow definitions to be processed lazily when the first element to customize is found. The constructorGenerator is a function that's invoked only the first time and element to customize is found. It can return an element constructor function or a promise that resolves to an element constructor function.
dfreedm
changed the title
lazyDefine feature to explore a future spec proposal.lazyDefine feature to explore a future spec proposal.
|
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. |
|
This issue has been automatically closed after being marked stale. If you're still facing this problem with the above solution, please comment and we'll reopen! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add a feature that allows defining custom elements via a function that is only run when the first element is found to be customized. This potentially allows the code needed to upgrade the element to be fetched on demand.
Something like
customElements.polyfillDefineLazy(name, classGenerator)whereclassGeneratoris a function that returns a promise that resolves to a custom elements constructor function.The text was updated successfully, but these errors were encountered: