zeekayandHanzo Dev e11127ec42 The terminal tells its parent it is really there ...

A workspace framing this page cannot find out for itself. Everything it can
reach across the origin lies to it identically: a frame refused by
`frame-ancestors` and one that loaded perfectly BOTH throw on contentDocument,
because the browser substitutes its own error document for the refusal. So the
workspace read every blocked terminal as healthy and painted an opaque black
rectangle over the only way out of it.

This is the honest half of the fix: sent by the page that owns the terminal,
after xterm has actually opened, so its absence means the terminal is genuinely
not there — gate, dead tunnel, offline machine, all the same silence.

`'*'` as the target origin because every machine publishes on its own tunnel
host, and the message claims nothing worth targeting.

Co-authored-by: Hanzo Dev <[email protected]>

2026-08-04 06:49:32 -07:00

..

term

The terminal tells its parent it is really there

2026-08-04 06:49:32 -07:00

themes

hanzo — the Hanzo CLI

2026-07-17 10:15:57 -07:00