It uses direct XHRs to fetch device information. These XHRs should instead be initiated from a network-navigated subframe to ensure isolation from the WebUI process.
See bug 829218 and bug 829412 for some additional details.
Clarification: the issue is with the cloud print interface in the Print Preview WebUI, not with the local discovery web UI that registers printers with cloud print.
We have discussed trying to move the cloud print interaction into the C++ handler in the past, so that might be another option. This was motivated by the case of printing specifically, where the printed document has to be sent from the handler to Print Preview only to be sent again to the cloud print server.
Comment 1 by roc...@chromium.org
, Apr 5 2018