Firefox dislikes clip-path

[Erik Bentsen]

It took me a while to figure this out, haven't found it in the docs, yet:

Firefox stalls for a few seconds when using <clipPath>, enough to make any user experience a royal pain...

However, if I comment out or remove the use of clipPath it behaves nicely. 

So, my svg-map is finally working as intended in all browsers. But according to w3.org the clipping path must be present:

"When an ‘svg’ element is either the root element in the document or is embedded within a document whose layout is determined according to the layout rules of CSS or XSL, then the user agent must establish an initial clipping path for the SVG document fragment."

What do I risk by omitting it?

Has anybody seen a workaround for Firefox?

This happens both on Mac and Win versions of the latest FF release, haven't checked older versions. 

[Rob Crawford]

That says the user agent -- the browser -- must define a clip path, not that the document has to.

(At least, that's how I read it.)

--
You received this message because you are subscribed to the Google Groups "SVG Web" group.
To view this discussion on the web visit https://groups.google.com/d/msg/svg-web/-/6DM9cuZCXWIJ.
To post to this group, send email to svg...@googlegroups.com.
To unsubscribe from this group, send email to svg-web+u...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/svg-web?hl=en.