Arthur Evans

That definitely seems like a bug. Stranger still, if you call `linkPaths` with the arguments reversed, you get different behavior (still wrong, but different).

@trevordixon that is what I meant. It looks to me from the code in `computeLinkedPaths` that the linkage should work either way: https://github.com/Polymer/polymer/blob/master/lib/mixins/property-effects.js#L453 ... but that doesn't seem to be...

@trevordixon you're right, I totally missed that. @kevinpschaaf this detail of linkPaths isn't documented anywhere that I can see--certainly not in the API docs, which list target path and source...

I think you're exactly right, it's a scope problem. The keyframes are defined inside the shadow DOM, and the slotted content is outside of it. To verify this, you can...

Running the original JSBin against 1.7.1, I'm not seeing the original error message, but I am seeing this new console error appear occasionally instead: ``` "Error: The ref_node to be...

The problem here is that IE's parser doesn't think `` belongs in a ``, so it helpfully removes it for you. `` and `` are among the "parser-challenged elements" referred...

Hi @divyanshu-rawat. The `type` key on a Polymer property is sometimes confusing because it serves a very different purpose than a TypeScript type. The property type is used _only_ when...

@andriyaucar what errors are you seeing? And is there an application URL you can share, or is this an internal app?

Hi @andriyaucar ... Hope you have resolved this. If not, there are a few suggestions here: https://github.com/Polymer/polymer/issues/5633#issuecomment-598918251

Hi, thanks for the report. Does that script tag occur before any of the Polymer elements are loaded? Are you seeing any errors in the console?