Some raw message keys shown literally when using an invalid one-letter ?uselang=x value
Open, Needs TriagePublic
Actions

Assigned To

None

Authored By

	Raymond
	Apr 19 2020, 9:53 AM

Description

Some message keys are shown literally when using ?uselang=x with x=1 letter

Steps to reproduce:

Call a page like https://de.wikipedia.org/wiki/Chevrolet_900
Change URL by adding ?uselang=a

Some messages are shown as literally message key, see markings in the screenshot

This does happen for 1 character language codes only (which are invalid). For invalid language codes with 3 or more characters this effect is not shown.

Event Timeline

Raymond created this task.Apr 19 2020, 9:53 AM

Restricted Application added a subscriber: Aklapper. · View Herald TranscriptApr 19 2020, 9:53 AM

uselang is implemented in core.

Aklapper renamed this task from Some message keys shown literally when using ?uselang=x to Some raw message keys shown literally when using an invalid one-letter ?uselang=x value.Apr 19 2020, 1:37 PM

Why would you use ?uselang=a, what's the usecase?

In T250609#6069397, @Ammarpad wrote:

Why would you use ?uselang=a, what's the usecase?

No usecase. I made a typing error in the URL and spotted this bug. For non-existing language codes all messages should be shown in the default content language, for Commons English.

The message are set by javascript. There are first in english and than changed (Sometimes the page was loaded/rendered slow and the change of the description was visible)

For example: "In other language" -> "(uls-plang-title-languages)"
or "edit" -> "(vector-view-edit)"

That is a js vs. php thing, so maybe resourceloader?

Ammarpad unsubscribed.Jun 13 2020, 12:02 PM

Umherirrender unsubscribed.Feb 27 2021, 9:20 PM

Some raw message keys shown literally when using an invalid one-letter ?uselang=x valueOpen, Needs TriagePublicActions

Description

Event Timeline

Some raw message keys shown literally when using an invalid one-letter ?uselang=x value
Open, Needs TriagePublic
Actions