Leave image content-edit mode, if an image is in it. Returns whether it did anything.
Canvas's version of this mode listens for Escape itself. The viewer runs the editor's mouse path instead, and the editor's keyboard callbacks are not in the viewer bundle at all — so without this there is no way out but clicking elsewhere.
Restrict this manager to states. Pass null to lift the restriction.
'none' and 'idle' are always reachable — idle is where a refused state lands, so excluding it would strand the machine.
View-only mode (TYP-597): stop responding to input, or start again.
Registered with canvas as an interaction listener, so typograph.set_interactive(false)
reaches this manager. It has to, because the editor and the viewer mute canvas's own
DocumentMouseManager at setup and drive interactions from here — before this, the call
gated only the muted manager and an implementer saw no effect at all.
Mirrors DocumentMouseManager.set_enabled(): highlighting, selection and text editing go away; zoom, scrolling, panning and the page bar are untouched; the programmatic selection API keeps working. Anything in progress is left rather than frozen on screen.
The states this profile may enter at all, or null for every state (the editor).
Two different questions are being answered here and they need two mechanisms. THIS one is "does this product have this interaction" — the viewer has no path tool and no marquee whatever the document says, and no per-element permission could express that. can() answers the other one, "may this element be edited that way", which varies per element and is the same question canvas asks.