This is fantastic. Thanks, Steve! > We’re also now providing a new event called ‘polymer-ready’. > > Use the ‘polymer-ready’ event to know when all the polymer elements that > have been loaded are upgraded and ready for use. Previously we recommended > using the ‘WebComponentsReady’ event for this purpose but we’re now > providing an explicit event because element upgrade timing has changed. >
So, our previous advice around 'WebComponentsReady' has been if you prematurely fetch an element from the DOM before it has a chance to upgrade you'll run into issues and you should instead wait for this event to fire before trying to interact with the element. Given your notes to Eric below, are we now saying that polymer-ready should* instead* be used to 100% guarantee Polymer elements and their dependencies are loaded? In which case.. - WebComponentsReady: only use if you're working with the polyfills and not Polymer - polymer-ready: opt for this if you are using Polymer, it's timing is more reliable. Is that right? > > Here’s some additional info... > > In enabling support for native imports, we’ve moved some features that are > not supported by native imports out of the polyfill and into Polymer. > Fixing url attributes and loading stylesheets in templates inside > polymer-element’s are now both the responsibility of Polymer. > > Because of the need to avoid FOUC, it’s important that element stylesheets > are loaded prior to rendering. To keep things simple, we’re delaying > element registration until these resources are ready. This means that > polymer needs a new signal to indicate that elements are ready; thus, > ‘polymer-ready’. > > There’s still more work to do. The HTMLImports polyfill does not yet > support imperatively constructed imports. We’re working on addressing that > right now. Once we have this, we plan to demonstrate how bundles of > elements can be easily loaded and used asynchronously, on demand. > > Please let us know if you have > feedback<https://groups.google.com/forum/#!forum/polymer-dev>or discover > issues <https://github.com/polymer/polymer/issues>. > > Follow Polymer on Google+: plus.google.com/107187849809354688692 --- You received this message because you are subscribed to the Google Groups "Polymer" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/polymer-dev/086c4eeb-d3d8-472a-b265-7f0790b5a585%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
