Closed
Bug 1288098
Opened 9 years ago
Closed 5 years ago
Per event coloring from Google Calendar is lost on notification.
Categories
(Calendar :: Provider: GData, defect)
Tracking
(Not tracked)
RESOLVED
MOVED
People
(Reporter: nnv, Unassigned)
References
Details
User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/51.0.2704.103 Safari/537.36
Steps to reproduce:
When I dismiss an event reminder from Thunderbird for an event with a non-default color that color is lost from google calendar.
Using Lightning v 4.7.2 (Drop down doesn't contain 4.7.2 so it is set to 4.7.1.1)
Provider for Google Calendar v 2.7
Actual results:
I dismissed an event in Thunderbird with a per event color in google and that coloring was removed.
Expected results:
When dismissing an event in Thunderbird that has a per event color that color should be retained on google.
(Ideally there would be a way to get event coloring from google calendar, but that feature does not appear to be implemented yet. )
Severity: normal → minor
OS: Unspecified → Windows 7
Hardware: Unspecified → x86_64
Updated•9 years ago
|
Version: Lightning 4.7.1.1 → Lightning 4.7.2
Comment 1•8 years ago
|
||
Can you enable calendar.debug.log and calendar.debug.log.verbose in the config editor and then provide the JSON of the event when it is being sent, and ideally also the JSON of the event when it comes from the Google servers (with the per-event coloring)?
Flags: needinfo?(nnv)
Comment 2•6 years ago
|
||
I can confirm this always happens. A straightforward way to replicate it is to add some events in the past in a Google Calendar, and then add it via Provider. You'll get the notifications immediately, and when you dismiss them, the colors of those events will be reset to default in Google Calendar.
The log output for 1 event being dismissed and having its color reset this way is here: https://pastebin.com/YHi2rH7b
Status: UNCONFIRMED → NEW
Ever confirmed: true
Flags: needinfo?(nnv)
Comment 3•5 years ago
|
||
Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → MOVED
Comment 4•5 years ago
|
||
Please update the see-also field with the URL of the new bug in the external tracker.
Updated•5 years ago
|
You need to log in
before you can comment on or make changes to this bug.
Description
•