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

Menus do not work on Windows 10 build 15025.rs_prerelease #19698

Closed
djensen47 opened this Issue Feb 1, 2017 · 21 comments

Comments

Projects
None yet
10 participants
@djensen47

djensen47 commented Feb 1, 2017

  • VSCode Version: I don't know because I can't open the menus
  • OS Version: Windows 10 build 15025.rs_prerelease

Steps to Reproduce:

  1. Install WIndows 10 15025.rs_prerelease
  2. Click on File, Edit, Selection, View, Go, Help (or try keyboard shortcuts)

Expected result: menu opens
Actual result; the menu doesn't open or the menu is not visible

@bpasero

This comment has been minimized.

Show comment
Hide comment
@bpasero

bpasero Feb 2, 2017

Member

@djensen47 that is weird!
Can you try to reproduce with our nightly insider builds? You can give our preview releases a try from: http://code.visualstudio.com/Download#insiders

Member

bpasero commented Feb 2, 2017

@djensen47 that is weird!
Can you try to reproduce with our nightly insider builds? You can give our preview releases a try from: http://code.visualstudio.com/Download#insiders

@be5invis

This comment has been minimized.

Show comment
Hide comment
Member

be5invis commented Feb 2, 2017

@dragonJACson

This comment has been minimized.

Show comment
Hide comment
@dragonJACson

dragonJACson Feb 2, 2017

When I click the invisible menu, it actually worked,but I can only see the program but not the menu. AKA, menu exists there, but the program is like ghost.

dragonJACson commented Feb 2, 2017

When I click the invisible menu, it actually worked,but I can only see the program but not the menu. AKA, menu exists there, but the program is like ghost.

@bpasero

This comment has been minimized.

Show comment
Hide comment
@bpasero

bpasero Feb 2, 2017

Member

This sounds like a Windows bug to me with a pre-release version of Windows 10

Member

bpasero commented Feb 2, 2017

This sounds like a Windows bug to me with a pre-release version of Windows 10

@bpasero bpasero added the upstream label Feb 2, 2017

@djensen47

This comment has been minimized.

Show comment
Hide comment
@djensen47

djensen47 Feb 2, 2017

djensen47 commented Feb 2, 2017

@be5invis

This comment has been minimized.

Show comment
Hide comment
@be5invis

be5invis Feb 2, 2017

Member

@gongminmin ← WDG DWM guy

Member

be5invis commented Feb 2, 2017

@gongminmin ← WDG DWM guy

@Rhywden

This comment has been minimized.

Show comment
Hide comment
@Rhywden

Rhywden Feb 3, 2017

@bpasero Can confirm that the issue still exists with the insider build I just downloaded.

Rhywden commented Feb 3, 2017

@bpasero Can confirm that the issue still exists with the insider build I just downloaded.

@Rhywden

This comment has been minimized.

Show comment
Hide comment
@Rhywden

Rhywden Feb 3, 2017

@bpasero However, here's the weird thing I just discovered: My desktop does not have this issue, only my Surface Book.

Even though both are on the same Windows Insider build.

Rhywden commented Feb 3, 2017

@bpasero However, here's the weird thing I just discovered: My desktop does not have this issue, only my Surface Book.

Even though both are on the same Windows Insider build.

@Rhywden

This comment has been minimized.

Show comment
Hide comment
@Rhywden

Rhywden Feb 3, 2017

Okay, I found the source of the issue - it's the DPI scaling. If it's set to 200% or above (which is the default for a Surface Book with its 3000 by 2000 resolution) then I don't see the menus. If I set the scaling to anything below 200% (i.e. 175% to 100%) then it works normally again.

Rhywden commented Feb 3, 2017

Okay, I found the source of the issue - it's the DPI scaling. If it's set to 200% or above (which is the default for a Surface Book with its 3000 by 2000 resolution) then I don't see the menus. If I set the scaling to anything below 200% (i.e. 175% to 100%) then it works normally again.

@gongminmin

This comment has been minimized.

Show comment
Hide comment
@gongminmin

gongminmin Feb 4, 2017

Found something more interesting.

  1. Only repro when DPI is 200%, not 175% nor 225%.
  2. Not only VSCode's menu get occluded, but also other menus, such as the menu popup when right-click on desktop.
  3. In screen print, it looks right.

