“ Any uses have been obsoleted by dynamic layouts.
.texhtml needs further investigation. The class is probably added by the math extension tag, and the styling may be legitimately needed. But math rendering has changed a lot since these were added, so it's possible they are no longer needed and it's possible they are broken (bitrotted) since we have some known math display bugs not reported elsewhere.
These are inherited from en.wp. Neither were used meaningfully. times-serif was removed. Here it's totally unused and you can remove the class name. There is also digits. It is similarly unused. ”

“ I would really like you to get rid of the automatic centering of scores—it's a nuisance throughout the DMM as there's no sensible way to put scores inline. I'm happy to centre those that need to be. With the exception of a hymn-book, most of the scores I've done shouldn't be centered, rather they should be inline or left-justified. When I need scores to be left justified I've been putting them in a table, and now I discover that I'm basically table nesting as a workaround. ”

“ Izno (talk) 18:37, 25 November 2022 (UTC) Uses: 30k, and that's just the wikitext version. I don't think moving is practical.
@Izno: As with similar for img and other replaced elements, the issue it's addressing is that "100%" sometimes ends up being more than 100vw, meaning you get horizontal scrollbars even on insane screens, etc.
This is one of the cases where we probably want to long-term move raw wikimarkup (styling owned by MW/skin) to a template (where we can own styling) , and maintain the max-width there. ”

“ After slimming down and pruning, the rest were migrated to MediaWiki:Gadget-Site.css. --Xover (talk) 15:47, 27 April 2024 (UTC)
.poem classes Should really have been a template with attendant TemplateStyles, but since poem is an extension tag and is being used 1) widely and 2) for creative purposes, I am not sure there are any real alternatives to a default Gadget. A lot of the uses of the extension tag would have been better off using {{ppoem}}, but it's a massive backlog that cannot be bot-converted (at best semi-automated in an interactive tool) . ”

“ Since they're otherwise fixed-width in pixels, they easily end up off the page on any kind of mobile screen, which is usually only about 350-ish effective pixels wide (see Help:Preparing_for_export#Formatting_for_small_screens) . And as @Izno says, this isn't from a template. If the centering isn't actually wanted, then get rid, I suppose. @Beeswaxcandle, but would {{Score aligned block}} work better than left-aligning everything to the page margin by default? Inductiveload—talk/contribs 22:04, 2 December 2022 (UTC) .pagetext class Justifies the text in PRP's output in Page: namespace pages. ”

“ You do appear to have some navboxes and things. I'd suggest keeping the rules for definition lists, which show up in that context on en.wp. Izno (talk) 07:28, 27 November 2022 (UTC) Uses
Module:Navbox (same changes as plainlist) Module:Sidebar (same changes as plainlist) Module:WikidataIB (ugh, haven't decided what to do with this one upstream yet) Module:Navbar Module:Collapsible list Template:Flatlist MediaWiki:Wikibase-unconnectedpages-summary (this no longer exists in the code) .plainlist classes Are probably mostly redundant to {{plainlist}} and its TemplateStyles already. ”

“ System messages styled similarly to fmbox These have been copied from enWP, but I don't think anyone would miss them if they were gone. The system boxes are the basic responsibility of MediaWiki, so if any styling is critical it should be upstreamed. In other words, these can probably just go away.
No comment. Izno (talk) 07:30, 27 November 2022 (UTC) I nuked ’em. This is "pretty" styling for a situation that should occur extremely rarely, and whose sensible styling is an upstream responsibility, but we're paying the price on every single page load. ”

“ A better question is why {{fs90}} (90%) exists at all, given {{fine}} (92%) is our standard sizing template. Xover (talk) 00:16, 4 December 2022 (UTC) cite *.printonly Is this needed for anything? We don't use raw cite tags, and our use of the CS1/2 citation templates should be minimal (inappropriate in content namespaces, so only on Author: and Portal: pages plus project spaces) . ”

“ It's used by {{book}} too, for which enWP has no equivalent. Xover (talk) 19:14, 25 November 2022 (UTC) True. I'm not sure it's relevant though. You just put the styles in one place regardless. In general, you can and should move styles without getting stuck in total rework: focus on removing uses that aren't inside a template and then deploy the TemplateStyles and then work on making the templates beautiful. Izno (talk) 01:36, 26 November 2022 (UTC) Meh. I just dumped it in Template:Information/styles.css and called it a day. Removed from Site.css so for this todo it's done. ”

“ Xover (talk) 23:47, 3 December 2022 (UTC) div.fslhInherit > p p-wrapping must be killed with fire! Someone please bribe cscott with a castle in Bavaria or something to assassinate it... *sigh*
This is probably a global workaround for a p-wrapping problem that was common to a small number of templates, and probably at least due to a then-current voodoo belief that line-height: inherit should always be set explicitly. We need to figure out where this is actually used and then either TemplateStyles-ify it or ust drop it if not needed.
Used only in Template:Font-size90%/s. ”