Chromium badly parsers timezone avoiding TweetDeck login via Twitter
Reported by
beos...@gmail.com,
Mar 7 2018
|
||||
Issue descriptionUserAgent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:58.0) Gecko/20100101 Firefox/58.0 Steps to reproduce the problem: 1. Open Chromium (clean cache or Incognito mode). 2. Go to http://tweetdeck.twitter.com 3. Try to login using Twitter. 4. Login do not work. What is the expected behavior? Login success and enter in TweetDeck allowing tweet from that application. What went wrong? Login in TweetDeck using Twitter failed throwing this message: Sorry, something went wrong. Please try again later. (Unsupported time zone specified undefined) Did this work before? Yes Chromium 63. Chrome version: 64.0.3282.167 Channel: stable OS Version: Ubuntu 16.04.3 64bit Flash Version:
,
Mar 8 2018
Unable to reproduce this issue on reported version 64.0.3282.167 using Ubuntu 14.04 and Ubuntu 17.10 with steps mentioned below. 1. Launched 64.0.3282.167 chromium and opened Incognito window. 2. Navigated to http://tweetdeck.twitter.com and logged in with valid credentials -- login worked successfully. Attaching screencast for reference. As ET team do not have Ubuntu 16.04, could someone from Inhouse team please help in triaging this issue further. Hence adding TE-NeedsTriageFromHYD label. Thanks!
,
Mar 8 2018
Attaching screencast for reference.
,
Mar 9 2018
I've made an screencast to show how Chromium fails. BTW, the same version of Google Chrome fails in the same way. Maybe the problem is related with Ubuntu? I think the problem is related with timezone strings, but I don't know if it is thrown by Chromium, TweetDeck or Ubuntu (I've tried to change TZ name in Ubuntu, either to UTC and other names, but the problem persists). TweetDeck works well in Firefox, either in Linux and Windows. In Google Chrome in Windows (same version) this problem is not raised.
,
Mar 9 2018
Unbale to reproduce the issue on Debian Rodete with chromium #64.0.3282.0, able to login to http://tweetdeck.twitter.com successfully. Attaching the screen-cast for reference Note: Since TE doesn't able to reproduce this issue adding TE-NeedsTriageHelp label
,
Mar 13 2018
Function that fails is "toLocaleTimeString()" from "Date" class. Specific function call is:
console.log(new Date("2018-03-13 16:04:00+00:00").toLocaleTimeString("es-ES"));
Minimum example that fails is attached. It fails both in Chromium and Chrome 64.0.3282.167 (V8 version is 6.4.388.45) in Ubuntu 16.04.4 x86_64 with Unity Desktop. It doesn't fail in Firefox.
Error shown (from developers tools console) is:
timezone.html:6 Uncaught RangeError: Unsupported time zone specified undefined
at new DateTimeFormat (native)
at Date.toLocaleTimeString (native)
at file:///home/user/Desktop/timezone.html:6:128
(anonymous) @ timezone.html:6
,
Mar 26 2018
Finally I've found how to reproduce the error: 1. Open a terminal and set TZ variable to ":/etc/localtime" using "export TZ=':/etc/localtime'" (this is to avoid unnecessary system calls according to this page: https://blog.packagecloud.io/eng/2017/02/21/set-environment-variable-save-thousands-of-system-calls/ ). 2. Open Chrome or Chromium from that terminal (launch 'google-chrome' or 'chromium-browser'). 3. Try to login in TweetDeck. 4. The error above is shown.
,
Apr 2 2018
Hello again. Has someone reviewed this issue? As I stated in the previous comment, I've finally been able to reproduce it.
,
Aug 4
Can confirm that it's reproducible and still prevents logging in to TweetDeck.
,
Nov 23
*** Mass UI Triage *** We were unable to find repro steps for this bug. If you have more data to reproduce this bug or have clear repro steps, please reopen or file a new issue. Thanks! |
||||
►
Sign in to add a comment |
||||
Comment 1 by susan.boorgula@chromium.org
, Mar 7 2018Labels: Needs-Bisect Needs-Triage-M64