Bug 1283523 - document bindings available to devtools clients; r?jlongster
MozReview-Commit-ID: H7nNrxfCxhm
--- a/devtools/docs/SUMMARY.md
+++ b/devtools/docs/SUMMARY.md
@@ -2,16 +2,17 @@
# Summary
* [Tool Architectures](tools.md)
* [Inspector](inspector-panel.md)
* [Memory](memory-panel.md)
* [Debugger](debugger-panel.md)
* [Responsive Design Mode](responsive-design-mode.md)
* [Frontend](frontend.md)
+ * [Environment](environment.md)
* [Panel SVGs](svgs.md)
* [React](react.md)
* [Guidelines](react-guidelines.md)
* [Tips](react-tips.md)
* [Redux](redux.md)
* [Guidelines](redux-guidelines.md)
* [Tips](redux-tips.md)
* [Backend](backend.md)
new file mode 100644
--- /dev/null
+++ b/devtools/docs/environment.md
@@ -0,0 +1,20 @@
+# Environment
+
+The client side of the Developer Tools is being rewritten to be able
+to run as content -- that is, without any special privileges. The
+loader, therefore, adds some bindings to the client environment which
+would ordinarily not be directly available to chrome code (or, at
+least, not under the same name).
+
+Here is the full list of content-like bindings that are available.
+
+* `atob`, `btoa`
+* `XMLHttpRequest`
+* `console`
+* `clearTimeout`, `setTimeout`
+* `clearInterval`, `setInterval`
+* `URL`
+* `CSSRule`
+* `DOMParser`
+
+New code should prefer these to using chrome APIs.