This patch was autogenerated by my decomponents.py
It covers almost every file with the extension js, jsm, html, py,
xhtml, or xul.
It removes blank lines after removed lines, when the removed lines are
preceded by either blank lines or the start of a new block. The "start
of a new block" is defined fairly hackily: either the line starts with
//, ends with */, ends with {, <![CDATA[, """ or '''. The first two
cover comments, the third one covers JS, the fourth covers JS embedded
in XUL, and the final two cover JS embedded in Python. This also
applies if the removed line was the first line of the file.
It covers the pattern matching cases like "var {classes: Cc,
interfaces: Ci, utils: Cu, results: Cr} = Components;". It'll remove
the entire thing if they are all either Ci, Cr, Cc or Cu, or it will
remove the appropriate ones and leave the residue behind. If there's
only one behind, then it will turn it into a normal, non-pattern
matching variable definition. (For instance, "const { classes: Cc,
Constructor: CC, interfaces: Ci, utils: Cu } = Components" becomes
"const CC = Components.Constructor".)
MozReview-Commit-ID: DeSHcClQ7cG
This cleans up all tests that were not moved into the sanitize directory
as part of the previous commit, but still use sanitize.js
MozReview-Commit-ID: 1CVa0ByVYDk
See comment 12. There is no guarantee 'canplaythrough' will always fire when
download is slow. It should listen to 'suspend' which is fired when download
is stopped.
MozReview-Commit-ID: GFUtjBpsAcT
This patch adds test cases for testing favicons of allTabs menu in terms of originAttributes.
It adds tests in existing tests, browser_favicon_userContextId.js and browser_favicon_firstParty.js.
The test will open tabs with different originAttributes and trigger the popup of
allTabs menu. Then it will verify that whether the network requests of favicon
have correct originAttributes.
MozReview-Commit-ID: 4Aa7RDFdosA
This patch adds test cases for testing favicons of allTabs menu in terms of originAttributes.
It adds tests in existing tests, browser_favicon_userContextId.js and browser_favicon_firstParty.js.
The test will open tabs with different originAttributes and trigger the popup of
allTabs menu. Then it will verify that whether the network requests of favicon
have correct originAttributes.
MozReview-Commit-ID: 4Aa7RDFdosA
Activity-stream is only enabled in Nightly, and if activity-stream is not
enabled, about:newtab is loaded without the flag
nsIAboutModule::URI_SAFE_FOR_UNTRUSTED_CONTENT, so it will be loaded with
System Principal.
Update the test to verify about:newtab should have firstPartyDomain set
when we enable the pref.
We split about:newtab from browser_firstPartyIsolation_aboutPages.js because
about:newtab needs special care.
In the original test browser_firstPartyIsolation_aboutPages.js, when calling
tabbrowser.addTab, if it found out the uri is about:newtab, it will use
the preloaded browser, however the preloaded browser is loaded before when we
turn on the firstPartyIsolation pref, which won't have the pref set.
To prevent to use the preloaded browser, a simple trick is open a window
first.
A web page could generate an URL by URl.createObjectURL(new Blob(...));
then navigate to this generated URL.
In this case the (top-level) document URI will be blob:{origin}:{uuid}.
And we try to add firstPartyDomain on this top-level document with blob URI, so
the following request from this document could have correct origin
attributes.
In the past we used a fixed value for the firstPartyDomain of
NullPrincipal, now we derive it from the path of NullPrincipal, so it
will be unique everytime we create it.
This reduces the amount of places where we need to specify the mozilla/frame-script environment. It does have
the side effect of allowing those globals in the whole file, but that is what specifying the environment would
do, and this is also for mochitest test files only.
MozReview-Commit-ID: 1LLFbn6fFJR