To support mash / out-of-process ash.
High level design from meeting with dtseng:
* Ash is in charge of the desktop tree. It has an AutomationManagerAura or equivalent.
* "Remote apps" use AXRemoteHost to supply node trees to ash
* The browser is just a "remote app" like keyboard shortcut viewer
* Ash passes the node trees to the browser, which forwards them to the accessibility extension
* As a future optimization we might pass around mojo interface pointers so the remote app could talk directly to the browser, or directly to the extension
Comment 1 by jamescook@chromium.org
, Sep 21