White screen and headless mode at the same time
Environment (please complete the following information):
- OS (e.g., Windows 10): Windows 10
- Extension version (e.g., 1.2.3): v2.1.6
Describe the bug:
When i open file with "open with edge"->"open browser" it opens the page but also opens a white screen i have to click out and in the window icon for t to go in the back, but it still there.
Repro steps:
if i open any html file with the option to open with edgeExpected behavior:
someone to tell me how to fix itAdditional context:
Thank you for reporting this issue. I have some follow up questions that might help investigation:
- In the extension settings, what channel are you using? can you try with a different browser flavor/channel (e.g Dev) you might need to install the associated browser version.
- Alternatively you can turn off headleases mode as a workaround
I'm getting the same thing.
I'm experiencing the same issues. I was able to fix by disconnecting debugger call stack, however, problem persist on reloading of edge preview. Moreover, on Initial opening of edge preview the floating control bar is behind the white headless box making it kind of hard to grab or even notice. The headless box also blocks all vs code settings if you've shifted to left aligned GUI.
Edition Windows 11 Home Version 23H2 OS build 22631.4169 Experience Windows Feature Experience Pack 1000.22700.1034.0
Microsoft Edge Tools for VS Code v2.1.6
Anyone hitting this,
You can workaround the issue by doing one of the following:
- In the extension settings, change the channel to Dev or Canary
- OR keep the channel/flavor in Default or Stable but uncheck the headless box in the same settings.
Here's the better workaround I have been using:
In settings.json
{
"vscode-edge-devtools.headless": true,
"vscode-edge-devtools.browserArgs": [
"--headless=old", // Fixes white screen in headless mode
// "--window-position=-2400,-2400", "--headless=new",
// ^ alternate method for the same effect, using new but moving white thing off-screen
]
}
Ideally I want browserArgs and headless args be accepted from the actual debug config. I will send a PR if that helps. 😉
@vidorteg Thanks, found out the actual reason.