Last modified: 2012-04-26 23:46:46 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 T38247, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 36247 - jump-to-nav display none strangeness
jump-to-nav display none strangeness
Status: NEW
Product: MediaWiki
Classification: Unclassified
General/Unknown (Other open bugs)
unspecified
All All
: Normal normal (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2012-04-25 17:42 UTC by MZMcBride
Modified: 2012-04-26 23:46 UTC (History)
3 users (show)

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


Attachments

Description MZMcBride 2012-04-25 17:42:45 UTC
Copying from <https://meta.wikimedia.org/w/index.php?oldid=3681360#Issues_clicking_the_.22discussion.22_link>:

---
If I recall correctly, the hiding-method was changed in 1.18 or 1.19 because display: none; had side-effects defeating its very purpose! Screenreaders are given a link that jumps to #jump-to-nav. However browsers can't scroll to a section that has no place in the rendering, it has to have a place in the document structure and also in the visual rendering (so that the browser can calculate to which pixel it should scroll). The element can be transparant and only 1x1px in size, but it must not be display: none;. This new hiding method was apparently only tested in Vector and works there, but it needs fixing in Monobook (or perhaps a different hiding method that doesn't cause this problem in Monobook). Either way, using display: none; (as you did now) is not an acceptable solution in the long term. It's okay for now since it is an understandable decision to prioritize the ability for most people to click the navigation links at all, then to allow the smaller part of the population to be able to skip to the navigation using screenreaders, but really both are important groups so this should be fixed soon and this local change reverted.
---

This bug may be a duplicate of bug 34893.
Comment 1 MZMcBride 2012-04-26 23:46:46 UTC
The English Wiktionary is currently having this problem because they haven't set display:none; on the #jump-to-nav element: <https://en.wiktionary.org/wiki/Wiktionary:Main_Page>.

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


Navigation
Links