Views don't update after changing timezone setting - restart required

RESOLVED FIXED

Status

Calendar
Lightning Only
RESOLVED FIXED
11 years ago
11 years ago

People

(Reporter: Stefan Sitter, Assigned: Joey Minta)

Tracking

Details

Attachments

(1 attachment)

(Reporter)

Description

11 years ago
Views don't update after changing timezone setting - restart required

Steps to reproduce:

0) If not done yet: Go to Lightning pane in Thunderbird options/preferences
   dialog select a timezone (e.g. Europe/Berlin (UTC+1)) and restart Thunderbird

1) Create an test event and note start time / end time

2) Go to Lightning pane in Thunderbird options/preferences dialog. Select
   a different timezone (e.g. America/Los_Angeles (UTC-8)). Press Ok.

3) Check the created event in the view
   --> Views have not changed, event is displayed as before

4) Restart Thunderbird and check the created event in the view
   --> Event is now displayed with start and end time shifted to new timezone
       (9 hours in this example)

Expected Results:
After changing the timezone settings the views should be updated automatically.
(Assignee)

Comment 1

11 years ago
Probably depends on landing bug 321608, since that will finish implementing pref-observers in all views.  These observers can then be wired to listen for the timezone pref too.

Updated

11 years ago
Whiteboard: [cal relnote]
(Assignee)

Comment 2

11 years ago
Created attachment 216319 [details] [diff] [review]
add timezone.local to pref listener

Patch adds a listener for calendar.timezone.local to automatically refresh the views.
Assignee: nobody → jminta
Status: NEW → ASSIGNED
Attachment #216319 - Flags: first-review?(dmose)

Comment 3

11 years ago
Comment on attachment 216319 [details] [diff] [review]
add timezone.local to pref listener

r=dmose
Attachment #216319 - Flags: first-review?(dmose) → first-review+
(Assignee)

Comment 4

11 years ago
Patch checked in.
Status: ASSIGNED → RESOLVED
Last Resolved: 11 years ago
Resolution: --- → FIXED
Whiteboard: [cal relnote]
You need to log in before you can comment on or make changes to this bug.