Last modified: 2014-03-07 11:50:27 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T37926, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 35926 - Cookie and Cache conflict resulting in wrong language being displayed
Cookie and Cache conflict resulting in wrong language being displayed
Status: NEW
Product: MediaWiki extensions
Classification: Unclassified
LanguageSelector (Other open bugs)
unspecified
All All
: Low major (vote)
: ---
Assigned To: Nobody - You can work on this!
http://translatewiki.net/wiki/Main_Page
: i18n
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2012-04-12 19:58 UTC by Srikanth Logic
Modified: 2014-03-07 11:50 UTC (History)
9 users (show)

See Also:
Web browser: Google Chrome
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments

Description Srikanth Logic 2012-04-12 19:58:05 UTC
This happens on Google chrome but not on firefox.

1. My interface language is English
2. I select Tamil from langauge selector and expect future pages on site load with Tamil interface.
3. I open a page which was previously viewed in Hindi interface and it loads in Hindi interface against expected Tamil interface.


This is probably something due to the cookie handling mentioned in bug 35842 comment 2

awjr was able to reproduce the same as well.
Comment 1 Niklas Laxström 2012-04-13 13:37:55 UTC
On which wiki did you reproduce it?
Comment 2 Arthur Richards 2012-04-19 16:56:21 UTC
I reproduced it on translatewiki.net
Comment 3 Nemo 2013-03-06 17:00:17 UTC
I suppose it was about ULS? I don't remember if it was already enabled on TWN in April.
Comment 4 Siebrand Mazeland 2013-04-02 11:20:11 UTC
This is LanguageSelector, not ULS.

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links