I would be careful about this change, and at the very least document it somewhere - a few people pack jQuery themselves in custom build scripts, and since the intro/outro files never did something significant before, they might have been ignored. On the other hand of course, we never officially supported such a use of the library :)
On Mon, Aug 10, 2009 at 11:23 PM, John Resig <jere...@gmail.com> wrote: > I agree that this is an exceedingly rare situation in which this occurs > (e.g. it only seems to occur with a 2 year old version of Prototype - the > problem has been fixed in Prorotype 1.6+). > > Although, the change seems pretty painless, so I've just landed it: > http://dev.jquery.com/changeset/6529 > > --John > > > > On Sat, Aug 8, 2009 at 5:27 PM, Aaron Pfeifer <aaron.pfei...@gmail.com>wrote: > >> >> Hey all, >> >> I was wondering if anyone had any feedback, comments, or concerns >> about the fix proposed in Bug 4834 http://dev.jquery.com/ticket/4834). >> This bug describes a situation where jQuery introduces global >> variables resulting in possible conflicts with other javascript >> libraries on the page. The proposed solution is to defer the >> assignment of global variables until the end of the jQuery library >> definition. >> >> Thanks! >> >> >> > > > > -- Paul Bakaus UI Architect @ smart.fm -- http://paulbakaus.com http://www.linkedin.com/in/paulbakaus --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "jQuery Development" group. To post to this group, send email to jquery-dev@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 -~----------~----~----~----~------~----~------~--~---
