Bug 1550591 - nsIRequestTailUnblockCallback and nsIRequestContext don't need to be scriptable. r=valentin
authorAndrew McCreight <continuation@gmail.com>
Fri, 10 May 2019 06:04:53 +0000
changeset 535302 fdfc7f74c157199e6bb88da583f0e9b3b88aec0f
parent 535301 b97aef38d5565a7c16879aac056ccaa7542a1d15
child 535303 292fec00f80015bbfabdf07c15a3b35184b8b1c0
push id2082
push userffxbld-merge
push dateMon, 01 Jul 2019 08:34:18 +0000
treeherdermozilla-release@2fb19d0466d2 [default view] [failures only]
perfherder[talos] [build metrics] [platform microbench] (compared to previous push)
reviewersvalentin
bugs1550591
milestone68.0a1
first release with
nightly linux32
nightly linux64
nightly mac
nightly win32
nightly win64
last release without
nightly linux32
nightly linux64
nightly mac
nightly win32
nightly win64
Bug 1550591 - nsIRequestTailUnblockCallback and nsIRequestContext don't need to be scriptable. r=valentin Differential Revision: https://phabricator.services.mozilla.com/D30607
netwerk/base/nsIRequestContext.idl
--- a/netwerk/base/nsIRequestContext.idl
+++ b/netwerk/base/nsIRequestContext.idl
@@ -21,17 +21,17 @@ interface nsIStreamListener;
 [ptr] native SpdyPushCachePtr(mozilla::net::SpdyPushCache);
 
 /**
  * Requests capable of tail-blocking must implement this
  * interfaces (typically channels).
  * If the request is tail-blocked, it will be held in its request
  * context queue until unblocked.
  */
-[scriptable, uuid(7EB361D4-37A5-42C9-AFAE-F6C88FE7C394)]
+[uuid(7EB361D4-37A5-42C9-AFAE-F6C88FE7C394)]
 interface nsIRequestTailUnblockCallback : nsISupports
 {
   /**
    * Called when the requests is unblocked and proceed.
    * @param result
    *    NS_OK - the request is OK to go, unblocking is not
    *            caused by cancelation of the request.
    *    any error - the request must behave as it were canceled
@@ -43,17 +43,17 @@ interface nsIRequestTailUnblockCallback 
 /**
  * The nsIRequestContext is used to maintain state about connections
  * that are in some way associated with each other (often by being part
  * of the same load group) and how they interact with blocking items like
  * HEAD css/js loads.
  *
  * This used to be known as nsILoadGroupConnectionInfo and nsISchedulingContext.
  */
-[scriptable, uuid(658e3e6e-8633-4b1a-8d66-fa9f72293e63)]
+[uuid(658e3e6e-8633-4b1a-8d66-fa9f72293e63)]
 interface nsIRequestContext : nsISupports
 {
   /**
    * A unique identifier for this request context
    */
   [notxpcom, nostdcall] readonly attribute unsigned long long ID;
 
   /**