Bug 12897

Summary: REGRESSION (r19567): Single Click in "all day event" area creates event with end date before start
Product: WebKit Reporter: Simon Pride <simon.pride>
Component: EvangelismAssignee: Nobody <webkit-unassigned>
Status: RESOLVED FIXED    
Severity: Normal CC: abob, ap, koivisto, mitz
Priority: P2 Keywords: GoogleBug, InRadar, NeedsReduction, Regression
Version: 523.x (Safari 3)   
Hardware: Mac   
OS: OS X 10.4   
URL: https://www.google.com/calendar/render?pli=1
Attachments:
Description Flags
Screen shot of invalid all-day event dates none

Simon Pride
Reported 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.
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 attachment proposed patch, testcase, etc.
Simon Pride
Comment 1 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.
Alexey Proskuryakov
Comment 2 2007-08-29 03:50:17 PDT
Confirmed as a regression with r25261.
David Kilzer (:ddkilzer)
Comment 3 2007-08-29 07:06:15 PDT
<rdar://problem/5446502>
mitz
Comment 4 2007-08-30 13:45:17 PDT
Rolling out <http://trac.webkit.org/projects/webkit/changeset/19567> fixes the bug.
Antti Koivisto
Comment 5 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.
Alexey Proskuryakov
Comment 6 2008-07-28 02:25:23 PDT
I can no longer reproduce this, presumably, fixed on Google side.
Note You need to log in before you can comment on or make changes to this bug.