Hotkey window cannot identify correctly where the Dock is

Open
#2,445 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
45/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Quiet
Tech stack
macos

Research direction

Start by reproducing the Hotkey Window placement on macOS 12.6.2 with the Dock pinned to the left and the window set to “Pin to bottom/top”; retry after cmd+w as described. Trace the placement behavior and verify that the window consistently avoids being obscured by the Dock when the hotkey is pressed.

Written by the indexing model from the issue text.

Description

area:settings-keybindings area:window-tabs-panes bug needs-info ready-to-implement triaged
Discord username (optional)

No response

Describe the bug

I usually use a Dock pinned at the left of the screen. When I set up a HotKey Window with "Pin to bottom/top" and press the hotkey, the Hotkey window often clings to the left side of the screen (partially obscured by Dock). However, sometimes it's normal again without changing any setting.

image
To Reproduce
  1. Pin the Dock at the left side;
  2. Set up a Hotkey Window with "Pin to bottom/top";
  3. Press the hotkey;
  4. the Hotkey window often clings to the left side of the screen. If not, cmd+w and try again.
Expected behaviour

No response

Screenshots

No response

Operating System

MacOS

OS Version

12.6.2

Shell Version

zsh 5.8.1

Warp Version

v0.2022.12.13.08.04.stable_01

Additional context

No response

Does this block you from using Warp daily?

Yes, this issue prevents me from using Warp daily.

Warp Internal (ignore): linear-label:b8107fdf-ba31-488d-b103-d271c89cac3e

None

Dominant language
Rust
Stars
65.1k
Forks
5.6k
PR merge metrics
PR metrics pending

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from warpdotdev/warp

All issues in warpdotdev/warp

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.