can we fix this somehow so the WP-Admin-Toolbar is not overriding the rest of the site…i saw some generaly cwicyl-styles who are leading to this behaviour…we might override them with CSS for admin only…but is there a more general way to avoid this?
Also this bevahiour also causing one more element to be renedered falsly…here you can see in comparison: its not only the overriding of the main body it is also causing the slider element to have a wrong margin-top…
Why do you want to remove it?
What you want to achieve is to display your page property beneath the admin bar.
Everything is done by this rule, except your header, because fixed elements are always positioned relative to the viewport, not to any element.
I just checked things on my side. Nothing has been changed. Neither by WP, nor by Cwicly.
There are no issues I can find on my side; everything works as expected when going the recommended route.
This is the only tweak you want to apply.
ok i see so our “fixed” header-area is the problem so we must re-think our concept…i thought this “fixed” header came from the cwicly-navigation-element? so we are multipled developers so someone set this up apart from your “route” right?
OK so I remember now why I didn’t need the fix any more… It has not been corrected by WP or Cwicly, but I found out that for a fixed positioned element, default top position is NOT 0 from VIEWPORT top, but zero from CONTAINER top.
So if you don’t set top: 0, you don’t need the fix, because the fixed header will be positioned at 0 pixel from the header container, which probably is the .wp-site-blocks div, which is contained in html element, which has a 32px top margin, hence not covering admin bar.
So you’re issue is that you probably set top: 0 on your fixed header, which you shouldn’t.
(NOTE: If you need to offset the fixed header, don’t use top but margin-top, so that you still work inside the container viewport.)
This is correct @yankiara. If you don’t set a direction, like top, a fixed element behaves like an absolute positioned element.
Cwicly, depending on your general approach, places blocks outside of the .wp-site-blocks element, so one must keep that in mind when building the site.
Especially with global elements like the header, one needs to be aware of that.
ok cool i see thanx! for now we dont fix it at all…we must sort some things out now…later we want a normal sticky-automatism. for what i see now Cwicly is really more for developers intended and not for “end users” without real indepth developing knowledge despite their marketing