-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Web preview overlay hides iframe errors #260
Comments
cc @kittaakos |
Related? eclipse-theia/theia#3589 (comment) |
Well, the CSP error is common, but this bug is about Gitpod hiding any iframe error behind an overlay, while that doesn't seem to happen in Theia itself. |
The overlay that remains visible (hiding iframe errors), only in Gitpod but not in stock Theia, is: <div class="theia-mini-browser-load-indicator" style="display: block;"></div> I'll tentatively look into fixing this, but I don't yet know Theia or its Gitpod Extension very well, so I might end up deferring to you @kittaakos or @AlexTugarev. |
Reading the code, it looks like neither onFrameLoad() nor catch (e) are being called in the case of iframe errors (it's the only two relevant locations that can call EDIT: Likely exception eater is this catch (would make cross-origin security exception disappear). Maybe it should forward the exceptions instead of hiding them? EDIT 2: Actually, that code runs after a |
Here are the various iframe error behaviors in my two browsers: In Firefox (Nightly)
In Chrome
|
In summary, the loading indicator overlay currently hides these iframe errors:
If we remove the loading indicator overlay (either completely, or hide it after a timeout) we'll reveal the above iframe error (except |
Aha, it seems that, in the case of a |
Fixed in eclipse-theia/theia#4399 and deployed. 🎉 |
Describe the bug
When a web preview fails because of some error, an overlay remains visible in the Preview pane, hiding the actual error.
To Reproduce
Expected behavior
The Preview should show the iframe error, instead of the unhelpful grey overlay.
Work around
You can work around this bug by manually deleting the overlay using the browser devtools:
Now you can see the actual error that the iframe encountered, and try to address it.
The text was updated successfully, but these errors were encountered: