This issue tracks moving XMLTreeViewer off of its private script implementation.
The current plan is to reuse the existing JS implementation (DocumentXMLTreeViewer.js) and run the script in its own world (using executeScriptInIsolatedWorld), without using any of the Blink-in-JS machinery.
+vivek who did the previous move _to_ Blink-in-JS and may have context
+haraken,esprehn for their opinions
SGTM. This looks like it would more or less amount to a revert of the changes that moved it to Blink-in-JS (except for any bug fixes there may have been in the meantime).
Those changes were (in multiple pieces, because we had split repositories at the time):
https://codereview.chromium.org/479753003https://codereview.chromium.org/539653002https://codereview.chromium.org/540493002
It seems we had originally used the main world for this (so presumably that's web-compatible), but an isolated world shouldn't have a high cost here and does insulate the script more from other frames.
Comment 1 by jbroman@chromium.org
, Dec 8 2016