Bug 1456048 - move ChromeUtils.requestPerformanceMetrics to the right scope - r?kmag
requestPerformanceMetrics should not be made available in the Worker scope.
MozReview-Commit-ID: K2nY6JIzWrE
--- a/dom/chrome-webidl/ChromeUtils.webidl
+++ b/dom/chrome-webidl/ChromeUtils.webidl
@@ -118,20 +118,16 @@ namespace ChromeUtils {
readonly attribute any recentJSDevError;
/**
* Reset `recentJSDevError` to `undefined` for the current JSRuntime.
*/
void clearRecentJSDevError();
#endif // NIGHTLY_BUILD
-#ifndef RELEASE_OR_BETA
- void requestPerformanceMetrics();
-#endif
-
/**
* IF YOU ADD NEW METHODS HERE, MAKE SURE THEY ARE THREAD-SAFE.
*/
};
/**
* Additional ChromeUtils methods that are _not_ thread-safe, and hence not
* exposed in workers.
@@ -309,16 +305,23 @@ partial namespace ChromeUtils {
/**
* Creates a JS Error object with the given message and stack.
*
* If a stack object is provided, the error object is created in the global
* that it belongs to.
*/
[Throws]
object createError(DOMString message, optional object? stack = null);
+
+#ifndef RELEASE_OR_BETA
+ /**
+ * Request performance metrics to the current process & all ontent processes.
+ */
+ void requestPerformanceMetrics();
+#endif
};
/**
* Used by principals and the script security manager to represent origin
* attributes. The first dictionary is designed to contain the full set of
* OriginAttributes, the second is used for pattern-matching (i.e. does this
* OriginAttributesDictionary match the non-empty attributes in this pattern).
*