# fix\(web\): report hover mouse motion only in any-event tracking · stienswout/t3code

[View on GitCafe](https://git.cafe/stienswout/t3code/commit/3dacf683567555a0945cdf088349eef280c2f0f0)

Repository: [stienswout/t3code](https://git.cafe/stienswout/t3code)

Visibility: public

Requested revision: 3dacf683567555a0945cdf088349eef280c2f0f0

Requested commit: 3dacf683567555a0945cdf088349eef280c2f0f0

Commit: 3dacf683567555a0945cdf088349eef280c2f0f0

Tree: 205b8d13b635b33028f61427bdd0b43fdd875051

Author: Wout Stiens

Committer: Wout Stiens

## Message

```
fix(web): report hover mouse motion only in any-event tracking

Normal (DEC 1000) and button-event (DEC 1002) tracking never report
motion without a pressed button, so hovering the canvas no longer
routes pointermove through the mouse reporting path unless any-event
tracking (DEC 1003) is enabled or the pointer was captured by a
reported press. Adds a Ghostty mode query for DEC 1003 and covers the
mode transitions in the vendored ABI regression test.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

```

## Parents

- [79301107ae483a5479faa70f6d5f3b7a16e1dae2](https://git.cafe/stienswout/t3code/commit/79301107ae483a5479faa70f6d5f3b7a16e1dae2?format=markdown)

[Source at this commit](https://git.cafe/stienswout/t3code/tree/3dacf683567555a0945cdf088349eef280c2f0f0?format=markdown)