Perhaps breaks was a little strong, I should say it conflict with
Bootstrap's .hidden class and causes problems with javascript being used to
show and hide sections.
Thanks,
Stuart
On Wednesday, September 16, 2015 at 10:02:23 AM UTC-7, Anthony wrote:
>
> What Bootstrap functionality is broken
That got it , Thanks.
On Wednesday, September 16, 2015 at 10:02:23 AM UTC-7, Anthony wrote:
>
> What Bootstrap functionality is broken by this?
>
> On Wednesday, September 16, 2015 at 9:42:55 AM UTC-4, Stuart Rolinson
> wrote:
>>
>> When I create an item directly in the html form with a class
That got it , Thanks.
On Wednesday, September 16, 2015 at 6:42:55 AM UTC-7, Stuart Rolinson wrote:
>
> When I create an item directly in the html form with a class ='hidden' for
> use with bootstrap, web2py appears to be rendering an additional element
> style "display:none" which stops
That got it, thank you.
On Wednesday, September 16, 2015 at 8:25:18 AM UTC-7, Leonel Câmara wrote:
>
> web2py.js does that, I think it's because of appadmin using class hidden
> and since appadmin uses your app's layout it may not have the css saying
> it's supposed to be display:none, but to
web2py.js does that, I think it's because of appadmin using class hidden
and since appadmin uses your app's layout it may not have the css saying
it's supposed to be display:none, but to be frank I'm not sure. You can
just delete the line that does it that looks like this because bootstrap
What Bootstrap functionality is broken by this?
On Wednesday, September 16, 2015 at 9:42:55 AM UTC-4, Stuart Rolinson wrote:
>
> When I create an item directly in the html form with a class ='hidden' for
> use with bootstrap, web2py appears to be rendering an additional element
> style
6 matches
Mail list logo
