Closed Bug 823179 Opened 12 years ago Closed 12 years ago

SVG clip-path calculated incorrectly for mouse events

Categories

(Core :: SVG, defect)

defect
Not set
normal

Tracking

()

VERIFIED FIXED
Tracking Status
firefox17 --- affected
firefox18 --- affected
firefox19 --- affected
firefox20 - ---

People

(Reporter: andrew.inscore, Unassigned)

References

Details

(Keywords: regression, testcase)

User Agent: Mozilla/5.0 (X11; Linux i686) AppleWebKit/536.11 (KHTML, like Gecko) Ubuntu/12.04 Chromium/20.0.1132.47 Chrome/20.0.1132.47 Safari/536.11 Steps to reproduce: I created an svg rectangle element with a rectangle clipping path and attached a mouse hover event to the element. http://jsfiddle.net/xVkY3/ Actual results: The element renders correctly, however, the element responds to mouse events as if the clipping path coordinates were applied relative to the rectangle element. So certain visible parts of the element do not respond to mouse events. Expected results: The element should respond to mouse events in its visible area.
Component: Untriaged → SVG
Product: Firefox → Core
Status: UNCONFIRMED → NEW
Ever confirmed: true
I can reproduce on trunk, by hovering the top ~20px of the rect in the jsfiddle. In broken builds, that doesn't change the rect's color. Mozilla/5.0 (X11; Linux x86_64; rv:20.0) Gecko/20121218 Firefox/20.0 Here's the regression range I get from mozregression: { Last good nightly: 2012-08-02 First bad nightly: 2012-08-03 Pushlog: http://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=588424024294&tochange=89dcadd42ec4 } That contained this cset: b077c43a4306 Jonathan Watt — Bug 776054 - Flip the prefs to enable the use of display lists for SVG painting and hit-testing. r=roc. In that range, that's probably the most likely to be responsible. (the hit-testing part in particular is what's involved here)
Blocks: 776054
Hardware: x86 → All
Version: 17 Branch → Trunk
This is in shipping versions of Firefox, and hasn't seen any significant user impact. Please re-nominate for tracking if that isn't in fact the case.
Fixed by bug 820506.
Status: NEW → RESOLVED
Closed: 12 years ago
Depends on: 820506
OS: Linux → All
Resolution: --- → FIXED
Verified fixed in Mozilla/5.0 (X11; Linux x86_64; rv:21.0) Gecko/20130110 Firefox/21.0
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.