I will explain with 3 images…
If I select a link from contents, in this case “The road map history”, I would expect to have something like this in return:
But instead, I got this one, where part of the text is hidden:
To add to this, I’ve see the same as well. It appears that when jumping to a different location on the page (using anchors, sections headers, etc.) the position you are jumping to is moved to the top of the window, and then hidden behind the Waze blue top bar which is being drawn over the viewable window instead of separately above it.
1 Like
This BUG still exists. It is due to the height and positioning of the headboard. I mention it to keep it in mind.
Keywords for searches: anchor, heading, fixed position.
You are exactly correct. It is because in the new CSS skin the top bar is now floating rather than positioned at the top of the screen. I propose that there is no reason to have that bar always visible, unless there is something it provides in the mobile environment that I am not aware of. I am assuming that it is floating because someone didn’t modify the CSS skin to match the prior operation.
Having said that, I am pretty sure I can work up the CSS that would adjust the bar to float, but the top of screen would not scroll under it. But before I can do that, I need to see the CSS for the skin in use and the CSS for the original Wiki skin. I think those are only available to the back end admins.
The mobile bversion uses a different skin, and they are working on replacing it with a mobile responsive version. So I doubt any behaviour here is related to mobile operation.
OK. Then the easiest solution would be to get the Waze skin CSS to NOT float that box and just anchor it to the top of the page. This problem would then go away.
Likely the top nav box on every page is using a “position: fixed;” attribute when it should be “position: relative;” or “position: static;” depending upon where and how the bar is configured in the skin CSS file.
Having it not floating would be very nice. I’d not noticed it as an issue until somebody pointed it out, as I’m usually going to the main pages. It should be a relatively easy CSS fix.
I had not noticed this until today, but I think it would be good to get this fixed.
Yes, please, it’s a persistent annoyance that I’m surprised hasn’t already driven people batty 
UP
Still broken in 1.29 as of 2018-06-20.