-
Notifications
You must be signed in to change notification settings - Fork 5.6k
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
Comments
Confirming bug existing on latest v2 and master branch. |
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? |
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. |
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. |
And I'll also note that this affects the initial text in the input as describe in #1051. |
The code in question: Essentially Firefox ends up running |
I've been having the same issue, and can confirm that this happens on Firefox and not Chrome (mobile and desktop). |
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! |
Sounds good. No problem and thank you. |
code-server
version: 2.1485-vsc1.38.1Description
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.
The text was updated successfully, but these errors were encountered: