Last modified: 2011-03-13 18:06:26 UTC

Wikimedia Bugzilla is closed!

Wikimedia has migrated from Bugzilla to Phabricator. Bug reports should be created and updated in Wikimedia Phabricator instead. Please create an account in Phabricator and add your Bugzilla email address to it.
Wikimedia Bugzilla is read-only. If you try to edit or create any bug report in Bugzilla you will be shown an intentional error message.
In order to access the Phabricator task corresponding to a Bugzilla report, just remove "static-" from its URL.
You could still run searches in Bugzilla or access your list of votes but bug reports will obviously not be up-to-date in Bugzilla.
Bug 10926 - Linear Browsing Feature
Linear Browsing Feature
Product: Wikimedia
Classification: Unclassified
General/Unknown (Other open bugs)
All All
: Lowest enhancement (vote)
: ---
Assigned To: Nobody - You can work on this!
Depends on:
  Show dependency treegraph
Reported: 2007-08-14 19:14 UTC by Hobbes
Modified: 2011-03-13 18:06 UTC (History)
0 users

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


Description Hobbes 2007-08-14 19:14:05 UTC
It would be nice to have the ability to read the articles on wikipedia in a linear manner. This would be a feature analogous to the "Random Article" feature in that it would be primarily for bored people, but would have the added benefit of allowing people to quantify and compare their boredom. One way of accomplishing this may be to make the seed value for the RNG used to determine a random article more prominent in the URL, so that it might easily be changed.
Comment 1 Brion Vibber 2007-08-14 19:37:00 UTC
You can go to Special:Allpages/Last_page_name to get the next N pages. A JavaScript client tool could probably easily use this (or the machine API, better yet, I suspect) to grab 'the next' page for viewing.

I don't think we'll integrate this into the mainline, though, since search and linking are the primary browse methods.

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