Unexpected drag state triggered on click of another entry in project panel when creating a new file

[ssut]

Check for existing issues

• Completed

Describe the bug / provide steps to reproduce it

1. Trigger 'New File' from the project panel, making the filename editor visible.
2. Single click on another entry(file) in the project panel while the filename editor is still visible. This action will make the filename editor disappear.
3. Move the mouse cursor to enter the drag state for the clicked entry.

Expected behavior: the clicked item should not enter the drag state.

Environment

Zed: v0.145.1 (Zed)
OS: macOS 14.5.0
Memory: 64 GiB
Architecture: aarch64

If applicable, add mockups / screenshots to help explain present your vision of the feature

zed.mp4

If applicable, attach your Zed.log file to this issue.

[notpeter]

It seems like there are a couple possible behaviors when clicking elsewhere in the project panel while in the midst of typing a new filename:

1. Cancel the creation of the new file (current zed behavior)
2. Confirm the creation of the new file; cancel creation if no filename present [behavior of vscode]
3. Lock focus. Make clicking elsewhere do nothing until the filename entry is explicitly confirmed/cancelled.

It sounds like you're advocating for the third option, is that correct?

[ssut]

Canceling the creation of the new file is just okay.
To clarify, my main concern is not about the behavior of the filename editor itself, but rather the unintended drag state that occurs when clicking another entry in the project panel. The selected item should remain in a normal state(marked?) unless explicitly dragged. As you can see from the screen recording I attached in the issue content, the item Cargo.toml enters to the drag state even though I just clicked it, not dragging.

[ssut]

Update:
I found that the error occurs when clicking an entry located after(below) the filename editor's location(position). Here's the detailed breakdown when creating a new file:

1. A mousedown event occurs on another entry.
2. The filename editor got a blur event and this makes the filename editor hidden due to step 1.
3. A mouseup event happens on the entry clicked in step 1 because the term click includes both mousedown and mouseup. This starts the dragging action because it exceeds the drag threshold from the following code in div.rs:

&& (event.position - mouse_down.position).magnitude()
    > DRAG_THRESHOLD

By the way, I logged the values to demonstrate this behavior:

event.position.y = 439.47265625, mouse_down.position.y = 436.08203125, magnitude = 3.390625

FYI on this, the drag event never happens when I click an entry located before the filename editor.

I don't get to know how to fix this problem in the code so far, but I think this information can be very helpful for solving the issue.