[Cosmo-dev] Unsupported Timezone Ids

[Aparna Kadakia]

This problem was particularly exhibited in the following test  
collection created on Hub for testing migration:

URL to the collection on Hub:
https://hub.chandlerproject.org/pim/collection/ 
0a97dbca-49ef-11dc-9af9-000ae42c2fb3?ticket=00qm1o93u0

URL to the same collection on lab.osaf.us after migration:
View and Edit: http://lab.osaf.us/pim/collection/ 
0a97dbca-49ef-11dc-9af9-000ae42c2fb3?ticket=00qm1o93u0

Aparna

On Aug 17, 2007, at 3:32 PM, Bobby Rullo wrote:

> This is rearing its ugly head in testing.
>
> Somehow there are a lot of events out there with the timezone  
> "PST", which cosmo (ui) doesn't know anything about.
>
> When I say "out there" I mean on lab.osaf.us, which has a bunch of  
> migrated data. I am curious to know where these PST events come  
> from...
>
> The problem with this is that in a collection with lots of events  
> like this (Aparna, could you send a link?) you get the whole  
> unsaved changes dialog box when you click around.
>
> What is odd is that if you view this event in Desktop, it displays  
> as "America/Los Angeles" - but it is stored as tzId 'PST' in cosmo  
> - I know this because I examined what comes back from the server.
>
> I have a fix which will allow this be tzId to be displayed in the  
> drop-down, but won't give the correct offset (will act as  
> floating). It will prevent the dialog box.
>
> bobby
>
>
> On Aug 16, 2007, at 11:44 AM, Bobby Rullo wrote:
>
>> Hi,
>>
>> In bug 10495 a bug regarding timezones in the cosmo UI was exposed.
>>
>> Basically, if Cosmo UI gets a tzId that it doesn't recognize, it  
>> treats it as if it has a GMT offset of zero, which means that  
>> unless you're timezone actually is GMT, your event will appear on  
>> the wrong place in the calendar.
>>
>> I think the original intent was to treat such timezones as  
>> floating, which makes much more sense to me. The only downside to  
>> this is that in the timezone selector box it will appear as  
>> "None", that is, no timezone selected. And then when you click  
>> away it will think that a change has  been made and will prompt  
>> you for to see if you want to save changes.
>>
>> There are probably better ways to handle this, but I think they  
>> should wait till after preview, when we re-work the tz selector.  
>> In the meantime, this won't pop up that much, as these timezones  
>> are rare-ish.
>>
>> If no-one objects, I'll go ahead and implement as described.
>>
>> bobby
>> _______________________________________________
>> cosmo-dev mailing list
>> cosmo-dev at lists.osafoundation.org
>> http://lists.osafoundation.org/mailman/listinfo/cosmo-dev
>
> _______________________________________________
> cosmo-dev mailing list
> cosmo-dev at lists.osafoundation.org
> http://lists.osafoundation.org/mailman/listinfo/cosmo-dev