> BTW: was it documented that ajax_page supports not having a target ? I can > patch it for '' and undefined, but I'm not sure where you found that > reference. Anyway it's not a big deal, I'll send a PR (just dealing with > the error, as I can't reproduce the missing xmlhttprequest) >
I don't think ajax_page is documented at all (I think only ajax, component, and websocket are documented as part of the public API). We should think about which functions in web2py.js are intended to be part of the API vs. internal, as we don't want to get locked into supporting all the internal functions for the sake of backward compatibility. Also, at the bottom of the file, there is: web2py_websocket = $.web2py.websocket; but it looks like the function name is still "web2py_websocket" rather than just "websocket". Anthony -- Resources: - http://web2py.com - http://web2py.com/book (Documentation) - http://github.com/web2py/web2py (Source code) - https://code.google.com/p/web2py/issues/list (Report Issues) --- 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 [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
