Avatar for Username

Pomoc pśepytaś

Glědajśo se wobšudy pomocy. Njenapominajomy was nigda, telefonowy numer zawołaś, SMS pósłaś abo wósobinske informacije pśeraźiś. Pšosym dajśo suspektnu aktiwitu z pomocu nastajenja „Znjewužywanje k wěsći daś“ k wěsći.

Dalšne informacije

Toś ta nitka jo se archiwěrowała. Pšosym stajśo nowe pšašanje, joli trjebaśo pomoc.

Mouse events do not occur when clip-path (SVG) property is set

  • 4 wótegrona
  • 11 ma toś ten problem
  • 2 naglěda
  • Slědne wótegrono wót longsonr

jakub.oppelt
jakub.oppelt
more options

Hi,

I think i have found bug in Firefox 17:

If SVG shape has set clip-path property mouse events do not occur / fire. It happens only for Firefox 17 (Windows and Mac) Following code works in Firefox 16, Chrome IE9.

See: More system details for code

Thanks for any help

Hi, I think i have found bug in Firefox 17: If SVG shape has set clip-path property mouse events do not occur / fire. It happens only for Firefox 17 (Windows and Mac) Following code works in Firefox 16, Chrome IE9. See: More system details for code Thanks for any help

Wót jakub.oppelt změnjony

Wšykne wótegrona (4)

dlaliberte
dlaliberte
more options

I don't know your particular case, but I learned that my problem was due to the presence of the 'base' tag. Making the clip-path attribute use a full URL, with #sufffix, resolves the problem. However, this breaks for IE9, so people would have to do it conditionally.

dlaliberte
dlaliberte
more options

And another condition is that this problem doesn't apply to all svg elements, at least not 'circle's. It does apply to 'rect's.

cor-el
cor-el
  • Moderator
  • Top 10 Contributor
more options

A good place to ask advice about web development is at the MozillaZine "Web Development/Standards Evangelism" forum.

The helpers at that forum are more knowledgeable about web development issues.
You need to register at the MozillaZine forum site in order to post at that forum.

longsonr
longsonr
more options

Works in Firefox trunk (21) and although I haven't tested it I think this is fixed in Firefox 19.