Page MenuHomePhabricator

Subpages class treated differently in Minerva/Mobile
Closed, DuplicatePublic

Description

I recently noticed that the CSS class subpages is treated differently in the Minerva skin. In Vector, Monobook, Timeless etc., span.subpages is getting a display:block, while in Minerva it does not. This causes problems when there are two span elements within the contentSub / minerva__subtitle of a page, as it happens in category subpages on dewiki, such as this one. If subpages is not formatted as a block element, the two lines will stick together without line break or spacing in between. We are now explicitly forcing display:block via Minerva.css and Mobile.css, but I feel like there should be a more obvious solution. Is there any reason why Minerva is treating subpages differently?

Maybe related to T256932.

Event Timeline

@XanonymusX is there a more up-to-date link that demonstratess this issue? I think I understand it but want to make sure.

Right now I am leaning towards recommending span.subpages should be changed to a DIV element in this particular case since this seems like a sensible default given how it is used:
https://gerrit.wikimedia.org/g/mediawiki/core/+/3c5ef86bc0d82056929ada2287b4208a69420459/includes/skins/Skin.php#2563

The linked page is still the relevant use case. To see the issue, you just need to be logged in and get rid of span.subpages {display: block;} in Minerva.css and Mobile.css, which is our temporary fix.

Do I need to enable a gadget? Looking fine to me even when that rule is removed:

Screen Shot 2021-08-24 at 8.41.27 AM.png (676×2 px, 151 KB)

Hm, so you basically do not see the element mw-fr-category-oldreviewed. I thought logged-in users would see it generally, but since it comes from FlaggedRevs, I suppose you need reviewer rights in order to see it.

This is what it looked like:

Screenshot Category Subtitle.jpg (592×1 px, 147 KB)

This is what the fix does:

Screenshot Category Subtitle Fix.jpg (616×1 px, 147 KB)

Ahh FlaggedRevisions.. I see. Yeh that extension is not maintained, so I can imagine it's restricted to only places it needs to show. Thanks for that context.

Yes! thanks for connecting these!