It's that single line within jQuery 1.4 (and 1.4.1) - tries to access the insides of a protected object, so put in a single "unsafeWindow." before the thing and include your custom version - works well enough for me to @require elsewhere. Just a pity that jQueryUI doesn't really work properly at all - most of the widgets are broken to some extent within GM :-/
On Jan 23, 11:47 pm, LeroySolay <[email protected]> wrote: > Yes, it is @require > > I just flipped back to jQuery 1.3.2 and it's happy again. Must be > compatibility between jQuery 1.4 and GreaseMonkey 0.8.20091209.4 ... > > On Jan 23, 6:42 pm, esquifit <[email protected]> wrote: > > > On Sun, Jan 17, 2010 at 2:54 PM, Henry 'Pi' > > James<[email protected]> wrote: > > > It appears the newly released jQuery 1.4 cannot be loaded via @include > > > 1) You mean @require? > > 2) Have you been able to include (require) previous versions of jQuery > > in Greasemonkey? -- You received this message because you are subscribed to the Google Groups "greasemonkey-users" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/greasemonkey-users?hl=en.
