1021833 - [B2G][Calendar] Google event notifications are firing at correct time but displaying incorrect time

Status: RESOLVED WONTFIX

(Firefox OS Graveyard :: Gaia::Calendar, defect)

Description

[bmorgan]

Attachment: logcat buri 2-0.txt

Description:
When importing a Google calendar event with alarms set by hours, the event details page displays the correct alarm, and the alarm fires at the correct interval, but the notification displays the alarm as one hour previous. (ie. Instead of the notification saying "Event starting [n] hours" it says "Event starting in [n-1] hours".)


Repro Steps:
1) Update a Flame to 20140606040202
2) Create an event with a 6-hour alarm in Google calendar through a PC.
3) On the DUT; open the Calendar app, tap on the Drawer in the upper left corner, tap on the Settings gear, and add the Google account that the event was created under.
4) Close the drawer by tapping the icon in the upper left corner again and navigate to the imported event.  Click the event and observe alarm is displayed as 6 hours.
5) When alarm is fired, observe notification saying that event will start in 5 hours.


Actual:
Notification displays event starting in [alarm-1] hours


Expected:
Notification displays event starting in [alarm] hours

Environmental Variables:
Device: Flame 2.0
Build ID: 20140606040202
Gaia: 857129928b6e56a809cee9d5445effb8fa9f1c2c
Gecko: c8288d0c7a15
Version: 32.0a1 (2.0) MOZ
Firmware Version: v10G-2

User Agent: Mozilla/5.0 (Mobile; rv:32.0) Gecko/32.0 Firefox/32.0


Notes: This applies to any alarm set in hours, not just 6 hours


Repro frequency: 100%
Link to failed test case: https://moztrap.mozilla.org/manage/case/7542/
See attached: logcat

Flame logcat issue: https://bugzilla.mozilla.org/show_bug.cgi?id=1010993

Comment 1

[bmorgan]

Attachment: screenshot of notification vs event details

Event notifications for imported Google events fire at the correct time but are displayed as [n-1] hours on the Buri 2.0 MOZ RIL

2.0 Environmental Variables:
Device: Buri 2.0 MOZ
BuildID: 20140530040207
Gaia: 26d8fcab9b61f46451600f39c51e0387ef3c4f88
Gecko: e6f113c83095
Version: 32.0a1
Firmware Version: v1.2-device.cfg

My User Agent: Mozilla/5.0 (Mobile; rv:32.0) Gecko/32.0 Firefox/32.0


Event notifications for imported Google events fire at the correct time but are displayed as [n-1] hours on the Buri 1.4 MOZ RIL

1.4 Environmental Variables:
Device: Buri 1.4 MOZ
BuildID: 20140530000202
Gaia: fe612fd21389193a8e593aa718831602e5086a62
Gecko: 25011f9a8f26
Version: 30.0
Firmware Version: v1.2-device.cfg

My User Agent: Mozilla/5.0 (Mobile; rv:30.0) Gecko/30.0 Firefox/30.0


Event notifications for imported Google events fire at the correct time but are displayed as [n-1] hours on the Buri 1.3 MOZ RIL

1.3 Environmental Variables:
Device: Buri 1.3 MOZ
BuildID: 20140530024008
Gaia: 5bd226b03a2d63dfe9df204f7c0afb9984e8fd42
Gecko: 57cd741e4d0b
Version: 28.0
Firmware Version: v1.2-device.cfg

My User Agent: Mozilla/5.0 (Mobile; rv:28.0) Gecko/28.0 Firefox/28.0

Comment 2

[Miller Medeiros [:millermedeiros]]

this is probably related to the way the `navigator.mozL10n.DateTimeFormat.fromNow` works. I thought that Bug 987427 would be enough to fix the error on most common cases but it seems that in this specific scenario the logic is a little bit different (rounding error probably isn't just of a few ms)..

maybe we will need to replace the whole rounding logic or just display the event time instead - which is way simpler and avoids mistakes (eg: "Foo Bar starts 06/06/2014 5:00 PM" instead of "Foo Bar starting in 5 hours") specially since the notification doesn't update after it's created, so the relative time doesn't work well if user only sees it after a few minutes/hours/days.

Comment 3

[BMO Automation]

Firefox OS is not being worked on