Module control 

The host’s control lines to the server, on stdout.

The input pipe runs the other way. The server writes pointer gestures on the host’s stdin; the host writes the things a viewer has to answer here - a page’s file chooser today - as one JSON line per event on its stdout, which the server reads beside the child’s frames. The log stays on stderr, so neither stream is parsed for the other’s content.

Re-exports

use std::io::Write as _; 🔒

use serde::Deserialize; 🔒

use serde::Deserialize; 🔒

use serde::Serialize; 🔒

use serde::Serialize; 🔒

Enums

HostEvent

One thing the host needs the server to route.

JsDialogState

Where a JavaScript dialog stands. The host holds one until it is answered, so these are the facts there are: it was raised, someone answered it, or the page took it away without an answer (a navigation, or the tab closing). Closed is not Answered: nobody decided.

Functions

emit

Write one event line for the server.

parse

The event one line names, or None for a line the server cannot read.