Page MenuHomePhabricator

"Configure" link for the termbox is shown below the toggle
Open, Needs TriagePublicBUG REPORT

Description

Steps to replicate the issue (include links if applicable):

What happens?:

The "Configure" link in the "In more languages" toggle above the termbox is shown below the toggle

It's not supposed to be there, so it causes the termbox (and the rest of the page) to jump down while loading

Bildschirmfoto_2024-03-25_11-30-45.png (158×43 px, 2 KB)

What should have happened instead?:

It should be shown to the right of the toggle

Software version (skip for WMF-hosted wikis like Wikipedia):

Other information (browser name/version, screenshots, etc.):

It is to the right of the toggle in https://commons.wikimedia.org/wiki/File:Elizabeth_Peratrovich_Wikidata_item-recoin_collapsed.png (July 2019)

It is below the toggle in https://commons.wikimedia.org/wiki/File:Changing-label.png (May 2020)

Event Timeline

What was the originally intended placement of the Configure link, @Lydia_Pintscher? Arthur found the initial ticket, but I'm unable to locate that information: T86191.

Interestingly enough, even after working on Termbox designs for different projects, I didn't recall noticing this link, which I would encourage us to improve: For starters, it is extremely small in size (with 9.8px, while the minimum recommended web font size is 12px). The superset placement of the link and its copy make it susceptible to be interpreted as an action: it implies "Configure this In more languages section", while what it does is navigate users to information on how to do that using the Babel extension. I'm also unsure of whether users that have configured their babel boxes are aware of their influence on the Termbox's content. It might be a good idea to provide access to that information in all cases.

Tanks, @Lydia_Pintscher. Would you and @Arian_Bozorg be open to implement a new and improved version of this link? It would just involve a change in font size, placement and copy.

Yes sounds good, I'll pop it into the backlog, and prioritise it below MUL and EntitySchemas