Why hitting a debugger; statement in js code from the preview window also freezes the IDE? Is this the expected behavior?
Yes, websites with iframes run in a single loop. You need to open the preview in a new browser tab to get around that.
Sorry, I don't think we can do anything about it as it is how browsers work.
To open the preview in a browser tab click the icon on the top right.
@akosyakov could you verify?
All windows on the same origin share an event loop as they can synchronously communicate
From http://hassansin.github.io/shared-event-loop-among-same-origin-windows
Because of it, I'm not sure that opening another window will help. It should still use the same event loop if it comes from the same origin.
I think ideally we should run all theia iframes sandboxed somehow, i.e. on different origins, that they don't share event loop and other common state as cookies and local storage.
@akosyakov see last paragraph:
It turns out we can pass an option noopener in window.open()
@AlexTugarev but then we won't be able to communicate with that window? i.e. right now there is no way to detect iframe focus except installing a listener inside iframe and forward them to host window. I hope we will fix it in this way that focus given properly.
So sounds like adding rel=noopener is still missing for our open in browser command?
An issue in upstream: https://github.com/theia-ide/theia/issues/5857
I believe this has been fixed 馃憤.
@Alaboudi1 indeed thanks, good catch! 馃挴
The fix was merged 21 days ago and deployed as a hotfix 16 days ago. 馃帀
I'm hitting this issue today, it doesn't seem fixed?
It was reintroduced lately by some changes we made in Theia. Thanks for the PR you provided, we will put it into production ASAP.
In production now