# workspace: Ensure pane handle hitbox blocks mouse events \(\#31719\) · gitcafe/zed

[View on GitCafe](https://git.cafe/gitcafe/zed/commit/cbed580db0e81021c208615a7f01f3f7613c89a5)

Repository: [gitcafe/zed](https://git.cafe/gitcafe/zed)

Visibility: public

Requested revision: cbed580db0e81021c208615a7f01f3f7613c89a5

Requested commit: cbed580db0e81021c208615a7f01f3f7613c89a5

Commit: cbed580db0e81021c208615a7f01f3f7613c89a5

Tree: ff4ddce673f1c61f93387a18e206f05bc377b6d7

Author: Finn Evers

Committer: GitHub

## Message

```
workspace: Ensure pane handle hitbox blocks mouse events (#31719)

Follow-up to #31712

Pane handle hitboxes were opaque prior to the linked PR. This was the
case because pane handles have an intentionally larger hitbox than the
pane dividers size to allow for easier dragging. The cursor style is
also updated for that hitbox to indicate that resizing is possible:


https://github.com/zed-industries/zed/blob/908678403871e0ef18bbe20f78a84654dfdd431d/crates/workspace/src/pane_group.rs#L1297-L1301

Not blocking the mouse events here causes mouse events to bleed through
this hitbox whilst actually any clicks will only cause a pane resize to
happen. Hence, this hitbox should continue to block mouse events to
avoid any confusion when resizing panes.

I considered using `HitboxBehavior::BlockMouseExceptScroll` here,
however, due to the reasons mentioned above, I decided against it. The
cursor will not indicate that scrolling should be possible. Since all
other mouse events on underlying elements (like hovers) are blocked, it
felt more reasonable to just go with `HitboxBehavior::BlockMouse`.

Release Notes:

- N/A
```

## Parents

- [8aef64bbfadc0060865c4d4b764f4769f6b4720e](https://git.cafe/gitcafe/zed/commit/8aef64bbfadc0060865c4d4b764f4769f6b4720e?format=markdown)

[Source at this commit](https://git.cafe/gitcafe/zed/tree/cbed580db0e81021c208615a7f01f3f7613c89a5?format=markdown)
