Now I understand. The problem is not the ajax trap. The problem is that browsers do not execute JS code in ajax loaded context. This is not a web2py issue but I can see the problem. Let me give this some thought.
On Apr 6, 3:39 pm, Kuba Kucharski <kuba.kuchar...@gmail.com> wrote: > Massimo, > > Isn't this the same issue? > > http://groups.google.com/group/web2py/browse_thread/thread/a907fdafd4... -- You received this message because you are subscribed to the Google Groups "web2py-users" group. To post to this group, send email to web...@googlegroups.com. To unsubscribe from this group, send email to web2py+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/web2py?hl=en.
