Page MenuHomePhabricator

Replace legacy breakpoint value tokens in web team extensions
Closed, ResolvedPublic1 Estimated Story Points

Description

Background

DST team needs help removing legacy code. See T349793 for clear instructions on how to

User story

As as developer I only want to use the latest and greatest code.

Acceptance criteria

Communication criteria - does this need an announcement or discussion?

N/A

Rollback plan

If needed, we should aim to create a new patch to statically define the variables in the Minerva or Vector skin.

This task was created by Version 1.0.0 of the Web team task template using phabulous

Event Timeline

Change #972327 had a related patch set uploaded (by Jdlrobson; author: VolkerE):

[mediawiki/skins/MinervaNeue@master] styles: Replace deprecated breakpoints

https://gerrit.wikimedia.org/r/972327

Per T349793#9844296 hope is to merge these tuesday (tomorrow)

Change #1037184 had a related patch set uploaded (by Jdlrobson; author: VolkerE):

[mediawiki/extensions/MobileFrontend@master] styles: Replace deprecated breakpoint tokens with Codex defined ones

https://gerrit.wikimedia.org/r/1037184

Change #1037184 merged by jenkins-bot:

[mediawiki/extensions/MobileFrontend@master] styles: Replace deprecated breakpoint tokens with Codex defined ones

https://gerrit.wikimedia.org/r/1037184

I created T367103. Discussing short term solutions as we speak.

After investigating this issue, and much confusion, we discovered it only impacted Monobook, and there was an issue in the original implementation of Codex carrying MediaWiki skin variables was uncovered. This ticket is therefore not blocked on this.

Hey for completeness i've merged https://gerrit.wikimedia.org/r/c/mediawiki/skins/Vector/+/1040085?usp=search after some thorough checks, Pixel was not flagging any issues, and now we have understood and addressed https://phabricator.wikimedia.org/T367103 I see no reason not to merge this. Having a predictable state for these design tokens seems preferable than keeping Vector using the old ones, especially given our big update to OOUI/Codex tomorrow.

Seems like all this work has been worthwhile as it uncovered some existing issues with how breakpoints are used and troubles with our LESS parser. It's also led to some visual improvements in the mobile site.