Depends on D229378
Expose a getter on nsILoadInfo to easily retrieve the fetch destination as a string
This avoids duplicating the mapping logic in JS for webdriver bidi
Differential Revision: https://phabricator.services.mozilla.com/D229384
This changeset synchronizes the initiatorType from the child channel to the parent channel in asyncOpen.
It also removes noscript from initiatorType in nsITimedChannel
Differential Revision: https://phabricator.services.mozilla.com/D229378
This method will later be used to import default permissions from remote
settings through the remote permission manager.
Differential Revision: https://phabricator.services.mozilla.com/D222650
This method will later be used to import default permissions from remote
settings through the remote permission manager.
Differential Revision: https://phabricator.services.mozilla.com/D222650
This method will later be used to import default permissions from remote
settings through the remote permission manager.
Differential Revision: https://phabricator.services.mozilla.com/D222650
This adds extra headers and query parameters to identify MAR GET
requests as originating from browsing profiles or background task
profiles.
This extracts a simple existing function for setting headers and then
makes it available to `nsIIncrementalDownload`. The existing function
is not the most pleasant API, but it exists and is much easier than
working through the details of storing header name-value pairs until
they are ready to be used. It's also the same API exposed by Windows
BITS, so there's no additional manipulation required to support BITS.
Differential Revision: https://phabricator.services.mozilla.com/D221860
MOZ_RUNINIT => initialized at runtime
MOZ_CONSTINIT => initialized at compile time
MOZ_GLOBINIT => initialized either at runtime or compile time, depending on template parameter, macro parameter etc
This annotation is only understood by our clang-tidy plugin. It has no
effect on regular compilation.
Differential Revision: https://phabricator.services.mozilla.com/D223341
This patch includes a special handling for the moz-extension _generated_background_page.html urls inside
nsStandardURL::EqualsInternal because it doesn't resolve to a file (instead it resolves to a data: URI,
see ExtensionProtocolHandler::ResolveSpecialCases), similarly to resource:// urls which are special case
a few lines before in the same nsStandardURL::EqualsInternal.
The test case introduced by the parent patch passes successfully on the unpacked extension loaded temporarily
with these changes applied.
Depends on D226376
Differential Revision: https://phabricator.services.mozilla.com/D226470
The warnings are:
no edition set: defaulting to the 2015 edition while the latest is 2021
unused manifest key: lib.plugin
Differential Revision: https://phabricator.services.mozilla.com/D226855
This patch includes a special handling for the moz-extension _generated_background_page.html urls inside
nsStandardURL::EqualsInternal because it doesn't resolve to a file (instead it resolves to a data: URI,
see ExtensionProtocolHandler::ResolveSpecialCases), similarly to resource:// urls which are special case
a few lines before in the same nsStandardURL::EqualsInternal.
The test case introduced by the parent patch passes successfully on the unpacked extension loaded temporarily
with these changes applied.
Depends on D226376
Differential Revision: https://phabricator.services.mozilla.com/D226470
This will prevent devs from accidentally requesting no buttons, since
the only way to dismiss such a prompt is with an intentional call to
prompt.close(). A request that indicates that button 0's label is
the empty string previously indicated button 0 is hidden, which means no
buttons. Now, that case is an exception unless BUTTON_NONE is set.
Differential Revision: https://phabricator.services.mozilla.com/D226081
There was a bug where the Action was getting initialized with the wrong URI, thus mTargerURI staying empty.
Also added an errorcheck to OnCacheEntryAvailable so even if an empty URI sneaks in from somewhere else it doesn't just crash.
Differential Revision: https://phabricator.services.mozilla.com/D225181
This is just an experiment to see if the recent telemetry changes is really caused by bug 1678312.
Will reland the change in bug 1678312 later.
Differential Revision: https://phabricator.services.mozilla.com/D224734
Knowing the actual fetchPriority of the initial request is useful information
when computing the urgency. This allows us to not worry about the priority
being clobbered by another caller of nsISupportsPriority.
Differential Revision: https://phabricator.services.mozilla.com/D221957
