Closed
Bug 619382
Opened 14 years ago
Closed 14 years ago
Registration form changes language on refresh
Categories
(support.mozilla.org :: Localization, task)
support.mozilla.org
Localization
Tracking
(Not tracked)
RESOLVED
FIXED
2.4.1
People
(Reporter: david.weir, Assigned: erik)
References
()
Details
Steps to get bug
Go to https://support.mozilla.com/en-US/users/register
press refresh
it changes to a other language
| Reporter | ||
Comment 1•14 years ago
|
||
I can conform Jan and EDO is having the issue also
| Assignee | ||
Comment 2•14 years ago
|
||
Here too.
Comment 3•14 years ago
|
||
Verified that support.mozilla.com registration in en-US locale switches between English and various alternate languages upon refresh.
Does not repro on master.support.mozilla.com
Summary: Registration → Registration form changes language on refresh
Updated•14 years ago
|
| Assignee | ||
Updated•14 years ago
|
Assignee: nobody → erik
| Assignee | ||
Comment 5•14 years ago
|
||
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
| Assignee | ||
Updated•14 years ago
|
Assignee: erik → nobody
Component: Users and Groups → Localization
QA Contact: users → localization
Target Milestone: --- → 2.4.1
Comment 6•14 years ago
|
||
As this didn't repro on master, is there a good way to verify this was fixed on master?
Comment 7•14 years ago
|
||
Verified on master with log_replay to simulate the rapid locale switching of prod
Status: RESOLVED → VERIFIED
Updated•14 years ago
|
Assignee: nobody → erik
| Reporter | ||
Comment 9•14 years ago
|
||
hi guys this issue is still happening for sumo on the stable version
I can conform this
Status: VERIFIED → REOPENED
Resolution: FIXED → ---
| Assignee | ||
Comment 10•14 years ago
|
||
Our Thursday push, where this was supposed to go live, was delayed until the 11th.
Status: REOPENED → RESOLVED
Closed: 14 years ago → 14 years ago
Resolution: --- → FIXED
Comment 11•14 years ago
|
||
This has been verified as much as possible on support-stage, will double check post-release on 1/11
You need to log in
before you can comment on or make changes to this bug.
Description
•