Last modified: 2010-12-31 22:07:14 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 T28520, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 26520 - Add HTML relative links and PREVIOUS, NEXT buttons to WikiBooks sections
Add HTML relative links and PREVIOUS, NEXT buttons to WikiBooks sections
Status: RESOLVED DUPLICATE of bug 1437
Product: MediaWiki extensions
Classification: Unclassified
DynamicPageList (Other open bugs)
unspecified
All All
: Normal enhancement (vote)
: ---
Assigned To: Bawolff (Brian Wolff)
http://en.wikibooks.org/wiki/Cascadin...
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2010-12-31 03:48 UTC by Dan Jacobson
Modified: 2010-12-31 22:07 UTC (History)
0 users

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


Attachments

Description Dan Jacobson 2010-12-31 03:48:31 UTC
Add relative links,
http://www.w3.org/TR/html4/struct/links.html#h-12.1.2
and familiar PREVIOUS UP HOME NEXT buttons to each part of a Wikibook, so the user could read from one part to the next, without first having to go back.
Comment 1 Bawolff (Brian Wolff) 2010-12-31 21:39:31 UTC
How is this a DPL issue?

If this was to be implemented (I believe opera supports such links, so does lynx, which are obviously not a large portion of the market share, but some people do support it, so its not exactly change for change sake) it would probably be implemented manually by wiki-editors using {{#link:some_page|type=next}} -ish syntax (with certain types whitelisted. Don't want people adding css/etc obviously)
Comment 2 Bawolff (Brian Wolff) 2010-12-31 22:07:14 UTC

*** This bug has been marked as a duplicate of bug 1437 ***

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


Navigation
Links