miljenko1

Dear Yasin, thank you! I had a SpeedyCache plugin activated. After I deactivated it, the problem was gone. I guess, from now on, I’ll keep the SpeedyCache plugin deactivated at all time, perhaps activating it only when I feel compelled to purge the cache. I had it activated in the first place because on another site I’m running, the changes to pages/posts don’t appear unless you purge the cache with a dedicated plugin like that.

That’s fair enough! Thanks!

Solved!
It was in here, I coppied this from original theme css into child theme css:

#access {
background: #222; /* Show a solid color for older browsers */
background: -moz-linear-gradient(#252525, #0a0a0a);
background: -o-linear-gradient(#252525, #0a0a0a);
background: -webkit-gradient(linear, 0% 0%, 0% 100%, from(#252525), to(#0a0a0a)); /* older webkit syntax */
background: -webkit-linear-gradient(#252525, #0a0a0a);
-webkit-box-shadow: rgba(0, 0, 0, 0.4) 0px 1px 2px;
-moz-box-shadow: rgba(0, 0, 0, 0.4) 0px 1px 2px;
box-shadow: rgba(0, 0, 0, 0.4) 0px 1px 2px;
clear: both;
display: block;
float: left;
margin: 0 auto 6px;
width: 100%;
}

And then I changed

margin: 0 auto 6px;

into

margin: 0 auto 0px;

naturally.

so you suspect at #access and stuff like that related to <nav>? Me too…