[Linux] Open File/Folder Dialog is Shown in Background
Check for existing issues
- [X] Completed
Describe the bug / provide steps to reproduce it
Like in VS Code, when you press Ctrl+O, or click "open project", the dialog opens behind the program window.
This must have to do with the window framework. In VS Code, the issue persists for years. After DE restart, VS code shows the dialog properly on top ONLY ONCE. Then it starts to work as before. Sometimes, the dialog would open in front of the editor, but unfocused.
SublimeText in Ubuntu/Mate has no such problem at all.
Environment
Ubutnu 23.10 Mate desktop 1.26.2
If applicable, add mockups / screenshots to help explain present your vision of the feature
No response
If applicable, attach your Zed.log file to this issue.
Zed.log
This sounds like an issue with your desktop environment, the file chooser portal doesn't specify any way to provide an activation token or similar. On KDE Wayland opening the file picker in Zed always automatically takes focus.
VS code shows the dialog properly on top ONLY ONCE SublimeText in Ubuntu/Mate has no such problem at all.
Maybe VSCode is using the portal while Sublime calls the GTK APIs directly? It's weird nonetheless.
Actually, what I said is wrong. Looks like we need to specify window identifiers when calling certain portals. I'll work on it later.
I am facing this issue after installing zed on Ubuntu(KDE). Edit: With Ubuntu(KDE) the Vs code opens "Open Project" window correctly in the foreground. Did not face this issue on master branch(from sometime in June, build locally) on Ubuntu(GNOME) Most likely switch to KDE caused this, can't say for sure.
Hi there! 👋 We're working to clean up our issue tracker by closing older issues that might not be relevant anymore. If you are able to reproduce this issue in the latest version of Zed, please let us know by commenting on this issue, and we will keep it open. If you can't reproduce it, feel free to close the issue yourself. Otherwise, we'll close it in 7 days. Thanks for your help!
This issue was closed due to inactivity. If you're still experiencing this problem, please open a new issue with a link to this issue.