npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

ff-svg-path-pushstate-workaround

v1.0.4

Published

FF SVG patterns path issue workaround

Downloads

2

Readme

FF-SVG-path-pushState-workaround

Brutal workaround for FF issue #652991

May be useful for SPA who rely on SVG patterns url(#...) and history.pushState. Having this stack you may noticed FF adds none; to the end of fill/stroke paths after changing route, causing SVG paths to break.

This workaround should refresh pattern paths on route change, whereby SVG won't break.

It does not observe window.onpopstate event so you have to call it manually once route changes.

Demo without fix Take a look at Firefox

Demo with fix

Usage

import fixSVGPathsFF from 'ff-svg-path-pushstate-workaround'

or 

var fixSVGPathsFF = require('ff-svg-path-pushstate-workaround')

or

var fixSVGPathsFF = window.ffSvgPathPushstateWorkaround

// at some point when route changes
fixSVGPathsFF()

By default it will lookup for all tags containing pattern in stroke or fill attributes. document.querySelectorAll([fill^="url(#"], [stroke^="url(#"])

You may change it to fit your needs by passing custom selector as optional argument fixSVGPathsFF('path') // will affect all path tags

P.s. Please note that default selector would search only fill/stroke specified by attributes. It won't find its parameters specified by styles, so you have to specify selector that will suit your needs, as mentioned above. (For example 'path' worked for me because on my project only path tags were used and all stroke/path parameters were specified by styles)

As example of usage with react-router

// yes, this should be called on every route change
const fixSVGPatternPathsInFF = () => {
    fixSVGPathsFF('path')
}

<Route path='/' component={App}>
    <Route path='profile' component={Profile} onEnter={fixSVGPatternPathsInFF} />
    ...
</Route>

MIT