On Wednesday, August 28, 2013 10:20:53 PM UTC+2, simon wrote: > > I have some very simple jquery scripts for creating dialog boxes. This was > all working fine until the replacement of web2py.js in release 5113. > However now it no longer works. >
What commit identifies "release 5113" ? > > The pre-5113 version had a web2py_ajax_page complete function that first > filled my dialog box and then executed response.js in that order. > > The new version does these two things asynchronously. Response.js is > executed within event_handler and generally this happens before the > ajax_page complete function. > I'm a little bit baffled..... trunk (and up until lots of time ago) executes the "response.js" command hooking up on the global ajaxSuccess event. Can you switch your web2py.js with the one in trunk and try ? if it has the same problem, would you move line 268 to after line 274 and see if it fixes the problem? > Is there some reason why this was changed or could it be changed back so > things happen in the same sequence? This does break backward compatibility. > > No, it doesn't. If you had a fully working app before, you have it also right now. If you want to leverage new features with - I assume - the newest web2py.js, then theoretically you should adapt accordingly your code. -- --- You received this message because you are subscribed to the Google Groups "web2py-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to web2py+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
