GeoHack coordinates are misaligned again for me (possibly because of the recent change to where the language links are displayed). It looks like this is because the position is now set based on the top of the prose, so the coordinates usually end up floating above the infobox area. I also have the XTools gadget turned on, which adds additional vertical space between the h1 line and the start of the prose.
|mediawiki/skins/Timeless||master||+28 -26||Create wrapper for all junk below firstHeading, including nav stuff|
All right, seems to be related to the position:relative on #mw-content-text. That maybe shouldn't even be there (should probably be on a block around/under the firstheading)...
Two questions (for you guys, or just in general):
- What exactly is geohack, that's adding these coordinates in the first place? Is this an extension, template, what?
- Why was the position:relative put there, does it actually need to be there, or can we move it?
I have zero knowledge as to when or why position:relative became attached to it and am not aware of any constraint to moving it.
All right, ashley found the things:
- Templates documented: https://www.mediawiki.org/wiki/GeoHack
- Timeless rule (commented!): https://github.com/wikimedia/mediawiki-skins-Timeless/blob/master/resources/screen-common.less#L26
Which basically means that Timeless probably isn't going to change this again, and we just need to change the offset for Timeless specifically in the template skinstyles to reflect this, or stuff. Anyone know where that is?
Slight problem in that different browsers appear to have wildly different line-heights and I do not know how to account for that with css when the problem is that we are trying to insert content data into a non-content part of the page...
So the new offset really only works in chrome on windows; elsewhere it's too low and bonks into the cactions tabs. On the other hand, firefox on windows and linux and even chrome on linux all seem to be a little more consistent with each other, but doing it for them causes it to overlap the firstheading on the other...