Skip to content
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

Refactor menu's css seems missing #198881

Closed
fourdim opened this issue Nov 22, 2023 · 9 comments
Closed

Refactor menu's css seems missing #198881

fourdim opened this issue Nov 22, 2023 · 9 comments
Assignees
Labels
bug Issue identified by VS Code Team member as probable bug candidate Issue identified as probable candidate for fixing in the next release confirmed Issue has been confirmed by VS Code Team member editor-code-actions Editor inplace actions (Ctrl + .) regression Something that used to work is now broken verified Verification succeeded

Comments

@fourdim
Copy link

fourdim commented Nov 22, 2023

Does this issue occur when all extensions are disabled?: Yes, but with vscode-remote enabled.

  • Version: 1.85.0-insider (user setup)
  • Commit: 05cd264
  • Date: 2023-11-21T05:35:09.651Z
  • Electron: 25.9.4
  • ElectronBuildId: 25127168
  • Chromium: 114.0.5735.289
  • Node.js: 18.15.0
  • V8: 11.4.183.29-electron.0
  • OS: Windows_NT x64 10.0.19045
  • Remote-SSH: v0.107.0

Steps to Reproduce:

  1. Create a typescript file.
  2. Select a function and click on refactor.

image

@gjsjohnmurray
Copy link
Contributor

Do you still get this after you update to the newest Insiders?

@fourdim
Copy link
Author

fourdim commented Nov 22, 2023

Yeah, the bug is still there.
The latest insider:

  • Version: 1.85.0-insider (user setup)
  • Commit: 9524207
  • Date: 2023-11-22T14:33:51.941Z
  • Electron: 25.9.4
  • ElectronBuildId: 25127168
  • Chromium: 114.0.5735.289
  • Node.js: 18.15.0
  • V8: 11.4.183.29-electron.0
  • OS: Windows_NT x64 10.0.19045

@justschen
Copy link
Contributor

I've been unable to reproduce this - do you have a reliable repro for this @fourdim ?

@fourdim
Copy link
Author

fourdim commented Nov 30, 2023

At least it is reproducible on my side.

  • Disable all the extensions.
  • Create a file called a.ts
  • Copy the following code to the file:
export const aa = () => {
    console.log('aa');
};
  • Move the cursor to lo|g
export const aa = () => {
    console.lo|g('aa');
};
  • Right click to open the menu and then click on the refactor.

@mjbvz mjbvz removed their assignment Dec 4, 2023
@mjbvz mjbvz added the editor-code-actions Editor inplace actions (Ctrl + .) label Dec 4, 2023
@justschen
Copy link
Contributor

justschen commented Dec 5, 2023

repro:

  • Linux/windows
  • refactor (via menu) before hitting the lightbulb, using the quick fix menu, or using ctrl + shift + r
  • Observe focused, but incorrectly rendered menu

@justschen justschen added this to the December 2023 milestone Dec 5, 2023
@mirao
Copy link

mirao commented Dec 11, 2023

The same issue is in my environment when using "Refactor" on a selected text in a TypeScript file. I'm able to reproduce it reliably.
Note it happens only if the setting window.titleBarStyle has the value custom. Value native works well.
It could be a regression in 1.85 as I didn't see the issue in 1.84.

image

Tested with (both environments are affected):

  • Windows 11, VSCode 1.85
  • Ubuntu 22.04, VSCode 1.85

@DanTup
Copy link
Contributor

DanTup commented Dec 11, 2023

This is happening in stable now, the refactor menu is broken in many ways. For TypeScript it looks like this:

image

For Dart/Flutter, the menu just doesn't appear when you click "Refactor" in the context menu, but if you use the shortcut key it appears, and then it subsequently appears when you use the menu.

@justschen
Copy link
Contributor

exploring this right now - looks like it's only happening in Windows and Linux, was unable to repro on Mac.

@justschen
Copy link
Contributor

wonder if it's related to @bpasero 's change in the contextViewService af63c41

I'm seeing shadow-root where it's not supposed to be.

Screenshot 2023-12-12 at 9 02 02 AM

@bpasero bpasero added bug Issue identified by VS Code Team member as probable bug candidate Issue identified as probable candidate for fixing in the next release labels Dec 13, 2023
@bpasero bpasero self-assigned this Dec 13, 2023
@bpasero bpasero added regression Something that used to work is now broken confirmed Issue has been confirmed by VS Code Team member labels Dec 13, 2023
@bpasero bpasero modified the milestones: December / January 2024, November 2023 Recovery 2 Dec 13, 2023
@bpasero bpasero modified the milestones: November 2023 Recovery 2, November 2023 Recovery 1 Dec 13, 2023
bpasero added a commit that referenced this issue Dec 13, 2023
@bpasero bpasero closed this as completed Dec 13, 2023
@benibenj benibenj added the verified Verification succeeded label Dec 13, 2023
@github-actions github-actions bot locked and limited conversation to collaborators Jan 27, 2024
zongou pushed a commit to zongou/vscode that referenced this issue Feb 1, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Issue identified by VS Code Team member as probable bug candidate Issue identified as probable candidate for fixing in the next release confirmed Issue has been confirmed by VS Code Team member editor-code-actions Editor inplace actions (Ctrl + .) regression Something that used to work is now broken verified Verification succeeded
Projects
None yet
Development

No branches or pull requests

10 participants