You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As it is a proper built-in extension and uses the rendering engine already embedded inside electron it does not suffer from the problems of the current screensharing architecture. This will likely resolve every issue listed above!
Alternative
Fix vscode-browse-lite, though I do not consider this worth the effort given the limitations of it architecture.
Additional context
The only drawback will be that devtools will be a bit less nice. One has to use the electron devtools (Help > Toggle Developer Tools) which are not in a nice tab like the current ones. However, I definitely consider this drawback justified given the amount of advantages this switch would bring.
Furthermore, one can still open it in an external browser if some parts of the devtools are limiting inside VSCode.
Clear and concise description of the problem
Currently there is a plethora of bugs with the embedded browser. It...
Remote-SSH
andRemote-Container
vscode-browse-lite#32),<select>
dropdown (Embedded browser <select> doesn't dropdown #24),vscode://
URIs (Unable to accessvscode:
URIs in<a>
elements vscode-browse-lite#19),Enter-Key
behavior bug vscode-browse-lite#2),Suggested solution
VSCode has a built-in "Simple browser" extension since a while ago: microsoft/vscode#109276
As it is a proper built-in extension and uses the rendering engine already embedded inside electron it does not suffer from the problems of the current screensharing architecture. This will likely resolve every issue listed above!
Alternative
Fix
vscode-browse-lite
, though I do not consider this worth the effort given the limitations of it architecture.Additional context
The only drawback will be that devtools will be a bit less nice. One has to use the electron devtools (Help > Toggle Developer Tools) which are not in a nice tab like the current ones. However, I definitely consider this drawback justified given the amount of advantages this switch would bring.
Furthermore, one can still open it in an external browser if some parts of the devtools are limiting inside VSCode.
Validations
The text was updated successfully, but these errors were encountered: