What’s The Bug?
In a non-entry space, when opening an existing object in new window (via Cmd+ Clicking Object), new window displays as black screen.
- Upon refresh, window returns to entry space, making it feel like Anytype is trying to open an object but couldn’t pass through the entry space stage. In other words, it feels like Cmd+Object is acting as Cmd+Shift+N first, then attempt to switch to an object but couldn’t, because Cmd+Shift+N first loads entry space.
How To Reproduce It
- Go to a non-entry space
- Cmd+Click object to open object in new window (At any possible clicking point, e.g. search pane, or object-supported relation, or set)
- New window opens but it displays as Black screen
- Since sidebar is not visible at this point, attempt to switch space by clicking Ctrl+tab
- See that the space name has been switched to the next space in the space list (at sidebar) ← Meaning Anytype is loading the correct non-entry space
Side comparison
Scenario 1: Cmd+Object in entry space. No black screen & successful opening of object
Scenario 2: Cmd+Shift+N in whatever space. New window opens entry space and its homepage.
Image or Video
The Expected Behavior
Opening the Cmd+clicked object
Additional Context
To clarify, the entry space we are discussing here is the functioning entry space, not the entry space as displayed in individual space setting, in other words, not the entry space from this other bug Entry space not displayed at entry.
- To avoid this confusion in reproduction, test using a third (non-entry) space.
btw it would be nice to have a keyboard shortcut for open the current object in new window.
Device
MacBook Air M1
OS
Sequoia 15.1.1
Anytype Version
v.0.45.3
Network Mode
AnySync (should be irrelevant)
Technical Information
OS version: darwin arm64 15.1.1
App version: 0.45.3
Build number: build on 2025-02-17 15:22:27 +0000 UTC at #f1ceda0a1457dbf982d8b3fd8479ccdcb95df6d3 (dirty)
Library version: v0.39.11