You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Right now if you try to summon scratchpad while anything is fullscreen, it just doesnt appear on top but is active and then I cannot tell if its still open or i accidentally interact with windows that are hidden.
Adjacent to this (if it needs its own feature please tell me) but would be nice if we could also assign a global dismiss key for all scratchpads.
When you get used to scratchpads as a replacement for other workspaces, it feels limiting when you realize how it behave fullscreen.
What would a better experience look like?
Have the scratchpad appear over any fullscreen app, have a global hotkey for dismissing (potentially?)
It would be particularly useful to have notes overlayed on something you see thanks to the transparency of the scratchpad view rather than toggling out to a separate workspace
Possible approach
No response
What have you tried?
No response
Area
None
Examples or references
No response
How would you like to help?
I can test an implementation in my own session.
I might be interested in implementing this after we discuss the scope.
Anything else?
No response
Reacted by Tanuki, fraction, LielaXea and Fabien Devaux
I'd argue that this is a bug, not a feature proposal. Scratchpads should be able to appear above fullscreen windows, and there's no case where it's the correct behavior for them to sit behind the fullscreen layer.
As to a global dismiss action, I'd like that as well; it should probably be a separate issue, though.
Activity
tanukikabu commentedon Oct 25, 2026
i think the easiest implementation of this is probably being able to pin a scratchpad window, but i agree this would be very useful.
fractioneater commentedon Nov 2, 2026
I'd argue that this is a bug, not a feature proposal. Scratchpads should be able to appear above fullscreen windows, and there's no case where it's the correct behavior for them to sit behind the fullscreen layer.
As to a global dismiss action, I'd like that as well; it should probably be a separate issue, though.