Closed Bug 1093474 Opened 10 years ago Closed 10 years ago

Default alarm delay no longer applied to new events in Lightning

Categories

(Calendar :: Provider: GData, defect)

Lightning 3.3
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 1083934

People

(Reporter: pithomas, Unassigned)

Details

User Agent: Mozilla/5.0 (X11; Ubuntu; Linux i686; rv:33.0) Gecko/20100101 Firefox/33.0 Build ID: 20141013200110 Steps to reproduce: Create a new event with a double click on date / time, or by clicking on Event button. Actual results: The default alarm delay is no longer applied to the event as it was before (no alarm applied). I missed a rendez-vous because of this bug !! Expected results: The default alarm delay should be automatically applied as defined is Preferences. Note that the default alarm delay is automatically applied when defining an event by dragging the mouse cursor from beginning to end time of the event.
I can't reproduce the issue on Lightning 3.3, here the default alarm setting is applied as expected. What calendars are you using? Are there any error messages in the log (ctrl+shift+j) when reproducing the issue? What add-ons do you have installed and does the issue still exist, if you disable other add-ons?
Bonjour, Thank you for the idea of disabling add-ons, I forgot this possibility. It is Provider for Google Calendar add-on which causes the problem, everything is OK when I disable it. Pierre
What default value do you have configured when using the Google provider? Is this a value, that you also can set via the Google web interface? What about the error messages?
Component: General → Provider: GData
Status: UNCONFIRMED → RESOLVED
Closed: 10 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.