Google's SafeBrowsing database is currently optimized for top-level
loads. They no longer suggest running SafeBrowsing protocol on
subresource loads.
In this patch we introduce a pref to contorl the SafeBrowsing behavior
on subresource loads. The propose is to follow the suggestion from
Google to only run SafeBrowsing protocoal for top-level loads.
Differential Revision: https://phabricator.services.mozilla.com/D236156
This was needed to not pick up the custom option background / color in
the UA sheet when stylable select is enabled (so, on Windows).
Instead, restrict the checked styling in the UA sheet to listbox select,
and remove the special code.
Differential Revision: https://phabricator.services.mozilla.com/D238875
Before the regressing change, we were accidentally enabling pdf.js for
object/embed loads due to the parent process thinking the load has
failed, and the content process coming to a different conclusion.
This check ensures that we always enable pdf.js within object/embed
elements so that the pdfs are rendered as expected.
This does not impact pdfs loaded in other places which could otherwise
be handled externally, such as in iframes.
Differential Revision: https://phabricator.services.mozilla.com/D238844
The commit is fairly mechanical except for one important thing: it assumes that
SpatialTree::get_root_transform is equivalent to SpatialTree::get_relative_transform
using the root node passed as the parent index parameter.
Differential Revision: https://phabricator.services.mozilla.com/D238728
This patch adds a temporary coordinate space which will as a first step be
synonymous to world space, but will eventually become raster space. This is
Done to facilitate identifying what parts of the world-space computations
need to move into raster space.
Differential Revision: https://phabricator.services.mozilla.com/D238722
The Android test harness can take up to 10 minutes to timeout, so limit the
number of attempts. This allows test jobs to fail more gracefully on emulator
hangs instead of waiting for TaskCluster to kill the worker and delete most of
the debugging information that might help track down the hang.
Differential Revision: https://phabricator.services.mozilla.com/D238902
Example usage: ./mach manifest clean-skip-fails path/to/manifest/or/folder --os=linux --os_version=18.04 --processor=x86_64
With this command, you can specify one of the os name, version or processor. For example you can remove all conditions for the x86 architecture, or only linux version 18.04.
You can either specify a folder to recursively edit all manifests, or pass a specific manifest path.
Differential Revision: https://phabricator.services.mozilla.com/D238921
Currently jetstream 2 is (near) perma failing on the M2 machines on the
chromium-as-release application. This patch disables it for now.
Ideally, once we get jetstream 3 up we focus on maintaining that
instead. (bug 1943365)
Differential Revision: https://phabricator.services.mozilla.com/D237854
The label already wraps the input, so we don't need to also
have this attribute.
This was causing troubles in the console where the network
detail panel can be included multiple times; the label "for"
attribute would then refer to the first item with such id,
making its actual child input without label.
Differential Revision: https://phabricator.services.mozilla.com/D238916
When there is no tab opened, there is no active document running in the parent process.
But DevTools at least expect one to be functional. On desktop it is browser.xhtml.
Differential Revision: https://phabricator.services.mozilla.com/D235938
The label already wraps the input, so we don't need to also
have this attribute.
This was causing troubles in the console where the network
detail panel can be included multiple times; the label "for"
attribute would then refer to the first item with such id,
making its actual child input without label.
Differential Revision: https://phabricator.services.mozilla.com/D238916
