Page MenuHomePhabricator

Proposal: integrate "skip to top and bottom" functionality into the standard UI
Closed, DeclinedPublic


The standard Wikimedia interface doesn't have (always visible) buttons that provide a jump to top or bottom functionality, like the template {{skip to top and bottom}} on en.wikipedia provides. This template adds quite clunky buttons though, covering the text in the right bottom corner of the page, which doesn't make it an attractive sollution. Last year I created a more subtle version of it on nl.wikipedia (currently in my userspace), which integrates two arrows (triangles) nicely into the margin line left of the page for different skins (in case of Vector: only the legacy one; I don't know what's the status with the 'new' Vector). See the template and the accompanying templatestyles. And see this archived talk page for a demonstration, a comparison with the en.wikipedia version, and the quite positive responses (in Dutch).

My proposal is to integrate the buttons (like in my template, or in a similar way) into the standard interface, so they're:

  • not only on the select few (by a template) but on all pages (talk pages, articles, special pages), meaning regular users of the Wikimedia projects can always use them to navigate;
  • not as intrusive as the en.wikipedia template, meaning they're never in the reader's face.

Some improvements to consider:

  • Use svg images instead of Unicode characters (and maybe better scaling on different devices?).
  • Prevent the arrows from falling below the when at the bottom of the page (dropping 'off' the margin line into the page's footer). -- using script?

I noticed T249579 also mentions the en.wikipedia template, as a solution to prevent a lot of scrolling on mobile view.

Event Timeline

Marc created this task.Sep 18 2020, 9:17 PM
Restricted Application added a subscriber: Aklapper. · View Herald TranscriptSep 18 2020, 9:17 PM

When would you have to jump to the bottom? What is the use case / underlying problem behind this request?

Aklapper closed this task as Declined.Oct 3 2020, 5:10 PM

Unfortunately closing this Phabricator task as no reply and no use cases have been provided (e.g. specific situations when and why this would be needed).

@Marc: After you have provided the information asked for and if this still happens, please set the status of this task back to "Open" via the Add Action...Change Status dropdown. Thanks!