[B2G][Calendar] All reminder options appear to be about 9 hours out-of-sync for an All Day event on a Google online calendar

RESOLVED INVALID

Status

RESOLVED INVALID
5 years ago
5 years ago

People

(Reporter: mvaughan, Unassigned)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: burirun3)

Attachments

(2 attachments)

(Reporter)

Description

5 years ago
Created attachment 824271 [details]
Screenshot of reminders set in the local calendar.

Description:
The "1 day before", "2 days before", "1 week before", and "2 weeks before" event reminders are shown in hours on the Google calendar. However the hours shown appear to be 9 hours less than what is expected. So for example a "1 day before" reminder shows as "15 hours" instead of "24 hours" on Google. The phone's calendar's timezone and the Google calendar's timezone appear to both be set to Pacific Time.

Prerequisites:
Have a Google calendar synced to the phone's calendar.

Repro Steps:
1) Update Buri to v1.2 comRIL BuildID: 20131025004000
2) Launch the Calendar app
3) Create a new event (tap '+' button)
4) Enable the "All day event?" checkbox
5) Set the begin and end dates to 11/30/2013
6) Set the "1 day before", "2 days before", "1 week before" and "2 weeks before" reminders
7) Set the event to sync to the Google calendar
8) Tap 'Save' button
9) On a PC, sign into the Google account and navigate to the calendar
10) Click on the event
11) Click on the 'Edit Event >>' button

Actual:
The set reminders display in hours and are 9 hours out of sync.

Expected:
The set reminders display as they appear on the local calendar.

Environmental Variables:
Device: Buri v1.2 comRIL
BuildID: 20131025004000
Gaia: 606517ceafe0950c2b89822d5f13353743334f2c
Gecko: 5eabd267ef04
Version: 26.0a2
RIL Version: 01.02.00.019.082

Notes:

Repro frequency: 100%
Link to failed test case:
See attached: ReminderLocal.png & ReminderOnline.png
(Reporter)

Comment 1

5 years ago
Created attachment 824272 [details]
Screenshot of PC screen showing reminders as they appear in Google.
This is invalid. Our client side representation of when alarms fire is different than Google's implementation. Our default is at 9am, Google's is at midnight.
Status: NEW → RESOLVED
Last Resolved: 5 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.