We're calling on all EU-based Mozillians with iOS or iPadOS devices to help us monitor Apple’s new browser choice screens. Join the effort to hold Big Tech to account!

Pesquisar no site de suporte

Evite golpes de suporte. Nunca pedimos que você ligue ou envie uma mensagem de texto para um número de telefone, ou compartilhe informações pessoais. Denuncie atividades suspeitas usando a opção “Denunciar abuso”.

Saiba mais

Esta discussão foi arquivada. Faça uma nova pergunta se precisa de ajuda.

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

  • 4 respostas
  • 11 têm este problema
  • 4 visualizações
  • Última resposta de longsonr

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

Alterado por jakub.oppelt em

Todas as respostas (4)

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.

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.

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.

more options

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