You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When two types extend the same super type they should no affect each other. However, in the following example i-break-inheritance appears to wipe out the prototype of su-per from should-work.
<polymer-elementname="su-per"><script>Polymer({foo: function(){console.log('foo');}});</script></polymer-element><polymer-elementname="should-work" extends="su-per"><script>Polymer({bar: function(){console.log('bar');}});</script></polymer-element><polymer-elementname="i-break-inheritance" extends="su-per" noscript></polymer-element><polymer-elementname="some-app"><template><su-perid="su_per"></su-per><should-workid="should_work"></should-work></template><script>Polymer({ready: function(){// This works.this.$.su_per.foo();// This is broken. foo is undefined.this.$.should_work.foo();}});</script></polymer-element>
The text was updated successfully, but these errors were encountered:
Ok, this is interesting. The cause was not what I was expecting. I just replaced my index file with your example and I was still getting the weird behaviour. I then realised that I was running it after it went through the vulcanize process which is part of my build. However, it worked well if I didn't vulcanize it.
Anyway, I had a 0.3.1 version of vulcanize. I updated it to the latest version and it works now. I'm gonna close the issue, sorry about that.
When two types extend the same super type they should no affect each other. However, in the following example
i-break-inheritance
appears to wipe out the prototype ofsu-per
fromshould-work
.The text was updated successfully, but these errors were encountered: