Closed notchris closed 2 months ago
Hey @notchris, thanks for reaching out.
I opened the first example, the simple auto complete and it seems to work fine on my end.
Do you get any errors in your (Chrome) DevTools? If the autocomplete works for you as well, let me know which one always fails for you?
We resolved an issue yesterday where WebContainer didn't seem to boot. This issue should be resolved now. I'm wondering if that was the one you where running into.
Can you try again and let us know if it's fixed?
@SamVerschueren Simple example:
My coworker has confirmed that they ran into the same issue, is this possibly a firewall issue?
@SamVerschueren So turns out, it's something internally. Something at work is preventing the fetch call from resolving because of the stackblitz-protocol urls. "URL scheme "stackblitz" is not supported."
With some more investigation, we found that it works in Edge, but not Chrome. There is also another open issue related to this.
@SamVerschueren Any ideas on how to resolve the URL Scheme issue?
@SamVerschueren This is now resolved! The issue is that StackBlitz will only work on 64bit Chrome (everyone at work was on 32bit) - and updating Chrome doesn't change between 32/64.
Describe the bug
Whenever I try to view an Stackblitz at work or at home, it almost never loads. I'm trying most of the examples on Angular Material and cant get them to load. I have multiple machines with Windows, OSX. Why doesn't Stackblitz work for every project and resolve every module correctly?
Link to the blitz that caused the error
https://material.angular.io/components/categories
Steps to reproduce
Go to any Stackblitz
Expected behavior
It should wor
Parity with Local
Screenshots
No response
Platform
Additional context
No response