Bug 81584 - [SVG] click events on objects below 1 unit of width ignored
Summary: [SVG] click events on objects below 1 unit of width ignored
Status: RESOLVED INVALID
Alias: None
Product: WebKit
Classification: Unclassified
Component: SVG (show other bugs)
Version: 528+ (Nightly build)
Hardware: All All
: P2 Normal
Assignee: Nobody
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-03-19 16:13 PDT by Eric U.
Modified: 2012-03-26 17:10 PDT (History)
3 users (show)

See Also:


Attachments
repro case (1.41 KB, text/html)
2012-03-19 16:13 PDT, Eric U.
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Eric U. 2012-03-19 16:13:48 PDT
Created attachment 132702 [details]
repro case

I logged this as a Chrome bug first, but it turns out to be broken in Safari as well, albeit differently.

See http://code.google.com/p/chromium/issues/detail?id=118108 for the Chrome bug.

What steps will reproduce the problem?
1. Load the attached file.
2. Open the debug console.
3. Click on black shapes on the left and on the right.

What is the expected output? What do you see instead?

You should get a message in the log for every click on a black shape.

In Chrome 18 on Linux or Windows, the black shapes of the left-hand SVG region never respond.
In Safari 5.1.4 for Windows, clicking either on the black shapes or in the white area results in a click event.
Firefox on Linux reacts to clicks on black or /some/ of the white.
Nobody gets it right.
Comment 1 Eric U. 2012-03-19 16:16:04 PDT
I forgot to mention that the only difference between left and right is the scaling.  The left-hand shapes are all < 1.0 units in size, and I've tweaked the viewbox so that they look the same as the ones on the right, which are 10x as big.  1.0 seems to be the magic cutoff point where click/mousedown/etc. events start working.
Comment 2 Dirk Schulze 2012-03-19 19:56:30 PDT
Please also check nightly builds. This was fixed several weeks ago.
Comment 3 Eric U. 2012-03-26 17:10:55 PDT
*** Bug 81980 has been marked as a duplicate of this bug. ***