Fungovanie tejto stránky je z dôvodu údržby dočasne obmedzené. Ak článok nevyrieši váš problém a chcete položiť otázku, napíšte našej komunite podpory na Twitter @FirefoxSupport alebo Reddit /r/firefox.

Vyhľadajte odpoveď

Vyhnite sa podvodom s podporou. Nikdy vás nebudeme žiadať, aby ste zavolali alebo poslali SMS na telefónne číslo alebo zdieľali osobné informácie. Nahláste prosím podozrivú aktivitu použitím voľby “Nahlásiť zneužitie”.

Ďalšie informácie

Firefox is very slow with masking images and animations in general.

  • 1 odpoveď
  • 1 má tento problém
  • 4 zobrazenia
  • Posledná odpoveď od user1929

more options

I am using animation on SVG elements (only paths) (Just by toggling the visibility property of paths very frequently with JavaScript). The SVG has a background image. Some of the paths that are displayed must have the background image on the stroke (to appear as if they are erasing paths). I use the masking capability of SVG to do this.

There are too many paths with or without background image on the stroke. This works well in Chrome. However, in FireFox, the animation process becomes very slow while displaying an erasing path (i.e a path with the background image on the stroke). Is there any other way to display an erasing path to which Firefox responds well.

I am using animation on SVG elements (only paths) (Just by toggling the visibility property of paths very frequently with JavaScript). The SVG has a background image. Some of the paths that are displayed must have the background image on the stroke (to appear as if they are erasing paths). I use the masking capability of SVG to do this. There are too many paths with or without background image on the stroke. This works well in Chrome. However, in FireFox, the animation process becomes very slow while displaying an erasing path (i.e a path with the background image on the stroke). Is there any other way to display an erasing path to which Firefox responds well.

Všetky odpovede (1)

more options

If you have an example page that does this, could you open a bug report at https://bugzilla.mozilla.org/ ?