Transform XML tree viewer to blink-in-js implementation.

Source/core/xml/XMLTreeViewer.idl

Index: Source/core/xml/XMLTreeViewer.idl
diff --git a/Source/modules/geofencing/GeofencingRegion.idl b/Source/core/xml/XMLTreeViewer.idl
similarity index 59%
copy from Source/modules/geofencing/GeofencingRegion.idl
copy to Source/core/xml/XMLTreeViewer.idl
index 4e22058d98b22fb2f0a7d196263ea4b9a458feab..455313a8ec2f6971d8ee6c9d35dd0315535e09c9 100644
--- a/Source/modules/geofencing/GeofencingRegion.idl
+++ b/Source/core/xml/XMLTreeViewer.idl
@@ -1,11 +1,8 @@
 // Copyright 2014 The Chromium Authors. All rights reserved.
 // Use of this source code is governed by a BSD-style license that can be
 // found in the LICENSE file.
-
 [
-    RuntimeEnabled=Geofencing,
-    NoInterfaceObject,
     GarbageCollected,
-] interface GeofencingRegion {
-    readonly attribute DOMString id;
-};
+] interface XMLTreeViewer {
+    [ImplementedInPrivateScript, OnlyExposedToPrivateScript] void transformDocumentToTreeView();

[eseidel, 2014/08/26 05:40:54]

What's the point of moving this to Blink-in-JS if we have to add backdoors to
implement it?

[vivekg, 2014/08/26 05:51:57]

Sorry @eseidel, I could not get what meant by saying 'add backdoors to implement
it?'. 

[haraken, 2014/08/26 05:57:48]

I'm considering a way to avoid the backdoor (but at least this CL is not making
our current situation worse; i.e., the current XMLTreeViewer is already
implemented in JS and working by manually getting invoked from C++).

Either way I think we should move this method to Document.idl (or to
DocumentXMLTreeViewer.idl, which is a partial interface of Document.idl). That
way we no longer need an interface for XMLTreeViewer. Then you can completely
remove the XMLTreeViewer class.

+};