Change Details

I think where styles are used only on one template, the obvious solution will be to migrate the styling to a slot on the template page. However, it's not obvious to me how these two will interact when the styling is shared by two (or more) different templates. Should the styles be in a style slot on a 3rd (otherwise-empty) template page, and the whole template is referenced? How will the whole template be referenced (`@import`? otherwise?)? This ensures the minimum necessary part is included in both templates. However, this leaves an 'extraneous' page lying around solely to hold styles. Another way would be to hold the template styles in a slot on one or the other templates, and then the second template would reference the styles in that slot. (We still don't know if we `@import` or otherwise.) However, does/should/will that increase the size of the second template by just the size of the styles, or also the entire rest of the first template? This task is a bit of a ways away still, but I'm thinking about it now so it should clearly be important for both projects :).

Once MCR is ready, most template styles should be slots on the template page instead of separate pages. This requires {T187935} and figuring out the details of multi-slot transclusion. What to do when the same style is shared by multiple templates is less clear. It can be worked around (put the style on an empty template, transclude that template into all templates needing the styles), but we might want to handle it via slot-level redirects. (The same also applies to {T200614}.) We could also handle it on the CSS parser level by supporting `@import` (and maybe turning it into something akin to module dependencies in ResourceLoader?) but that seems vastly more complicated without any clear benefit.

I think wherOnce MCR is ready, most template styles are used onlyshould be slots on onthe template,ate page instead of separate pages. the obvious solution will be to migrateThis requires {T187935} and figuring out the styling to a slot on the template pagedetails of multi-slot transclusion. However, it's not obvious to me how these two will interact when the styling is shared by two (or more) different templates. Should the styles be in a style slot on a 3rd (otherwise-empty) template page, and the whole template is referenced? How will the whole template be referenced (`@import`? otherwise?)? This ensures the minimum necessary part is included in both templates. However, this leaves an 'extraneous' page lying around solely to hold styles. Another way would be to hold the template styles in a slot on one or the other templates,What to do when the same style is shared by multiple templates is less clear. and then the second template would referenceIt can be worked around (put the styles in that slot. on an empty template, (We still don't know if we `@import` or otherwise.) Howevertransclude that template into all templates needing the styles), does/should/will that increase the size of the second template by just the size of the styles,but we might want to handle it via slot-level redirects. or also the entire rest of the first template? This task is a bit of a ways away still, but I'm thinking about it now so it should clearly be important for both projects :)(The same also applies to {T200614}.) We could also handle it on the CSS parser level by supporting `@import` (and maybe turning it into something akin to module dependencies in ResourceLoader?) but that seems vastly more complicated without any clear benefit.