> > - 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?
Exactly right. On Fri, Jan 24, 2014 at 7:13 AM, Sam Carecho <[email protected]> wrote: > Great question. > This was something I was in doubt about. > > > > On Fri, Jan 24, 2014 at 1:52 AM, Eric Bidelman <[email protected]> wrote: > >> Awesome work. This is huge! I do have a couple of questions: >> >> What (if anything) should the WebComponentsReady signal be used for now? >> >> The polymer-ready event is only relevant when using imports, correct? >> >> Has there been any further discussion on prollyfilling an async attribute >> on link[rel=import]? Or, will dynamically created imports be enough? >> On Jan 23, 2014 2:48 PM, "Steve Orvell" <[email protected]> wrote: >> >>> In today's release... Polymer now supports native >>> HTMLImports<http://w3c.github.io/webcomponents/spec/imports/> >>> ! >>> >>> If you turn on the ‘Enable HTML Imports’ flag in Chrome Canary, Polymer >>> should seamlessly work and take advantage of native imports. >>> >>> 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. >>> >>> 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/CA%2BrMWZg%3DTeFUBx61%2B74YoDDMCoVza76v1Z%2B1n2Nydwj-99DnoQ%40mail.gmail.com >>> . >>> For more options, visit https://groups.google.com/groups/opt_out. >>> >> 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/CACGqRCAB2wkzJ_HnqZnczE4AEwSv7Q6JXnfGJefu4fQMmYZ9OQ%40mail.gmail.com >> . >> >> For more options, visit https://groups.google.com/groups/opt_out. >> > > 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/CA%2BrMWZik_VdknsxFiFfe46T5n92f%3Ds-noiCMNQfogQx9J7yTgw%40mail.gmail.com. For more options, visit https://groups.google.com/groups/opt_out.
