Open bug report

Remote-click overlay leaves the whole screen dimmed for many minutes; image-space clicks into a Hydrogen webview card didn't land

John Lauer · 21d ago

2026-10-20 ~02:40Z on the office PC (ab 2.1.184, Windows 11, 4K): two desktop_click {"space":"image", ...} calls into a Hydrogen window (answering a Claude question card) put up ab's remote-input overlay: the whole screen dimmed grey with the teal click marker. The clicks did not land on the card (it stayed unanswered), and the grey dim stayed on the screen for many minutes afterwards (at least 02:40 to past 03:00, seen in a full-screen recording of that monitor), long after the clicks finished.

Effect: a long full-screen demo recording turned grey for half an hour; the clicks themselves did nothing.

Expected: the overlay lasts only for the input it signals (fade out within a second or two after the last synthetic input), and a click that lands on an element inside a webview actually reaches it (or the reply says it didn't).

1 Reply

John Lauer · 21d ago

Correction and measurements from the recordings: the grey wash covered only the Hydrogen window's content area (its title bar and the Windows taskbar stayed untouched), and it began at 02:41Z, right at the clicks. The content area's 10th-percentile luma went from ~30 to ~106 and stayed there through 06:30Z, about four hours, with stretches at ~63 near the end (05:30-06:30). Clean again by 06:45Z. So it is window-scoped, but it outlived the clicks by hours.

Log in to reply.