The documentation is incorrect and misleading.

I think adding the following to Special:MyPage/common.css is seems to also a good short term solution but with no guarantee that will continue working:

.mw-body-content {
    text-size-adjust: 200%;
}

Content transform team are working on this.

Ie. My recommendation would be to undo the ID change in rECACff06099b0c91

Ideally I would love it if it replaced the existing link using the same ID rather than adding a link. Semantically these actions are identical. Classes should be used to distinguish them if additional CSS is needed.

In T357352#11265385, @OTichonova wrote:

Hi @Scardenasmolinar. Are the user groups a vital part of the card? If not, I wouldn't keep them, as the elements in the card are taking up a lot of the screen.

cc @Samwalton9-WMF

Please create a subtask for QA.

Thank you for tagging this task with good first task for Wikimedia newcomers!

Is there any way I can help contribute?

Is there a new timeline for this? (Apologies if this is common knowledge I am still in the process of catching up after being away)

The settings page ( https://en.m.wikipedia.org/w/index.php?title=Special:MobileOptions&returnto=Main+Page ) provides this - it will save to cookie or preference depending on your login status. The preferences page requires two clicks on a mobile device so this got overlooked.

(The editor and associated workflow is maintained by the editing team so untagging Reader Experience Team). Note, Reader Growth Team maintains MobileFrontend if any changes needed go beyond the editor.

The bytes shipped add up as up to 3 different image sizes could be used for the open graph tags leading to slower load times than possible as well as extra CO2 emissions.

The favourite button is shown on all subpages of templates. It is not always appropriate for subpages like /doc and /testcases. We should find a way to exclude certain subpages from having the favourite button shown.

MobileFrontend doesnt make any modifications to thid page.

This would need an update in mediawiki.user library
https://gerrit.wikimedia.org/g/mediawiki/core/+/3c4d177456c3a0a642f61aafd4a7562e34850a0f/resources/src/mediawiki.user.js

In T396268#10896498, @Alex44019 wrote:

No, it only covers users who can set those browser- or system-wide preferences that automatic dark mode checks. This task is for users who have to override automatic detection by manually selecting the dark mode in Vector's rail.

Another simpler option might be adding an offset option for chart axis spec so editors can tweak this themselves.

Timeless is currently without any maintainers and not actively developed.

What should have happened instead?:
The entire screen should look black.

In T394655#10873982, @Ponor wrote:

@Jdlrobson True, but interface administrators are only volunteers who could do things but never should. Are there global interface administrators or developers who could/should do this instead?

Please subscribe to tech news (https://mediawiki.org/wiki/Project:Tech_News) All breaking changes follow the process clearly defined on https://m.mediawiki.org/wiki/Stable_interface_policy/Frontend

(For now)

Does not impact web team.

I understand Jan is looking into this.