-
Notifications
You must be signed in to change notification settings - Fork 20
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
[bug] When tray menu is replaced while it's opened an old menu stays on the screen #129
Comments
I really don't know what the best behavior would be here, it feels weird to replace the menu while it is open, because we would need to close the active menu and then show another menu which is not a good UX for the user IMO. Also do you have an idea how it works in other frameworks like electron? |
I agree this is a weird from UX perspective. It would be much nicer to have the ability to add/remove specific items instead of rebuilding whole menu. Electron closes the old menu and reopens the new one. This is what it looks like on Ubuntu (you should notice flickering caused by closing animation): Screencast.from.05.10.23.10_48_47.mp4 |
Yeah, this is available in tauri 2.0-alpha, and there are no plans to backport it to v1.
Even though this looks like a bad UX, I think we still need to comply |
I will move this over to |
I've just discovered that Ubuntu updates the tray menu automatically. Here is what my sample repo looks like on ubuntu (It doesn't flicker like an electron app): Screencast.from.27.11.23.13_26_38.mp4 |
Describe the bug
I'm creating this issue in addition to our recent talk on Twitter: https://twitter.com/TauriApps/status/1709573174269002065.
If the tray menu is opened during its change (tray_handle().set_menu()), an old menu stays visible. Users have to reopen the menu to see the changes.
Here is the video of the sample repo:
Area.mp4
Reproduction
I've made a repo: https://github.com/vovayatsyuk/tauri-dynamic-tray-menu
Here is the code I use:
Expected behavior
I expect that the old tray menu will be closed and a new one will be opened in its place.
Platform and versions
Stack trace
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: