Resulting from T169910, we've started with extracting
legacy.less still carries a number of i18n specific styles on directionality. They should be extracted as well.
| Subject | Repo | Branch | Lines +/- | |
|---|---|---|---|---|
| Extract rules and add 'i18n-directionality.less' | mediawiki/core | master | +140 -98 | |
| Combine input type directionality selectors | mediawiki/core | master | +7 -16 |
Change 577369 had a related patch set uploaded (by VolkerE; owner: VolkerE):
[mediawiki/core@master] Extract rules and add 'i18n-directionality.less'
What problem will this explicitly solve for Minerva? Can you update the description with a line that Olga can use for prioritisation? Thank you.
Change 577693 had a related patch set uploaded (by VolkerE; owner: VolkerE):
[mediawiki/core@master] Combine input type directionality selectors
@Volker_E could you rephrase this as a problem statement rather than a thing to do? What is the end goal of this work? Easier to maintain code or to fix a bug with an existing skin (this helps me understand your motivations).
It was my understanding that Minerva for example didn't need many of these styles in legacy as it rolls its own. Is there something specifically broken in Minerva (or another skin) that we want to fix?
I was never intending for us to copy over everything in legacy.less - my intention was to scope the new features to useful utilities and generic tag selectors e.g. h1,h2,h3,ul etc..
There is nothing stopping you pulling out LESS modules and importing them directly inside legacy.less (outside ResourceLoaderSkinModule) but the features array is supposed to force us to revisit and wean ourselves off much of the legacy code in legacy.less - a skin developer should be able to clearly grok each feature and decide whether it's useful or not to them before including it.
Change 577693 merged by jenkins-bot:
[mediawiki/core@master] Combine input type directionality selectors
I'm going to assume there's nothing left to do here given the age. If it's still relevant, I think a new task would make sense so that the problem is rescoped and clear.