4

Certain elements, like iron-list, require template elements as children. However, Polymer 3 strips templates of its content.

How are these seemingly conflicting principles supposed to work together? See the jsbin examples @ https://www.webcomponents.org/element/@polymer/iron-list (they don't work due to the empty nested template).

The preserve-content leads to missing binding capability, so that's no viable solution. What's the reason for this template-stripping anyways? (Docs just say "better performance".)

Nicholas Brandt
  • 302
  • 2
  • 8

1 Answers1

1

The given examples have been updated and work now.

It seems like the combination of v3 elements and v2 polymer-core caused the failure.

Also my personal guess is that template-based elements are manually Templatizer-ing their child templates to stamp the content of the template even though the template's actual content is undefined. Templatizer seems to access the cache content that is noted in the docs.

Nicholas Brandt
  • 302
  • 2
  • 8