{"version":"2.1.269","anchor":"pointer-press-tracking-renamed-to-click-tracking-and-made-as","canonical_anchor":"pointer-press-tracking-renamed-to-click-tracking-and-made-as","heading":"Pointer-press tracking renamed to click tracking and made async","tier":"internal","area":"Terminal UI","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.269\/e\/pointer-press-tracking-renamed-to-click-tracking-and-made-as","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.269","markdown":"### Pointer-press tracking renamed to click tracking and made async\n\nInternal 'pointer press' tracking in the terminal UI was renamed to 'click' tracking and made asynchronous\n\n**Unclear.** The finding does not say what effect the deferred dispatch or the extra null argument has for a user.\n\n**What**\n\nInternal names used for tracking mouse clicks in Claude Code's terminal interface were renamed: `pressListeners`, `subscribePointerPresses`, and `tellPressedNowhere` are now `clickListeners`, `subscribeClicks`, and `tellClickedNowhere`. The 'clicked nowhere' event (fired when a click lands outside any tracked element) is now dispatched via `queueMicrotask`, deferring it slightly, and it now passes two null arguments instead of one.\n\n**Why**\n\nThis is an internal rename and timing change to how click events are dispatched; it does not describe a new capability for users, though deferring the dispatch may change the order in which click-related events fire.\n\n- Area: Terminal UI\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 0\/5"}