Last modified: 2014-10-01 12:44:57 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T50687, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 48687 - #jump-to-nav links make absolutely positioned elements jump
#jump-to-nav links make absolutely positioned elements jump
Status: NEW
Product: MediaWiki
Classification: Unclassified
Interface (Other open bugs)
1.22.0
All All
: Normal normal (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2013-05-21 17:17 UTC by entlinkt
Modified: 2014-10-01 12:44 UTC (History)
1 user (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments

Description entlinkt 2013-05-21 17:17:32 UTC
The #jump-to-nav links are currently hidden using "height: 0; overflow: hidden;", and that's causing trouble with absolutely positioned elements, like coordinates (especially in the Vector skin). This makes the coordinates position change in Firefox, depending on whether these links are present in the HTML or not (they are always present in the source for anonymous users, but not for logged-in users).

To reproduce, visit [[de:Berlin]] in Firefox 23, logged out (-> coordinates appear above header line) and logged in with #jump-to-nav links disabled (-> coordinates appear below header line). This is rather new; the coordinates are meant to be below the header line at all times (and it used to be like that).

I'd suggest to hide them with "position: absolute; top: -9999px;" like it is done in vector/screen.css for #mw-navigation h2. That should achieve consistent behavior across browsers.
Comment 1 Andre Klapper 2013-05-24 13:53:41 UTC
Thanks for the report and the detailed analysis!

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links