Mike - Actually, last night I realized that more plugins end up using it then I previously realized, so I added it back in, but it's just an empty function (does nothing).
--John On 8/24/07, Mike Alsup <[EMAIL PROTECTED]> wrote: > > Brandon is correct. There was a recent change to the form plugin to > avoid calling evalScripts (which no longer exists in jQuery 1.1.4). > > Thanks. > > Mike > > > On 8/24/07, Brandon Aaron <[EMAIL PROTECTED]> wrote: > > Did you get the latest version of the form plugin? I believe there was an > > update to make it work with 1.1.4. > > > > -- > > Brandon Aaron > > > > On 8/24/07, Matt Kruse <[EMAIL PROTECTED]> wrote: > > > > > > I haven't dug into the details yet, but I swapped the updated 1.1.4 > > > into my development app and it broke a screen. > > > > > > It looks like it has to do with eval'ing of scripts in a XHR response. > > > I'm using the form plugin to post a form and get the results back into > > > a DIV, and the blockUI plugin to block the page while it's processing. > > > Nothing fancy. I don't have any scripts being returned in the > > > response, so it shouldn't need to eval anything, but that's what the > > > error console looks like it's saying to me. > > > > > > Works fine with 1.1.3, breaks with 1.1.4 (no other changes). I will > > > look into it further when I get a chance, but I thought I would post a > > > message now in case anyone else is having a similar problem. > > > > > > Of course, it could be my own problem somewhere, but I'll try to rule > > > that out ;) > > > > > > Matt Kruse > > > > > > > > > > >
