You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
By adding !important to this class, there is no possibility to overwrite margin-top via userall.css or userstyle.css anymore.
The reason: it's implemented/rendered as in inline:css. All other css files (userall.css or userstyle.css) are imported before that.
Here's the problem: If you have chosen a custom bootstrap theme with a navbar at a different height (e.g. 100px) than all different themes from bootswatch.com, the default setting for the navbar remains 50px as it is defined in template.php. I cannot find a way of overwriting this setting and combination of these variables without editing template.php (which isn't save for updates at all, of course.)
And that is the result: Some content will be hidden behind the navbar, e.g. breadcrumbs, youarehere, social-buttons, print-button or even headlines.
It would be great, if there wouldn't be any classes that include !important, that are rendered by php inline, at all.
Otherwise …
One suggestion to manage "Fixed global margin-top" is to getInfo about .navbar's height without any presets, but by checking the actual height of .navbar while loading the site. This would actually be very helpful if it varies from big device to mobile device.
Another suggestion is to make an input-field in DokuWiki / Bootstrap3 Template / Configuration for a custom presets of .navbar in height. Well, but this might be very complicated.
By the way: I tried these solution, but none of the did the job:
There is the possibility to use padding-top as an addition to margin-top, but it's not a good choice, cause it's effecting scrolling to the anchors via TOC, so that there ain't no precise scrolling anymore.
I tried using this in userall.css body.custom .navbar-default {height:100px;}
but it only effects the navbar and actually does not effect the php-reading/writing for margin-top
Versions
Bootstrap3 Template 2020-08-28
Custom Design
DokuWiki Hogfather 2020-07-29
The text was updated successfully, but these errors were encountered:
nurzu
changed the title
inline:style !important is overwriting userstyle.css/userall.csss
inline:style !important is overwriting userstyle.css/userall.css
Nov 6, 2020
inline:style
!important
is overwriting userstyle.css/userall.csssReferring to the changed file: d1ac22c
By adding
!important
to this class, there is no possibility to overwrite margin-top via userall.css or userstyle.css anymore.The reason: it's implemented/rendered as in
inline:css
. All other css files (userall.css or userstyle.css) are imported before that.Here's the problem: If you have chosen a custom bootstrap theme with a navbar at a different height (e.g. 100px) than all different themes from bootswatch.com, the default setting for the navbar remains 50px as it is defined in template.php. I cannot find a way of overwriting this setting and combination of these variables without editing template.php (which isn't save for updates at all, of course.)
And that is the result: Some content will be hidden behind the navbar, e.g. breadcrumbs, youarehere, social-buttons, print-button or even headlines.
It would be great, if there wouldn't be any classes that include
!important
, that are rendered by phpinline
, at all.Otherwise …
One suggestion to manage "Fixed global margin-top" is to
getInfo
about.navbar
's height without any presets, but by checking the actual height of.navbar
while loading the site. This would actually be very helpful if it varies from big device to mobile device.Another suggestion is to make an input-field in DokuWiki / Bootstrap3 Template / Configuration for a custom presets of
.navbar
in height. Well, but this might be very complicated.By the way: I tried these solution, but none of the did the job:
body.custom .navbar-default {height:100px;}
but it only effects the navbar and actually does not effect the php-reading/writing for margin-top
Versions
The text was updated successfully, but these errors were encountered: