Closed
Bug 226716
Opened 22 years ago
Closed 21 years ago
bad calendar events are accepted: end preceeds start
Categories
(Calendar :: General, defect)
Tracking
(Not tracked)
RESOLVED
WORKSFORME
People
(Reporter: olleo, Assigned: mostafah)
Details
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.5) Gecko/20031007
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.5) Gecko/20031007
calendar events are defined by start and end times. When interactively creating
events, some UI-functionality steps in to say something like "yo cannot have end
preceed start". But in the ICS file I have found several occurrences of bad
start/end. And then when I look in the UI edit-event I see that indeed the times
are ordered badly. "start: 11/10 and: 9/8". If it is impossible to manually
enter badly sequenced dates, there should be something that announces to the
user that "Hey there is a problem with this event. Please fix it".
Reproducible: Couldn't Reproduce
Steps to Reproduce:
1.
2.
3.
To be clear: yes I use the ICS file as input to other workflow. But I do not
make changes to the ICS file except through the Calendar interface.
I could not reproduce the problem. Every time I tried to enter an event with
an end date occuring before the start date, or with the end time occuring
before the start time (in the case of an event on one day), I always get a
warning from the UI and it will not let me save the event.
How did these "bad" events get into the calendar in question in the first
place? Are they from a remote database entered by someone else uing some other
UI that allows the date/time issue?
Comment 2•21 years ago
|
||
This bug is invalid/fixed/worksforme.
Comment 3•21 years ago
|
||
Filed as WORKSFORME
Status: UNCONFIRMED → RESOLVED
Closed: 21 years ago
Resolution: --- → WORKSFORME
Comment 4•20 years ago
|
||
The bugspam monkeys have been set free and are feeding on Calendar :: General. Be afraid for your sanity!
QA Contact: gurganbl → general
You need to log in
before you can comment on or make changes to this bug.
Description
•