Repository navigation
Crash when Polymer/Platform loaded twice #478
Description
Activity
If we made that work, then every time you loaded a component, the browser would reload
platform.jsand reparse it. This would be bad for performance, and you should not try to do that.Note the above is specifically about
platform.js. You can replicate thepolymer.htmlimport infinity times with no cost. This is built in to the component system, e.g.:Just curious: doesn't the browser reload and reparse
platform.jsregardless of how many times it's included? Isn't the onus on the developer to not includeplatform.jsmore than is necessary?Note that I'm not saying it's great practice, but it looks as though it actively crashes things when I try. Am I wrong?
No, you are not wrong. I'm saying there is a disincentive to fix it, because it would allow people to do things which are bad for everybody.
Good enough :). Thanks!
If Polymer gets loaded more than once via
Polymer & Platform will crash. Is there any sane way to recover?
e.g. http://jsbin.com/yisadate/1/edit
Why?!
It would be cool to have documents that contain polymer definitions and markup to display what they are. e.g. Visiting
component.htmlwould display information about the component (and even render it!), but using it in alinktag will only pay attention to the<polymer-element>.