Right-click release can be missed, leaving mouse state stuck in drag:right

[noborus]

Issue Description

Ghostty may sometimes enter a drag state after a right-click, failing to correctly report the release event.

Expected Behavior

When the right-click is released, Ghostty should report a release and change its state to not drag.

Actual Behavior

You can verify this using the following shell script.

https://gist.github.com/cb46d900a623977bb380c46fd5cf269f.git

After right-clicking, run this script and move the mouse.

The following will be displayed:

state=drag:right raw_b=34

It should be:

state=drag:none raw_b=35

Right-clicking again will fix it.

Reproduction Steps

1. Open Ghostty
2. curl -O https://gist.githubusercontent.com/noborus/cb46d900a623977bb380c46fd5cf269f/raw/45f195d82ff6325108836599b36bcb54da7d0b59/mouse_status.sh
3. right click
4. bash mouse_status.sh

Ghostty Logs

info: ghostty version=1.3.0
info: ghostty build optimize=ReleaseFast
info: runtime=.gtk
info: font_backend=.fontconfig_freetype
info: dependency harfbuzz=8.3.0
info: dependency fontconfig=21500
info: renderer=renderer.generic.Renderer(renderer.OpenGL)
info: libxev default backend=io_uring
info(os_locale): setlocale from env result=LC_CTYPE=ja_JP.UTF-8;LC_NUMERIC=ja_JP.UTF-8;LC_TIME=C;LC_COLLATE=ja_JP.UTF-8;LC_MONETARY=ja_JP.UTF-8;LC_MESSAGES=ja_JP.UTF-8;LC_PAPER=ja_JP.UTF-8;LC_NAME=ja_JP.UTF-8;LC_ADDRESS=ja_JP.UTF-8;LC_TELEPHONE=ja_JP.UTF-8;LC_MEASUREMENT=ja_JP.UTF-8;LC_IDENTIFICATION=ja_JP.UTF-8
info(gtk): GTK version build=4.14.5 runtime=4.14.5
info(gtk): libadwaita version build=1.5.0 runtime=1.5.0
info: reading configuration file path=/home/noborus/.config/ghostty/config
info(config): default shell src=passwd value=/usr/bin/zsh
info(config): default working directory src=passwd value=/home/noborus
warning(gtk_ghostty_application): setting GDK_DEBUG=gl-disable-gles,gl-no-fractional,vulkan-disable
warning(gtk_ghostty_application): setting GDK_DISABLE=color-mgmt
warning(glib): WARNING: Gtk: Theme parser error: style.css:140:17-19: Unexpected data at end of hsl() argument
info(opengl): loaded OpenGL 4.6
info(io_exec): found Ghostty resources dir: /usr/share/ghostty
info(io_exec): shell integration automatically injected shell=.zsh
warning(gtk_ghostty_application): unimplemented action=.cell_size
info(io_exec): started subcommand path=/bin/sh pid=529669
info(io_exec): pty fd closed, read thread exiting
info(surface): surface closed addr=571e286455e0

Ghostty Version

hostty 1.3.0

Version
  - version: 1.3.0
  - channel: stable
Build Config
  - Zig version   : 0.15.2
  - build mode    : .ReleaseFast
  - app runtime   : .gtk
  - font engine   : .fontconfig_freetype
  - renderer      : renderer.generic.Renderer(renderer.OpenGL)
  - libxev        : io_uring
  - kernel version: 6.17.0-1010-oem
  - desktop env   : other
  - GTK version   :
    build         : 4.14.5
    runtime       : 4.14.5
  - libadwaita    : enabled
    build         : 1.5.0
    runtime       : 1.5.0
  - libX11        : enabled
  - libwayland    : enabled

OS Version Information

Ubuntu 24.04.4 and macOS Tahoe 26.4

(Linux only) Display Server

Wayland

(Linux only) Desktop Environment/Window Manager

GNOME 46.0

Minimal Ghostty Configuration

none

Additional Relevant Configuration

gdamore/tcell#1045

I acknowledge that:

• I have reviewed the FAQ and confirm that my issue is NOT among them.
• I have searched the Ghostty repository (both open and closed Discussions and Issues) and confirm this is not a duplicate of an existing issue or discussion.
• I have checked the "Preview" tab on all text fields to ensure that everything looks right, and have wrapped all configuration and code in code blocks with a group of three backticks (```) on separate lines.

[noborus]

In Go's tcell, you can verify this using the following steps:

Right-click
cd tcell
go run _demos/mouse.go

In Go's BubbleTea,, you can verify this using the following steps:

Right-click
cd bubbletea
go run ./examples/mouse/main.go

[noborus]

This issue no longer occurs in tcell v3.3.0 and later versions, as a fix (gdamore/tcell#1051) has been implemented to avoid it.