Bug 16247

Summary: REGRESSION: visibility:hidden style of <a> ignored causing invisible clickable area in picasaweb
Product: WebKit Reporter: Anantha Keesara <anantha>
Component: Layout and RenderingAssignee: Dave Hyatt <hyatt>
Status: RESOLVED FIXED    
Severity: Normal CC: mitz
Priority: P1 Keywords: HasReduction, Regression
Version: 528+ (Nightly build)   
Hardware: PC   
OS: Windows XP   
URL: http://picasaweb.google.com/anantha.keesara/Sunset
Attachments:
Description Flags
Check visibility in RenderBox's nodeAtPoint method adele: review+

Anantha Keesara
Reported 2007-12-02 08:13:08 PST
Steps: 1. got to http://picasaweb.google.com/anantha.keesara/Sunset 2. Click on next image button until the last image is reached. 3. Mouse hover over the grayed out next image button ( > ) Issue: Hovering over the area causes the cursor to change to the link finger as though the image link was actually there. Only Safari has this Issue. All other browsers don't show hand shaped cursor.
Attachments
Check visibility in RenderBox's nodeAtPoint method (734 bytes, patch)
2008-01-08 13:50 PST, Dave Hyatt 		adele: review+
DetailsFormatted DiffDiff
View All Add attachment proposed patch, testcase, etc.
Anantha Keesara
Comment 1 2007-12-02 08:17:45 PST
reduction: http://help.improve.safari.googlepages.com/test.html verified with WebKit-r28278
Dave Hyatt
Comment 2 2007-12-02 19:59:18 PST
This is a severe regression in Safari 3.
Dave Hyatt
Comment 3 2007-12-02 19:59:32 PST
Elevating to P1.
Dave Hyatt
Comment 4 2008-01-08 13:50:36 PST
Created attachment 18334 [details] Check visibility in RenderBox's nodeAtPoint method
Alexey Proskuryakov
Comment 5 2008-01-08 13:57:06 PST
Comment on attachment 18334 [details] Check visibility in RenderBox's nodeAtPoint method Can this be tested for in DRT?
Dave Hyatt
Comment 6 2008-01-08 13:57:49 PST
Yes, it can be tested using elementAtPoint.
Dave Hyatt
Comment 7 2008-01-08 13:58:33 PST
I will add a test case before landing.
Dave Hyatt
Comment 8 2008-01-10 11:30:06 PST
Fixed in r29364.
Note You need to log in before you can comment on or make changes to this bug.