Bug 81151

Summary: getIntersectionList incorrectly takes into account padding on ancestor DOM elements.
Product: WebKit Reporter: Oscar Kozlowski <okozlo>
Component: SVGAssignee: Nobody <webkit-unassigned>
Status: NEW    
Severity: Normal CC: ahmad.saleem792, dtrebbien, mmaxfield, sabouhallawa, simon.fraser, webkit-bug-importer, zalan, zimmermann
Priority: P2 Keywords: BrowserCompat, InRadar
Version: 528+ (Nightly build)   
Hardware: PC   
OS: Windows 7   
Attachments:
Description Flags
Repro case none

Oscar Kozlowski
Reported 2012-03-14 13:36:57 PDT
Created attachment 131912 [details] Repro case getIntersectionList appears take into account any padding that has been applied to ancestor DOM elements. Steps to reproduce: 1. Open attached mininmal repro (svg_getIntersectionList_padding_bug.svg). This repro attaches a mouse move handler that retrieves the intersected SVG elements directly under the pointer. If the rectangle is intersected, it is highlighted red, otherwise it is green. 2. Move mouse over the green rectangle. Expect rectangle to highlight red, but remains green. 3. Move mouse to screen position (200, 0). Rectangle is now highlighted red when it should not be. Correct behaviour under IE9 and Opera.
Attachments
Repro case (1.50 KB, text/html)
2012-03-14 13:36 PDT, Oscar Kozlowski 		no flags
Details
View All Add attachment proposed patch, testcase, etc.
Ahmad Saleem
Comment 1 2022-05-30 05:24:54 PDT
I am able to reproduce the following bug in Safari 15.5 on macOS 12.4 and it is also broken in Firefox Nightly 102. On hover, the green box does not change to "red" for Firefox and Safari but it works with Chrome Canary 104. Thanks!
Radar WebKit Bug Importer
Comment 2 2022-05-31 10:21:54 PDT
<rdar://problem/94161043>
Ahmad Saleem
Comment 3 2023-05-12 02:37:29 PDT
(In reply to Ahmad Saleem from comment #1) > I am able to reproduce the following bug in Safari 15.5 on macOS 12.4 and it > is also broken in Firefox Nightly 102. On hover, the green box does not > change to "red" for Firefox and Safari but it works with Chrome Canary 104. > > Thanks! Now Chrome Canary 115 works fine while Safari 16.4.1 is still broken.
Note You need to log in before you can comment on or make changes to this bug.