Maniphest T11174

Per-page CSS classes for all pages in hierarchy
Closed, DeclinedPublic
Actions

Assigned To

None

Authored By

	• bzimport
	Mar 5 2007, 9:17 PM

Tags

Referenced Files

None

Subscribers

Description

Author: bugzilla

Description:
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.

Version: 1.9.x
Severity: enhancement

Details

Reference: bz9174

Related Objects
Search...

		Status	Subtype	Assigned	Task
		Invalid		None	T24771 CSS hooks in output (tracking)
		Declined		None	T11174 Per-page CSS classes for all pages in hierarchy

Event Timeline

• bzimport raised the priority of this task from to Low.Nov 21 2014, 9:37 PM

• bzimport added a project: MediaWiki-User-Interface.

• bzimport set Reference to bz9174.

• bzimport added a subscriber: Unknown Object (MLST).

• bzimport created this task.Mar 5 2007, 9:17 PM

ayg wrote:

It would make more sense to have pageparent-foo_bar or something.

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

• Phabricator_maintenance added a project: CSS.Jul 29 2016, 7:16 PM

• Phabricator_maintenance removed a subscriber: • wikibugs-l-list.

• Phabricator_maintenance removed a parent task: T14788: [DO NOT USE] CSS (tracking) [superseded by #CSS].Jul 29 2016, 7:16 PM