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
Describe the bug
It seems that the DropPoint will not appear in the same screen in full screen mode.
To Reproduce
Steps to reproduce the behavior:
0. open finder with a new window
Click the left upper side green button to make the window full-screen mode
type shift-tab
screen will be changed to a new space and the DropPoint will appear there.
no way to use the original finder
Expected behavior
even if in the full screen mode, DropPoint should appear in the original full-screen window
Screenshots
it should be clear if follow the above steps
Desktop (please complete the following information):
macos Monterey
Version 12.5.1
MacBook Pro (14-inch, 2021)
Chip Apple M1 Pro
Memory 16 GB
Additional context
If this is done in an external display, the DropPoint will appear in the macbook main display, but it would be better to let it appear in the same windows. I guess this issue is the macOS spec and cannot avoid it. So better use it not in a full-screen mode.
The text was updated successfully, but these errors were encountered:
Describe the bug
It seems that the DropPoint will not appear in the same screen in full screen mode.
To Reproduce
Steps to reproduce the behavior:
0. open finder with a new window
Expected behavior
even if in the full screen mode, DropPoint should appear in the original full-screen window
Screenshots
it should be clear if follow the above steps
Desktop (please complete the following information):
macos Monterey
Version 12.5.1
MacBook Pro (14-inch, 2021)
Chip Apple M1 Pro
Memory 16 GB
Additional context
If this is done in an external display, the DropPoint will appear in the macbook main display, but it would be better to let it appear in the same windows. I guess this issue is the macOS spec and cannot avoid it. So better use it not in a full-screen mode.
The text was updated successfully, but these errors were encountered: