RESOLVED INVALID 11357
Google Calendar: events with web content render behind the calendar grid instead of in front of it 
https://bugs.webkit.org/show_bug.cgi?id=11357
Summary Google Calendar: events with web content render behind the calendar grid inst...
mitz
Reported 2006-10-19 08:55:24 PDT
To reproduce this bug: 1. Log in to Google Calendar 2. Go to Manage Calendars and click Add Calendar 3. Choose the Browse Calendars tab and add the Google Holiday Logos calendar 4. Go to the week of October 9, 2006 5. Click the icon at the top of the Monday column Expected result: The logo popup should render in front of the calendar gridlines. Actual result: The logo popup renders behind the calendar gridlines. See attached screenshots. Behavior is the same in shipping Safari.
Attachments
TOT WebKit rendering (47.22 KB, image/png)
2006-10-19 08:56 PDT, mitz 		no flags
Details
Firefox rendering (46.42 KB, image/png)
2006-10-19 08:56 PDT, mitz 		no flags
Details
Reduction (274 bytes, text/html)
2006-10-20 15:42 PDT, mitz 		no flags
Details
View All Add attachment proposed patch, testcase, etc.
mitz
Comment 1 2006-10-19 08:56:00 PDT
Created attachment 11147 [details] TOT WebKit rendering
mitz
Comment 2 2006-10-19 08:56:45 PDT
Created attachment 11148 [details] Firefox rendering
mitz
Comment 3 2006-10-19 08:57:25 PDT
Note that WebKit also gets the positioning of the icon wrong (too low).
mitz
Comment 4 2006-10-20 15:42:05 PDT
Created attachment 11170 [details] Reduction Firefox renders a green square. WebKit and Opera render a red square (and Opera's rendering of Google calendar also has the grid overlaying the image).
mitz
Comment 5 2006-10-20 15:46:33 PDT
As a workaround, Google can add "z-index: 1" to the style attribute of the "wc" div.
Dave Hyatt
Comment 6 2006-10-20 15:47:46 PDT
The reduction is a bug in Firefox I believe.
Dave Hyatt
Comment 7 2006-10-20 15:48:26 PDT
Pretty sure WebKit's rendering is right. :)
mitz
Comment 8 2007-03-31 08:29:26 PDT
Google fixed it a while ago. Closing based on comment #6 and comment #7.
Note You need to log in before you can comment on or make changes to this bug.