Change Details

**Steps to reproduce:** Open any Entity (e.g. https://test.wikidata.org/wiki/Q172818) * on desktop ** https://test.wikidata.org/wiki/Q172818?uselang=mul ** https://test.wikidata.org/wiki/Q172818?uselang=en * or mobile ** https://test.m.wikidata.org/wiki/Q57591?uselang=en **What happens?** * The termbox initially shows the languages sorted in one order (e.g. `mul`, `en`, `de`, `pt`), but then JS runs and they get reordered into another order (e.g. `mul`, `de`, `en`, `pt`). * The behavior changes based on your logged-in state / Babels (`de-N`, `en-4`, `pt-1` in the example given), and uselang (`mul` in the example given). * There is also an accompanying console warning: > Existing entitytermsforlanguagelistview DOM does not match configured languages Mobile-only: * On mobile an additional result is that the formatting is off ("No label defined" is bold, "blah" is not). {F35309750} **What should have happened instead?** * The termbox should show the languages correctly ordered from the start (just like we are used to from Wikidata proper). That is, the languages do not jump around. * The formatting on mobile is normal again. **Notes:** * We thought we’d fixed this with T307808, but there’s still some remaining issue. * At some point we will change the sorting to allow `mul` to be there by default (see T312176). **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)

**Steps to reproduce:** Open any Entity (e.g. https://test.wikidata.org/wiki/Q172818) * on desktop ** https://test.wikidata.org/wiki/Q172818?uselang=mul ** https://test.wikidata.org/wiki/Q172818?uselang=en * or mobile ** https://test.m.wikidata.org/wiki/Q57591?uselang=en **What happens?** * The termbox initially shows the languages sorted in one order (e.g. `mul`, `en`, `de`, `pt`), but then JS runs and they get reordered into another order (e.g. `mul`, `de`, `en`, `pt`). * The behavior changes based on your logged-in state / Babels (`de-N`, `en-4`, `pt-1` in the example given), and uselang (`mul` in the example given). * There is also an accompanying console warning: > Existing entitytermsforlanguagelistview DOM does not match configured languages Mobile-only: * On mobile an additional result is that the formatting is off ("No label defined" is bold, "blah" is not). {F35309750} **What should have happened instead?** * The termbox should show the languages correctly ordered from the start (just like we are used to from Wikidata proper). That is, the languages do not jump around. * The formatting on mobile is normal again. **Notes:** * We thought we’d fixed this with T307808, but there’s still some remaining issue. * At some point we will change the sorting to allow `mul` to be there by default (see T312176). **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) **Original:** When I load https://test.wikidata.org/wiki/Q172818?uselang=mul, the termbox initially shows the languages `mul`, `en`, `de`, `pt`, but then JS runs and they get reordered into `mul`, `de`, `en`, `pt` – English and German switch places. (My Babel is currently `de-N`, `en-4`, `pt-1`.) There is also an accompanying console warning: > Existing entitytermsforlanguagelistview DOM does not match configured languages This needs to be looked into. (I thought I’d fixed this with T307808, but clearly there’s still some remaining issue.)

**Steps to reproduce:** Open any Entity (e.g. https://test.wikidata.org/wiki/Q172818) * on desktop ** https://test.wikidata.org/wiki/Q172818?uselang=mul ** https://test.wikidata.org/wiki/Q172818?uselang=en * or mobile ** https://test.m.wikidata.org/wiki/Q57591?uselang=en **What happens?** * The termbox initially shows the languages sorted in one order (e.g. `mul`, `en`, `de`, `pt`), but then JS runs and they get reordered into another order (e.g. `mul`, `de`, `en`, `pt`). * The behavior changes based on your logged-in state / Babels (`de-N`, `en-4`, `pt-1` in the example given), and uselang (`mul` in the example given). * There is also an accompanying console warning: > Existing entitytermsforlanguagelistview DOM does not match configured languages Mobile-only: * On mobile an additional result is that the formatting is off ("No label defined" is bold, "blah" is not). {F35309750} **What should have happened instead?** * The termbox should show the languages correctly ordered from the start (just like we are used to from Wikidata proper). That is, the languages do not jump around. * The formatting on mobile is normal again. **Notes:** * We thought we’d fixed this with T307808, but there’s still some remaining issue. * At some point we will change the sorting to allow `mul` to be there by default (see T312176). **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) **Original:** When I load https://test.wikidata.org/wiki/Q172818?uselang=mul, the termbox initially shows the languages `mul`, `en`, `de`, `pt`, but then JS runs and they get reordered into `mul`, `de`, `en`, `pt` – English and German switch places. (My Babel is currently `de-N`, `en-4`, `pt-1`.) There is also an accompanying console warning: > Existing entitytermsforlanguagelistview DOM does not match configured languages This needs to be looked into. (I thought I’d fixed this with T307808, but clearly there’s still some remaining issue.)