Closed Bug 327311 Opened 19 years ago Closed 19 years ago

Crash if bad data input in date fields

Categories

(Calendar :: Internal Components, defect)

x86
Windows XP
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 278236

People

(Reporter: iversone, Unassigned)

Details

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.0.1) Gecko/20060111 Firefox/1.5.0.1 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9a1) Gecko/20060208 Mozilla Sunbird/0.3a1+ When events and tasks are input, if bad data is put in for the date, Mozilla crashes and/or changes the date to something completely different. Reproducible: Always Steps to Reproduce: 1 -- Create a task or event 2 -- Enter a date with decimals, such as 2.1/4.2/2007.9 Actual Results: Crash and/or date changed to something completely different. Expected Results: Tell the user the date is malformed and have them re-input.
From a quick test: If you enter something invalid the datepicker tries to interprete these as valid values resulting in changed dates. If you end up with a date after 2037 or before 1970 it crashes. For this crash we already have bugs filed (see Bug 324293, Bug 278236).
(In reply to comment #1) > From a quick test: If you enter something invalid the datepicker tries to > interprete these as valid values resulting in changed dates. If you end up with > a date after 2037 or before 1970 it crashes. For this crash we already have > bugs filed (see Bug 324293, Bug 278236). > I agree that this is the correct analysis, resolving as a duplicate. *** This bug has been marked as a duplicate of 278236 ***
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → DUPLICATE
The bugspam monkeys have struck again. They are currently chewing on default assignees for Calendar. Be afraid for your sanity!
Assignee: base → nobody
You need to log in before you can comment on or make changes to this bug.