Bug 12897 - REGRESSION (r19567): Single Click in "all day event" area creates event with end date before start
Summary: REGRESSION (r19567): Single Click in "all day event" area creates event with ...
Status: RESOLVED FIXED
Alias: None
Product: WebKit
Classification: Unclassified
Component: Evangelism (show other bugs)
Version: 523.x (Safari 3)
Hardware: Mac OS X 10.4
: P2 Normal
Assignee: Nobody
URL: https://www.google.com/calendar/rende...
Keywords: GoogleBug, InRadar, NeedsReduction, Regression
Depends on:
Blocks:
 
Reported: 2007-02-26 09:19 PST by Simon Pride
Modified: 2008-07-28 02:25 PDT (History)
4 users (show)

See Also:

Attachments
Screen shot of invalid all-day event dates (13.01 KB, image/png)
2007-02-26 09:21 PST, Simon Pride 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Simon Pride 2007-02-26 09:19:54 PST 
In Google Calendar Week View you can click once in the blue-shaded 'All Day Event' area to create a new all-day event, the popup shows the end date as being a day before the start date. This, if unnoticed, results in an event that will not display in the calendar. Original Safari/WebKit and Mozilla family browsers do not exhibit this problem with the same page. See attachment for evidence.
Comment 1 Simon Pride 2007-02-26 09:21:32 PST 
Created attachment 13381 [details]
Screen shot of invalid all-day event dates

Screenshot of a popup in Google Calendar showing that a single click in 520+ creates an invalid date range (start > end).  Does not occur in Safari or other browsers.
Comment 2 Alexey Proskuryakov 2007-08-29 03:50:17 PDT 
Confirmed as a regression with r25261.
Comment 3 David Kilzer (:ddkilzer) 2007-08-29 07:06:15 PDT 
<rdar://problem/5446502>
Comment 4 mitz 2007-08-30 13:45:17 PDT 
Rolling out <http://trac.webkit.org/projects/webkit/changeset/19567> fixes the bug.
Comment 5 Antti Koivisto 2007-08-30 18:31:37 PDT 
Spoofing as Firefox fixes the problem. They probably have Safari specific code path that relies on/works around the old behavior.
Comment 6 Alexey Proskuryakov 2008-07-28 02:25:23 PDT 
I can no longer reproduce this, presumably, fixed on Google side.