Looks like this change<https://code.google.com/p/web2py/source/browse/applications/admin/static/js/web2py.js?r=b995ca36cd33a28339d54f15bcf8eebb6d58f2e6>was actually made in January in response to this issue <https://code.google.com/p/web2py/issues/detail?id=1254>. Technically, I suppose it does break backward compatibility because previously web2py-component-command (i.e., the content of response.js) was executed synchronously after the component content loaded, and now it is run asynchronously. Actually, this was probably not a good move, because you might need the JS to run after the component content has loaded, so we might want to revert this change. The web2py-component-command and web2py-component-flash headers were intended for use specifically with components. If we want to enable such functionality more generally, perhaps we should use alternative headers for that purpose. Please open an issue about this and link back to this thread.
Anthony On Wednesday, August 28, 2013 1:20:53 PM UTC-7, 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. > > 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. > > 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. > > > -- --- 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.
