Last modified: 2014-07-09 22:23:34 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 T28032, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 26032 - Give "back to top" button
Give "back to top" button
Status: NEW
Product: MediaWiki
Classification: Unclassified
Interface (Other open bugs)
unspecified
All All
: Low enhancement (vote)
: ---
Assigned To: Nobody - You can work on this!
: design
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2010-11-20 23:50 UTC by ivan
Modified: 2014-07-09 22:23 UTC (History)
12 users (show)

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


Attachments
Back to top button implemented using JQuery (3.23 KB, patch)
2014-01-19 07:15 UTC, kunalgrover05
Details

Description ivan 2010-11-20 23:50:44 UTC
Is it possible to add a "back to top button". 

The content is generalized in the beginning of every article through points (1,2,3, etc) and subpoints (1.1,1.2,1.3, etc) and it's great. But in very long articles would be nice to have this button after the end of every point or subpoint for better and faster navigation on the page and between seperate points.
Comment 1 Krinkle 2010-11-21 00:15:00 UTC
For if/when this is implemented, a possible way to aavoid the ugly repeating 'back to top' links all over the place, a solution would be  having it 'float' in a fixed position on the bottom left. As part of the sidebar but staying fixed when scrolling down. Avoids having it duplicate and adds that it is always in the same place.
Comment 2 Mark A. Hershberger 2011-02-12 04:09:07 UTC
I like Krinkle's floater idea!  Giving this to Trevor since it is UI and he doesn't have enough of these yet.
Comment 3 Andre Klapper 2013-01-09 13:27:23 UTC
Trevor:
This report has been in ASSIGNED status for more than one year and you are set as its assignee. In case that you are not actively working on a fix, please reset the bug status to NEW/UNCONFIRMED.
In case you do not plan to work on a fix in the near future: Please also edit the "Assigned To" field by clicking "Reset Assignee to default", in order to not prevent potential contributors from working on a fix. Thanks for your help!
[assigned>=1y]
Comment 4 Gerrit Notification Bot 2014-01-19 06:16:16 UTC
Change 108306 had a related patch set uploaded by Jforrester:
Go to top button for pages. Implements go to top button with smooth scrolling. Hidden when on top of page and appears when scrolled down to some extent. Configurable-Enabled by default. Can be disabled by using "$wgShowTopButton = false;" in LocalSettings

https://gerrit.wikimedia.org/r/108306
Comment 5 kunalgrover05 2014-01-19 06:35:55 UTC
Hi I submitted this patch through online gerrit uploader. Can someone review the patch?
https://gerrit.wikimedia.org/r/108306

Also I am new here so please tell if there is a better way to write the patch or if something else is wrong in the commit.
Comment 6 kunalgrover05 2014-01-19 07:15:39 UTC
Created attachment 14339 [details]
Back to top button implemented using JQuery

My patch had a few errors as indicated by the notification bot.
I fixed them but I couldn't make a change as I hadn't submitted the patch through git-review.
I am uploading the new patch here. Please someone review it.
Comment 7 p858snake 2014-01-19 10:15:07 UTC
(In reply to comment #6)
> Created attachment 14339 [details]
> Back to top button implemented using JQuery
> 
> My patch had a few errors as indicated by the notification bot.
> I fixed them but I couldn't make a change as I hadn't submitted the patch
> through git-review.
> I am uploading the new patch here. Please someone review it.

Can you please submit it as a new patch via the uploader? (We can mark the old one as abandoned)
Comment 8 kunalgrover05 2014-01-19 12:45:06 UTC
Added here:
https://gerrit.wikimedia.org/r/#/c/108323/
Comment 9 Gerrit Notification Bot 2014-01-20 20:29:11 UTC
Change 108306 abandoned by Jforrester:
Go to top button for pages

Reason:
Newer version in I866cd88201948177da2fec3cc9d4c713bb39bc0f.

https://gerrit.wikimedia.org/r/108306
Comment 10 Gerrit Notification Bot 2014-01-20 20:29:47 UTC
Change 108323 had a related patch set uploaded by Jforrester:
Go to top button for pages

https://gerrit.wikimedia.org/r/108323
Comment 11 Brandon Harris 2014-02-11 03:00:21 UTC
This bug should likely be closed WONTFIX, at least in regards to Foundation wikis.  I have left comments on the gerrit change to this effect.

If this is a feature desired by 3rd Party wikis, it should be bundled into an extension rather than into core.
Comment 12 MZMcBride 2014-02-11 03:37:27 UTC
(In reply to comment #11)
> This bug should likely be closed WONTFIX, at least in regards to Foundation
> wikis.  I have left comments on the gerrit change to this effect.

Can you please elaborate on why you think this is a complete non-starter for MediaWiki core?

Imagine something like [[mw:Requests for comment/Clickable section anchors#Option 2]] but with an additional up arrow icon to return back to the top of the page. If implemented well, I think this would be a net benefit to readers and users. Since we're discussing a core functionality of any MediaWiki wiki (the ability to create headers), it would make sense to add such capability directly into core.

I'm interested to hear what others think.
Comment 13 Technical 13 2014-02-11 03:43:43 UTC
I don't think there should be a link for every section header as that would look cluttered and unprofessional.  I like the idea of back to top / back to TOC links, but I think it should be a single static link somewhere on the page (bottom corner?).
Comment 14 Gerrit Notification Bot 2014-07-09 22:16:54 UTC
Change 108323 abandoned by Krinkle:
Go to top button for pages

Reason:
Closing change as the implementation has various issues, patch author has not responded in several months, and there is some discussion on the bug report about whether this feature should be in core after all usability/design wise.

https://gerrit.wikimedia.org/r/108323

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


Navigation
Links