Skip to content

Loading…

`dom-module` forces `CustomElements.upgradeAll` each time an element without a dom-module is registered #2708

Closed
kevinpschaaf opened this Issue · 0 comments

2 participants

@kevinpschaaf
Owner

Code in dom-module added to ensure non-upgraded dom-modules can be found by registering elements has an undesired side-effect of doing potentially expensive tree walks for each element registered that intentionally has no dom-module. Issue is to consider avoiding these expensive tree-walks somehow.

@kevinpschaaf kevinpschaaf added the p1 label
@sorvell sorvell was assigned by kevinpschaaf
@sorvell sorvell referenced this issue from a commit
@sorvell sorvell Explicitly making an element's `_template` falsy is now considered an…
… allowable setting. This means the element stamps no content, doesn't collect any styles, and avoids looking up a dom-module. This helps address #2708 and the 5 elements Polymer registers that have no template have been set with `_template: null`.
b905a37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.