-
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
Two packages/actual package not working with localhost #36
Comments
alexw10
changed the title
Two packages?
Two packages/actual package not working with localhost?
Jun 5, 2019
alexw10
changed the title
Two packages/actual package not working with localhost?
Two packages/actual package not working with localhost
Jun 5, 2019
You need to use @netbasal/ngx-content-loader |
I confirm @alexw10 report: at least in localhost absolute url doesn't work, changing the url to a relative one makes it work. Not tested in production. |
Nothing changed... and now works 💯 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I am really confused when it comes to the two packages.
These both exist in NPM:
It looks like you published to ngx-content-loader. However, this one does not work for me it seems? but content-loader does.
How I am using it:
It seems like the old one /content-loader for the clip-path has something like
clip-path="url(#uy19jgwmh8a)"
but for the latest version of the ngx-content-loader one it puts in http:// in it like soclip-path="url(https://ngx-content-loader.stackblitz.io/#u5gh7bxo95n)"
<--- did this via stackblitz which your example is not using latest version either by the way.It seems this maybe a localhost issue where the svg is not rendering with localhost?
Seems this issue is related:
#28
I feel like the clip-path can just be the id? not really sure though I do not know much about how this works so hoping you will have more insight.
thoughts on this?
The text was updated successfully, but these errors were encountered: