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

[v2] Folder selector not working as intended (Firefox) #1063

Closed
EnKrypt opened this issue Oct 8, 2019 · 9 comments
Closed

[v2] Folder selector not working as intended (Firefox) #1063

EnKrypt opened this issue Oct 8, 2019 · 9 comments
Assignees
Labels
bug Something isn't working

Comments

@EnKrypt
Copy link

EnKrypt commented Oct 8, 2019

  • code-server version: 2.1485-vsc1.38.1
  • OS Version: Arch Linux (rolling release)

Description

test

The folder selector seems to be very glitched, making it near impossible to open the folder I want.

Specifically, one of the main bugs seems to be that selecting a folder by left clicking or hitting return on a dropdown entry, does not reflect on the path in the bar.

As such, the "OK" button does not work as intended either.

This bug is consistently reproducible.

@EnKrypt EnKrypt added the bug Something isn't working label Oct 8, 2019
@sr229
Copy link
Contributor

sr229 commented Oct 8, 2019

Confirming bug existing on latest v2 and master branch.

@EnKrypt EnKrypt changed the title Folder selector not working as intended. [v2] Folder selector not working as intended. Oct 9, 2019
@EnKrypt
Copy link
Author

EnKrypt commented Oct 9, 2019

Any ideas where I can start looking if I wanted to find a fix myself?

Could this be coming from upstream, or is there any specific part of our codebase that I could probe?

@sr229
Copy link
Contributor

sr229 commented Oct 9, 2019

From what can I see this is more than likely a upstream bug as well since we're not doing particularly anything on the "open folder" feature.

@code-asher
Copy link
Member

Wow, there's some really weird behavior with the open dialog on Firefox. When I stepped through it the difference seemed to be that Firefox maintains the input as the active element while Chrome doesn't and VS Code runs different code based on whether the input is active or not which results in this discrepancy.

@code-asher
Copy link
Member

And I'll also note that this affects the initial text in the input as describe in #1051.

@code-asher
Copy link
Member

The code in question:

https://github.com/microsoft/vscode/blob/6ab598523be7a800d7f3eb4d92d7ab9a66069390/src/vs/workbench/services/dialogs/browser/simpleFileDialog.ts#L641

Essentially Firefox ends up running execCommand while Chromium ends up setting the text directly. I haven't looked deeper though to see whether this is a browser bug or a bug in the VS Code codebase.

@code-asher code-asher changed the title [v2] Folder selector not working as intended. [v2] Folder selector not working as intended (Firefox) Oct 24, 2019
@Developer626
Copy link

I've been having the same issue, and can confirm that this happens on Firefox and not Chrome (mobile and desktop).

@sr229
Copy link
Contributor

sr229 commented Oct 28, 2019

Hey OP, I'll be closing this since Microsoft has stated they would want this be seen on the main vscode project. Make sure to prefix [web] and use the same exact details here (with the exception of code-server version). Thanks for helping us out spot bugs!

@sr229 sr229 closed this as completed Oct 28, 2019
@EnKrypt
Copy link
Author

EnKrypt commented Oct 28, 2019

Sounds good. No problem and thank you.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

4 participants