-
Notifications
You must be signed in to change notification settings - Fork 16.2k
fix: WCO occlusion of DevTools #35209
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
Conversation
2743e4f
to
fac1fb9
Compare
fac1fb9
to
f35390b
Compare
Release Notes Persisted
|
I have automatically backported this PR to "18-x-y", please check out #35307 |
I have automatically backported this PR to "19-x-y", please check out #35308 |
I have automatically backported this PR to "20-x-y", please check out #35309 |
/trop run backport-to 21-x-y |
The backport process for this PR has been manually initiated - sending your PR to |
I have automatically backported this PR to "21-x-y", please check out #35688 |
So when the user manually dock the devtool to the right side, it would still be occluded (see microsoft/vscode#168454 (comment)). Is there any plan to actually fix this? |
Description of Change
Closes #34129.
This change matches Chromium behavior for WCO by opening DevTools in detached mode if WCO is enabled.
This prevents the DevTools from being occluded and becoming semi-unusable.
Before
After
Checklist
npm test
passesRelease Notes
Notes: Fixed an issue where WCO could occlude DevTools opened in any non-detached mode.