Closed seanpdoyle closed 8 years ago
The only reason I'm hesitant to add this is because it is a breaking change and will prevent people from getting future bug fixes who have ^2.0.0
in their package.json
I agree, it would certainly require at least a minor version bump, but in what way would previous behavior be "broken".
.svg
files were ignored / unaffected in previous versions, right?
Well someone could explicitly not want svg's to be fingerprinted so I would consider this a major breaking change.
@rickharrison good point.
Is a major version bump anywhere on the horizon, or is this a bonafide Bad Idea :tm: ?
I think it might be a good idea to save this for the next major version. I do have ideas for an internal refactoring to split some things out. I don't have an immediate timeline for that, but its something I'd like to do in the near future.
Relevant: #88
Closing in favor of #88.
Modern browsers now support
svg
as a validbackground-image
value.We should support this out of the box, without additional configuration.