Using Lightning 1.0b3pre with Lanikai 3.1.8pre from today. Creating a new event now requires more clicks compared to previous Sunbird and Lightning releases. This is probably caused by the change for Bug 366139. Steps to Reproduce: 1) Start creating new event 2) Set start date and time 3) Set end date and time 4) Save event Actual Results: This are the same steps used in previous Sunbird and Lightning releases as well as other calendar software I tested. But the event did not saved as specified because after step 3 the start date is suddenly changed without notice. One has to reopen the event, disable the link icon, reset start/end date/time and save again. Expected Results: In my opinion a new features should make it easier for users. But now it is actually more complicated to create the event. The default behavior should match the easier behavior known from previous releases. Otherwise I expect a lot of support request, bug reports and similar until you told every user to always disable the link icon when creating event.
(In reply to comment #0) > This are the same steps used in previous Sunbird and Lightning releases as well > as other calendar software I tested. But the event did not saved as specified > because after step 3 the start date is suddenly changed without notice. Might it help to set a default "unlinked" status for the button? In this way the workflow would be the same immediately at the first run of Lightning and, at the same time, the user is noticed about the interface's behavior by the the icon on the button (instead before no element noticed the user that when he changed the start date, the end date changed too (bug 366139). However the button keeps the status between different new events and between sessions so the user can choose his preferred behavior and change it only when it needs.
Status: UNCONFIRMED → NEW
Ever confirmed: true
The default status of the keep-duration button has been changed with patches for bug 366139 in order to restore the previous behavior and fixing this bug.
Status: NEW → RESOLVED
Last Resolved: 6 years ago
Resolution: --- → FIXED
Target Milestone: --- → 1.0b3
You need to log in before you can comment on or make changes to this bug.