-
Notifications
You must be signed in to change notification settings - Fork 41
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
When using a bad element name, the loading indicator is shown indefinitely instead of the error indicator #74
Comments
Hey @lbilger . I see there's error template has been created and not the loading one: Could you tell me if I'm missing anythig? |
Hi @arturovt, thanks for having a look! I had tried this only in Safari, but now that you said it works for you, I noticed that it works in Chrome but not in Safari. |
Ok, need to find my Mac to try it out in Safari 😄 Will get back to you with info soon! |
@lbilger library, did NOT work with Stackblitz in the past much because of their service worker setup, did that change? |
I saw no other problems and it seems to work in Chrome, but of course it’s a very minimal example. I noticed the problem in my real application, though. Stackblitz seemed the simplest way to create an example to reproduce it. |
Hello, Line 88 in 5b5668b
As this function itself is not throwing an error or has a timeout included, the code gets stuck there. |
I have created an example at https://stackblitz.com/edit/angular-extensions-elements-loading?file=src/app/app.component.html
If the element I am trying to reference is not included in the specified URL, I would expect an error message (as I get when the URL itself is bad), but I get the loading indicator.
The text was updated successfully, but these errors were encountered: