Last modified: 2011-07-07 08:12:11 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 T11174, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 9174 - Per-page CSS classes for all pages in hierarchy
Per-page CSS classes for all pages in hierarchy
Status: RESOLVED WONTFIX
Product: MediaWiki
Classification: Unclassified
Interface (Other open bugs)
1.9.x
All All
: Low enhancement (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks: css 22771
  Show dependency treegraph
 
Reported: 2007-03-05 21:17 UTC by Philip Withnall
Modified: 2011-07-07 08:12 UTC (History)
1 user (show)

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


Attachments

Description Philip Withnall 2007-03-05 21:17:59 UTC
The new per-page CSS feature is great, but I think it would be useful if <body>
had classes for all pages in the current page hierarchy.
For example, if you had a page foo/bar/meh, instead of having one <body> class
of "page-foo_bar_meh", you'd have three: "page-foo page-foo_bar
page-foo_bar_meh". This would be useful for places like StrategyWiki
(http://strategywiki.org/), where guides are organised using sub-pages.

I suppose this is an extension of bug #5795.
Comment 1 Aryeh Gregor (not reading bugmail, please e-mail directly) 2007-03-06 02:11:17 UTC
It would make more sense to have pageparent-foo_bar or something.
Comment 2 DieBuche 2011-07-07 08:12:11 UTC
body[className*=page-foo] matches page-foo, page-foo_bar and page-foo_bar_meh
body[className*=page-foo_bar] matches page-foo_bar and page-foo_bar_meh

So adding additional classes doesn't seem to be neccessary here

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


Navigation
Links