Bug 1328620 - Rename LargeAllocationRelatedBrowsingContexts to reflect new content, r=smaug

MozReview-Commit-ID: AQVqIFKObsI

dom/base/nsContentUtils.cpp

@@ -9723,7 +9723,7 @@ nsContentUtils::AttemptLargeAllocationLoad(nsIHttpChannel* aChannel)
                                       NS_LITERAL_CSTRING("DOM"),
                                       doc,
                                       nsContentUtils::eDOM_PROPERTIES,
-                                      "LargeAllocationRelatedBrowsingContexts");
+                                      "LargeAllocationNotOnlyToplevelInTabGroup");
     }
     return false;
   }

dom/locales/en-US/chrome/dom/dom.properties

@@ -315,6 +315,6 @@ LargeAllocationSuccess=This page was loaded in a new process due to a Large-Allo
 # LOCALIZATION NOTE: Do not translate "Large-Allocation", as it is a literal header name. Do not translate GET.
 LargeAllocationNonGetRequest=A Large-Allocation header was ignored due to the load being triggered by a non-GET request.
 # LOCALIZATION NOTE: Do not translate "Large-Allocation", as it is a literal header name. Do not translate `window.opener`.
-LargeAllocationRelatedBrowsingContexts=A Large-Allocation header was ignored due to the presence of windows which have a reference to this browsing context through the frame hierarchy or window.opener.
+LargeAllocationNotOnlyToplevelInTabGroup=A Large-Allocation header was ignored due to the presence of windows which have a reference to this browsing context through the frame hierarchy or window.opener.
 # LOCALIZATION NOTE: Do not translate "Large-Allocation", as it is a literal header name
 LargeAllocationNonE10S=A Large-Allocation header was ignored due to the document not being loaded out of process.