-
Notifications
You must be signed in to change notification settings - Fork 58
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Issue with window.location.pathname #52
Comments
Thanks. You're welcome to submit a PR. |
+1 |
@NetanelBasal, I could be wrong but it doesn't look like baseUrl is needed in the fill and clip path. Removing seems to work the same and it fixes the bug. I tested in safari too, since @timminss mentioned that. |
Try to check in previous issues why we added it. |
Oh! My mistake |
@Steven-Harris try to see if the React version made some updates we can use here. |
Dang... They are doing something similar. The default is empty instead of
|
I've updated the library to the same code as the original React one. It should work now. |
Thanks for the fantastic library! I came across an issue with it, and hopefully the below provides a solution too:
I'm submitting a...
Current behavior
When using queryParams in an Angular project, window.location.pathname is not sufficient to determine the URL. SVGs appear black in Safari as a result.
Expected behavior
SVGs should display as normal in Safari, even when using queryParams.
Minimal reproduction of the problem with instructions
A new Angular project, with content-loader installed, and a single route. Add a queryParameter to the end of the URL, and the SVG will no longer load.
What is the motivation / use case for changing the behavior?
Fix a bug
Environment
The text was updated successfully, but these errors were encountered: