[Cosmo-dev] Re: [Design] Design] [Cosmo] Login-related workflows update

[Matthew Eernisse]

Unfortunately, I think the answer to number 2 below might be 'not 
exactly,' since a given UTC offset could be the same for multiple 
timezones -- purely by happenstance. For example, CDT and EST both have 
the same offset in minutes.

We may be able to try to looking at the TZ abbreviation (if any) 
reported in the toString/toLocaleString methods (e.g., 'CDT,'PST').

Without a timezone abbreviation, I don't know what we do -- try to 
guess? I think it might be better just to ask users the first time they 
log in once we implement timezones, and save their preference.


Matthew


Jeremy Epstein wrote:
> From Priscilla's original post:
> 
>>/ + Does the user get assigned a default timezone based on their IP  
> />/ address?
> /So first, the Cosmo user would have an account and is logged in. This  
> happens when the Cosmo user first selects and turns on time-zone  
> support. The first item in the drop down is based on whatever their  
> computer is set to, not based on the IP address. I have been informed  
> that Cosmo the web client can get the time-zone from the browser  
> through javascript–Matthew correct me if I'm wrong here.
> 
> So there are three issues here (BTW I think we are actually in agreement on this)
> 
> 1) is there a way to obtain the hour offset of the user's local machine (relative to UTC) aat the time they choose to enable timezone support? YES
> 2) using this offset is there a way to lookup and set a "good" (at least 80% accurate) default choice for timezone in a timezone dropdown. YEs
> 3) creation of a timezone dropdown based on some good reference data? YES -- you have a library for this.
> 
> If the user's machine couldn't give us a timezone offset (relative to utc) we couldn't even get in the ballpark.
>  
>