Hi,
Thanks for the prompt reply.
It seems I've found a workaround:
{{=A('Working Modal', _href="#tst_modal", _class="btn btn-success", _onclick
="ajax('%s', '', 'ext_modal_data')" % URL("test_modal.load", vars={"var1":
"varX","var2":"varY"}), **{"_data-toggle":"modal"})}}
So adding an *onclick* attribute makes my button work as expected. Though
it's a shame, it can't be done using the in-house machinery..
Thanks
2015 m. gegužė 25 d., pirmadienis 23:23:34 UTC+1, Niphlod rašė:
>
> you can't mix and match ALWAYS web2py's facilities and bootstrap ones.
> Specifically, an A(..., callback=something) builds and intercepts any
> click link on it, as it's supposed to be.
> If you want bootstrap to work, use other (their?!) methods, not web2py's
> one expecting that they work without issues.
>
> BTW: loading via ajax is going to be deprecated, see
> http://getbootstrap.com/javascript/#modals-usage (the remote argument)
>
--
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/d/optout.
