Last modified: 2011-04-14 15:12:45 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 6723 - Separate page title rendering from subpage syntax
Separate page title rendering from subpage syntax
Status: NEW
Product: MediaWiki
Classification: Unclassified
Parser (Other open bugs)
unspecified
All All
: Low enhancement with 2 votes (vote)
: ---
Assigned To: Nobody - You can work on this!
http://en.wikibooks.org/wiki/Wikibook...
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2006-07-17 20:17 UTC by Manuel G. R.
Modified: 2011-04-14 15:12 UTC (History)
0 users

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


Attachments

Description Manuel G. R. 2006-07-17 20:17:36 UTC
Subpages are perfect for organizing chapters inside books in Wikibooks. But some
users are unhappy with how the page level 1 header is rendered using exactly the
same syntax than the used for linking.

It should be a way to display the superpage and subpage titles  in a more
aesthetic and more typical form for a book. One way would be to divide the
header level 1 in one line per each superpage and subpage, or using different
font sizes or font decorations. The slash should not be displayed since it is a
syntax artifact rather than a part of the book naming scheme.

The second line with up links to parent pages could be merged with this new way
of displaying the module titles, so there is no redundacy.

This rendering should be activated through a configuration option so other
projects are not disturbed.
Comment 1 Kellen 2006-07-17 23:36:05 UTC
A better solution might be to use the local styleshee to affect these elements
rather than building it into the other configuration. Wrap each individual
element of the header and breadcrumbs with html elements and have unique classes
for each level. For example, you could have: .heading-level<N> where <N> is the
subpage number starting at 0 for the top level. The slashes should each be
wrapped in .headerslash or somesuch, so the stylesheet could just turn off their
display.
Comment 2 Aryeh Gregor (not reading bugmail, please e-mail directly) 2006-07-17 23:44:06 UTC
> A better solution might be to use the local styleshee to affect these elements
> rather than building it into the other configuration. Wrap each individual
> element of the header and breadcrumbs with html elements and have unique classes
> for each level. For example, you could have: .heading-level<N> where <N> is the
> subpage number starting at 0 for the top level. The slashes should each be
> wrapped in .headerslash or somesuch, so the stylesheet could just turn off their
> display.

That would be a partial solution, but it wouldn't affect the possibly
counterintuitive entry of page tities into the "Go" bar, nor would it affect the
page title (as in, in the browser).  Looking at the Monobook.php implementation,
even the stylesheet issue would seem to be nontrivial, although perhaps not
difficult for someone a bit more familiar with the skin classes than I.  A more
complete solution would be to make subpage-ness distinct from page name, but
that would certainly be a much more difficult change to make.
Comment 3 Manuel G. R. 2006-07-18 22:20:31 UTC
We have made some mockups for illustrating how this could be displayed. We have
tried to preserve the possibility of copy-pasting the page title for a link. See:

http://es.wikibooks.org/wiki/Usuario:Ciencia_Al_Poder/Pruebas

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


Navigation
Links