1863985 - English (GB) language setting is not being respected in v.119.0.1

Status: RESOLVED INCOMPLETE

(Web Compatibility :: Site Reports, defect)

Description

[Peter Parsons]

Attachment: Screenshot showing date in MM/DD rather than DD/MM format.

User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:109.0) Gecko/20100101 Firefox/119.0

Steps to reproduce:

Accessed an American-based website with my language settings set to English (GB) after upgrading to v.119.0.1. I compared with the same page on the latest version of Chrome and the latest version of Safari on the same laptop to verify that this only happens in Firefox.

Actual results:

The website showed weeks and dates in English (US) format (week starts on Monday, date using MM/DD/YYY format) rather than my selected English (GB) preference.

Expected results:

My English (GB) language settings should have been respected and displayed (i.e. week starts on Monday, date format is DD/MM/YYYY).

Comment 1

[BugBot [:suhaib / :marco/ :calixte]]

The Bugbug bot thinks this bug should belong to the 'Firefox::Settings UI' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.

Comment 2

[Francesco Lodolo [:flod]]

What is the website? There is also a possibility that the website changed something on their side.

From which version did you update?

Comment 3

[Peter Parsons]

I updated from 118 to 119.0.1.

The website is arbitersports.com.

The language settings are being respected in Chrome and Safari on the same laptop. The pages worked fine prior to updating to v.119.0.1. This behaviour appeared only once I updated to v.119.0.1.

Comment 4

[Peter Parsons]

I've just tested it on my Android phone. It works as expected there too.

Comment 5

[Francesco Lodolo [:flod]]

Could you provide any more info on how to get to the screen in your screenshot, or a screen with dates?

Comment 6

[Peter Parsons]

You have to be logged in to the account in order to be able to access those pages. I can provide screenshots comparing Firefox 119 with Chrome, Safari and Firefox on Android for comparison.

Comment 7

[Petruta Horea [:phorea]]

Could you please install mozregression and run it using the same profile (so that you won't have to sign in each time) using builds from 118 to 119.0.1 (the app will download them automatically) to see which bug introduced this regression? Thank you!

Comment 8

[Peter Parsons]

Using that tool, it works fine in 118.

You'll need to point me at instructions as to how to go any more fine grained since there isn't anything useful I can find that tells me how to do that.

Comment 9

[Donal Meehan [:dmeehan]]

Thanks for trying mozregression to narrow down the cause.

mozreggresion works by integrating through different Firefox builds, each time it will ask you was the build good or bad.

The goal is to try your steps to reproduce in each build, mozreggresion will narrow down to a build that first introduced the issue, and then provide an output of changes that were included in that build.

It might take several builds before it narrows down the culprit.

There's a video and some instructions in the quickstart guide, hopefully that helps?
If you are using the command line version, you could try mozregression --good 118 --bad 119.0.1. This will narrow down to only changes between 118 and 119.01.

Comment 10

[Peter Parsons]

That video shows a bisection wizard which is not available to me when I start the GUI on MacOS, and there is no command line binary available after the installation ("find / -name mozregression" returns no results other than a directory located in .mozilla).

As such, I can't do this bisection testing. I've tested v118, it works. 119.0.1 doesn't.

Comment 11

[Liz Henry (:lizzard)]

Is this issue still showing for you in a current version of Firefox? Just checking - if it is then maybe we can make an account on this site and see the issue and what may be causing it.

Comment 12

[Sky Schubert [:skyschub]]

I'm going to close this as incomplete for now. If this is still an issue, please file a new report.