gongminmin commented Feb 4, 2017

Found something more interesting.

  1. Only repro when DPI is 200%, not 175% nor 225%.
  2. Not only VSCode's menu get occluded, but also other menus, such as the menu popup when right-click on desktop.
  3. In screen print, it looks right.
@zhengbli

This comment has been minimized.

Show comment
Hide comment
@zhengbli

zhengbli Feb 4, 2017

Have issues with %250 as well. Sometimes the right-click menu does not show up on this build.
Happens for Chrome as well.

zhengbli commented Feb 4, 2017

Have issues with %250 as well. Sometimes the right-click menu does not show up on this build.
Happens for Chrome as well.

@EternalPhane

This comment has been minimized.

Show comment
Hide comment
@EternalPhane

EternalPhane Feb 4, 2017

mine's %125, but the menu still hides behind the window (= =)
seems to be related with both dpi and resolution

EternalPhane commented Feb 4, 2017

mine's %125, but the menu still hides behind the window (= =)
seems to be related with both dpi and resolution

@danieldjordan

This comment has been minimized.

Show comment
Hide comment
@danieldjordan

danieldjordan Feb 6, 2017

Same Issue.
Resolution: 3200x1800
DPI Scaling: 175%
Windows Version: 15025.rs_prerelease
VS.Code Version: 1.10.0-insider

Taking a screenshot brings the menu in front of the app.

danieldjordan commented Feb 6, 2017

Same Issue.
Resolution: 3200x1800
DPI Scaling: 175%
Windows Version: 15025.rs_prerelease
VS.Code Version: 1.10.0-insider

Taking a screenshot brings the menu in front of the app.

@djensen47

This comment has been minimized.

Show comment
Hide comment
@djensen47

djensen47 Feb 8, 2017

There's a new Windows Insider Fast Ring build. Has anybody tried 15031 yet? Is the issue still there?

djensen47 commented Feb 8, 2017

There's a new Windows Insider Fast Ring build. Has anybody tried 15031 yet? Is the issue still there?

@gongminmin

This comment has been minimized.

Show comment
Hide comment
@gongminmin

gongminmin Feb 9, 2017

Tried on 15032, no repro anymore.

gongminmin commented Feb 9, 2017

Tried on 15032, no repro anymore.

@madcampos

This comment has been minimized.

Show comment
Hide comment
@madcampos

madcampos Feb 9, 2017

Same here.
Surface book, with windows build 15025 and scaling of 200%.
It's known that there is problems with this build and scaling.
Tested on version 1.9 of vscode, the prior version (1.8.1) worked as expected in the same windows build.
Insiders build don't work either.

madcampos commented Feb 9, 2017

Same here.
Surface book, with windows build 15025 and scaling of 200%.
It's known that there is problems with this build and scaling.
Tested on version 1.9 of vscode, the prior version (1.8.1) worked as expected in the same windows build.
Insiders build don't work either.

@djensen47

This comment has been minimized.

Show comment
Hide comment
@djensen47

djensen47 Feb 9, 2017

@gongminmin
Tried on 15032, no repro anymore.

Do you mean to say that the issue is resolved in 15032?

djensen47 commented Feb 9, 2017

@gongminmin
Tried on 15032, no repro anymore.

Do you mean to say that the issue is resolved in 15032?

@zhengbli

This comment has been minimized.

Show comment
Hide comment
@zhengbli

zhengbli Feb 9, 2017

Nope, on 15033 even, still see this.

zhengbli commented Feb 9, 2017

Nope, on 15033 even, still see this.

@zhengbli

This comment has been minimized.

Show comment
Hide comment
@zhengbli

zhengbli Feb 11, 2017

Seems fixed in an internal build 15035. So the fix should be available for next insider build I think

zhengbli commented Feb 11, 2017

Seems fixed in an internal build 15035. So the fix should be available for next insider build I think

@bpasero

This comment has been minimized.

Show comment
Hide comment
@bpasero

bpasero Feb 20, 2017

Member

Ok thanks.

Member

bpasero commented Feb 20, 2017

Ok thanks.

@bpasero bpasero closed this Feb 20, 2017

@vscodebot vscodebot bot locked and limited conversation to collaborators Nov 18, 2017

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.