chore: remove Polymer 1 DOM API and HTML import loading - #25145
Merged
Conversation
DomApi switched from the normal DOM API to a Polymer specific one when a global Polymer object reporting version 1.x was present. Polymer 1 was distributed as an HTML import (polymer-micro.html) and HTML imports can no longer be loaded: Dependency.Type only knows STYLESHEET, JAVASCRIPT, JS_MODULE and DYNAMIC_IMPORT, and Polymer 3 never defines a global Polymer object. The Polymer implementation was therefore never taken into use and DomApi.wrap always returned the node as is. As nothing requests HTML imports anymore, ResourceLoader.loadHtml and inlineHtml, the HTMLImports.whenReady plumbing they rely on and the rel="import" branch of the already loaded resource scan are removed as well.
Contributor
|
mshabarov
approved these changes
Aug 11, 2026
This was referenced Aug 13, 2026
Artur-
added a commit
that referenced
this pull request
Aug 14, 2026
Artur-
added a commit
that referenced
this pull request
Aug 14, 2026
Artur-
added a commit
that referenced
this pull request
Aug 14, 2026
Artur-
added a commit
that referenced
this pull request
Aug 17, 2026
Artur-
added a commit
that referenced
this pull request
Aug 17, 2026
Artur-
added a commit
that referenced
this pull request
Aug 17, 2026
platosha
pushed a commit
that referenced
this pull request
Aug 18, 2026
platosha
pushed a commit
that referenced
this pull request
Aug 18, 2026
platosha
pushed a commit
that referenced
this pull request
Aug 18, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
DomApi switched from the normal DOM API to a Polymer specific one when a global Polymer object reporting version 1.x was present. Polymer 1 was distributed as an HTML import (polymer-micro.html) and HTML imports can no longer be loaded: Dependency.Type only knows STYLESHEET, JAVASCRIPT, JS_MODULE and DYNAMIC_IMPORT, and Polymer 3 never defines a global Polymer object. The Polymer implementation was therefore never taken into use and DomApi.wrap always returned the node as is.
As nothing requests HTML imports anymore, ResourceLoader.loadHtml and inlineHtml, the HTMLImports.whenReady plumbing they rely on and the rel="import" branch of the already loaded resource scan are removed as well.