Page MenuHomePhabricator

Badges are not compatible with Vector 2022 when ULS is disabled due to assumption around margin
Open, Needs TriagePublic

Description

Steps to reproduce:

Screenshots:

Screen Shot 2021-07-13 at 1.43.24 PM.png (778×1 px, 504 KB)

What happens?

Badges are not visible.

What should have happened instead?

Badges appear next to language links.

See on old Vector:

Screen Shot 2021-07-13 at 1.40.31 PM.png (598×346 px, 40 KB)

Notes:

  • On new Vector the CSS applies but UL element has a margin of 0.
  • Instead of using :marker it might make sense to use a pseudo :before element to achieve the same, or explicitly setting a margin on elements where it is required to apply
  • there is a workaround (see T286612#7210250)

Acceptance criteria:

  • We understand the problem that leads to this issue.
  • The problem is solved (or if solving the problem is out of scope, then please create a follow-up task, so we can discuss it).

Event Timeline

@hoo is this something you could help me get prioritized?

Is the above workaround still needed?

It seems the <ul> is not (or no longer?) displayed directly, but used as source data to generate the widget that is actually displayed.

Is the above workaround still needed?

It seems the <ul> is not (or no longer?) displayed directly, but used as source data to generate the widget that is actually displayed.

Many editors have ULS disabled, since it previously powered compact links, which wasn’t everyone’s cup of tea. So the answer is yes.

Jdlrobson renamed this task from Badges are not compatible with new Vector due to assumption around margin to Badges are not compatible with Vector 2022 due to assumption around margin.Oct 5 2022, 5:48 PM
Jdlrobson added a subscriber: TheDJ.
Manuel updated the task description. (Show Details)

This seems fixed already (I checked on fr and vi, test looks similar on the first glance).

Is there still something to do here?
If yes, what would be the practical steps for me to test/reproduce this?

This seems fixed already (I checked on fr and vi, test looks similar on the first glance).

Is there still something to do here?
If yes, what would be the practical steps for me to test/reproduce this?

https://fr.wikipedia.org/wiki/MediaWiki:Vector.css#L-116 has a workaround for this bug. Vietnamese Wikipedia probably has one too. Use ?safemode=1 to actually test how it looks. For example, https://ru.wikipedia.org/wiki/Россия?useskin=vector-2022&safemode=1 shows the bug still present.

Jdlrobson renamed this task from Badges are not compatible with Vector 2022 due to assumption around margin to Badges are not compatible with Vector 2022 when ULS is disabled due to assumption around margin.Oct 25 2022, 3:40 PM
Jdlrobson updated the task description. (Show Details)

Thank you @stjn for the clarification!

@Jdlrobson: Before the Wikidata development team gets started on this, could you please advise if it still makes sense to work on this in the context of the planned changes (e.g. T310259)?

I don’t see any connection between this and T310259. T310259 touches the ULS-based language selector, this task is about the much more usable non-ULS-based one.

Manuel changed the task status from Open to Stalled.Nov 9 2022, 7:03 PM

Thank you, @Tacsipacsi, I see that now! A word from @Jdlrobson would still help me to understand if this is still needed for some WMF purposes or not.

@Tacsipacsi I believe the maintainers have now made the decision to disable the non-ULS based dropdown. Please see this conversation T319690#8358870.

I believe because of that decision, this bug now only applies to the non-JavaScript version of the page (and presumably if a gadget is created to workaround the decision in T319690#8358870). The language menu also appears in some projects where the language button is not shown e.g. commons.wikimedia.org (i'm not sure if these sites are a problem as I'm not too familiar with the badge functionality).

That said I think the existing use of :marker is problematic is not compatible with how we are building out menus in skins and should be considered technical debt. It may break in other skins (particularly Vector) as the skin system evolves if we don't want this feature to degrade over time.

Manuel changed the task status from Stalled to Open.Nov 15 2022, 8:04 AM
Manuel added a project: Technical-Debt.