> > 1. In the jQuery specific case, if the library will adopt the script, > the library will make lazy plug-ins load based on $(document).ready(...) > possible. We need to understand that jQuery as is, is not that kind of lazy > loaded library since I assume that if a website uses jQuery, everything > will > depend on it. Accordingly, this trick inside jQuery will make everything > else lazy loadable except jQuery itself ... now please find a real case > scenario where jQuery is lazy loaded ... if any, that has never trusted the > ready event since it cannot work in any case with the current > DOMContentLoaded based implementation > > The last use case you mention doesn't make any sense. If jQuery is already on the page before DOM ready then the ready event has already fired and dynamically-loaded plugins (that use the ready event) will still work just fine.
The use case that needs to be supported is the dynamic loading of jQuery + jQuery scripts into any given webpage at any time - regardless of if they already use jQuery. Unfortunately still looking for a Firefox solution there. As mentioned before this is something that we've never supported (because it hasn't worked) but we want to support going forward. --John -- You received this message because you are subscribed to the Google Groups "jQuery Development" group. To post to this group, send email to jquery-...@googlegroups.com. To unsubscribe from this group, send email to jquery-dev+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/jquery-dev?hl=en.
