Simple addition of one item to list of granted permissions, for Android P+; see bug 1553515.
Differential Revision: https://phabricator.services.mozilla.com/D55561
--HG--
extra : moz-landing-system : lando
Instead of setting MOZ_QUIET to hide the DOMWINDOW and DOCSHELL log messages, you
now must set a regular logging module to enable them. They are automatically enabled
on tests that rely on these messages are leak checking.
That module is DocShellAndDOMWindowLeak:3
One disadvantage of this change is that you cannot set MOZ_QUIET to hide these
messages when running those tests (primarily browser-chrome).
Differential Revision: https://phabricator.services.mozilla.com/D52413
--HG--
extra : moz-landing-system : lando
Some manifests get included by parent manifests (e.g [include:<child
manifest>]). The runtime of these manifests should be rolled into the runtime
of the parent manifest as that is how it will be run in CI.
This change also updates the runtimes files to incorporate this change.
Differential Revision: https://phabricator.services.mozilla.com/D55285
--HG--
extra : moz-landing-system : lando
Ensures child (aka included) manifests always run in the same chunk as their parent.
Differential Revision: https://phabricator.services.mozilla.com/D55284
--HG--
extra : moz-landing-system : lando
Also rename the key from 'ancestor-manifest' to 'ancestor_manifest' to be
consistent with other keys.
Differential Revision: https://phabricator.services.mozilla.com/D55283
--HG--
extra : moz-landing-system : lando
This patch rolls up all the required changes for this purpose. Since the
whole crash reporting flow must understand the new format it's not possible
to land this as separate patches as individually they would be broken. This
patch includes the following changes:
* Changes to the crash reporting machinery to write out annotations as JSON,
these includes changes to the DLL blocklist code that must be run at crash
time.
* Modifications to the crash reporter client so that it can read and
submit the new format; this includes platform-specific changes to the
Breakpad libraries it uses for submitting crashes.
* Modifications to the minidump-analyzer to understand and process the new
format correctly.
* Modifications to the crash manager to understand and process the new format
correctly.
* Modifications to GeckoView's crash handler to understand and submit the
new format correctly.
* Added new tests to cover the new format and modified existing ones to
accomodate the new one.
Differential Revision: https://phabricator.services.mozilla.com/D46848
--HG--
extra : moz-landing-system : lando
The next merge will mean esr68 doesn't have a confvars.sh that
references these lines, and the current config is broken due to the 'from'
lines not existing in mozilla-release
Differential Revision: https://phabricator.services.mozilla.com/D54756
--HG--
extra : moz-landing-system : lando
Bug 1594937 comment 2 provides an analysis on why it is OK to remove
css-multicol reftests.
The manual modifications in this patch are:
- Remove `os.path.join("css-multicol")` in import-tests.py.
- Remove css-multicol lines in failures.list
- Migrate geckoview only failures annotations (bug 1558509) in failures.list
to wpt ini files.
- Add fuzzy-if annotation to dom/tests/reftest/bug453105.html for Android.
(bug 1600534)
Others parts are generated by running import-tests.py on a wpt
repository with commit 15f199c91a72b0d51bf0a12b3b77827ecb5051ff.
Differential Revision: https://phabricator.services.mozilla.com/D52928
--HG--
extra : moz-landing-system : lando
Snapping glyph positions are an internal detail to a primitive. As such,
any snapping required must be taken into account when calculating the
local rect. That ensures that when the clip is applied, it doesn't cut
off parts of the glyph that would have been retained after snapping.
Differential Revision: https://phabricator.services.mozilla.com/D55348
--HG--
extra : moz-landing-system : lando
BrowserTestUtils.crashFrame now accepts additional `options`, with an argument `crashType` that may
take "CRASH_OOM" or "CRASH_INVALID_POINTER_DEREF"|null to specify the nature of the crash. The names
are taken from CrashTestUtils.jsm but this module cannot be imported as such as it has non-trivial
binary dependencies.
Depends on D54130
Differential Revision: https://phabricator.services.mozilla.com/D54700
--HG--
extra : moz-landing-system : lando
Automatic update from web-platform-tests
Add an initial test for wasm multi-value. (#17314)
--
wpt-commits: b8079efa83c28bc0fc9ec7ff18b20c0be23a4275
wpt-pr: 17314
Differential Revision: https://phabricator.services.mozilla.com/D55308
--HG--
extra : moz-landing-system : lando
Automatic update from web-platform-tests
Fixes click on inline element embedded in anchor inside <summary> breaks anchor.
Previous to this CL, clicking on an inline element embedded in an anchor placed
inside a <summary> tag will expand the <details> section instead of navigating to
the anchor's href. However, when the anchor is placed outside of <summary>,
it behaves correctly.
The error is caused by DOMActivate event generated by the inline element. As
DOMActivate bubbles up, it bypasses the anchor's event handler, reaches the
<summary>, and is handled there. Once DOMActivate is handled, the original
click event stops propagating and terminates. This behavior, however, differs
from when the anchor tag is placed outside of the summary. DOMActivate isn't
handled, and the original click event keeps bubbling up till it's handled by
the anchor.
DOMActivate event is deprecated:
https://developer.mozilla.org/en-US/docs/Web/API/Element/DOMActivate_event.
However, since blink still has code that depends on it, replacing it is outside
of the scope for this fix. Instead, this fix is for the anchor element to
handle the DOMActivate event as it bubbles up. The anchor event handler checks
the underlying event of DOMActivate and handles it if it's a click.
I also looked at an alternative fix by trying to prevent the DOMActivate event
from bubbling up. But calling event.stopPropagation() doesn't work as the
EventDispatcher::DispatchEventPostProcess doesn't check this status.
Bug: 538283
Change-Id: I11fb072faa0563279d43a28e5dc19cee89906bf0
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1928234
Reviewed-by: Kent Tamura <tkent@chromium.org>
Reviewed-by: Mason Freed <masonfreed@chromium.org>
Commit-Queue: Yu Han <yuzhehan@chromium.org>
Cr-Commit-Position: refs/heads/master@{#718552}
--
wpt-commits: fa8e9c41c5581439f93897e7c2fe674f803bfa21
wpt-pr: 20376
Automatic update from web-platform-tests
Remove test for RTL ms and add test for legacy lquote/rquote (#20426)
https://github.com/mathml-refresh/mathml/issues/120
--
wpt-commits: cce5582adbd6218dc617052fb3a609667b8faf49
wpt-pr: 20426
Automatic update from web-platform-tests
Make DecompressionStream error checking stricter
Error the stream if the input to DecompressionStream is truncated, or
there is junk after the end of the stream. This will help avoid
accidental loss of data.
Also add a thorough test of the behaviour when various fields of a
compressed stream are corrupted. Also test that errors are correctly
issued when the stream is truncated or has trailing junk.
BUG=1014422
Change-Id: I8aceeafd279b75d4fea76d7edca19024856417c0
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1928428
Reviewed-by: Yutaka Hirano <yhirano@chromium.org>
Commit-Queue: Adam Rice <ricea@chromium.org>
Cr-Commit-Position: refs/heads/master@{#718543}
--
wpt-commits: 157b71e48394fb63f91fa497be429c3543b0ab03
wpt-pr: 20359
Automatic update from web-platform-tests
[Trusted Types] make the idlharness.js tentative (#20166)
Almost all of the other tests are already tentative.
--
wpt-commits: b074e94e68233694e757e746b3a17d02553735ed
wpt-pr: 20166
Automatic update from web-platform-tests
Implement ServiceWorkerContainer.onmessageerror.
This patch implements ServiceWorkerContainer.onmessageerror and writes
WPT test for it.
chromestatus: https://chromestatus.com/feature/5699031592337408
Bug: 926102
Change-Id: I60e73dcb69de4a2876cc966dfa1809a30510b5f2
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1864409
Reviewed-by: Kent Tamura <tkent@chromium.org>
Reviewed-by: Matt Falkenhagen <falken@chromium.org>
Commit-Queue: Wei4 Wang <wei4.wang@intel.com>
Cr-Commit-Position: refs/heads/master@{#718507}
--
wpt-commits: c2ddea9d464a9ac5d31630b0b6f2a76b58e93489
wpt-pr: 19966
Automatic update from web-platform-tests
Do not attempt to push to epochs on forks (#20412)
GITHUB_TOKEN on forks only has read access to the repo. Fixes#20392.
--
wpt-commits: 886d5cabcafee3a9e0afaa146a65fb2f69ab42f1
wpt-pr: 20412
Automatic update from web-platform-tests
Remove size_x and size_z from VRStageParameters
The notion of a simple "size" for Stage Parameters/bounded was a WebVr
concept that did not carry over to WebXr. To simplify the mojom, move
the "conversion" of square stages (for those runtimes that only support
giving size x/z) down into a utility function in the device process.
Bug: 1017843
Change-Id: Ib050a7ea3655a3816f6008e82434435ecb2c4426
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1918037
Commit-Queue: Alexander Cooper <alcooper@chromium.org>
Reviewed-by: Daniel Cheng <dcheng@chromium.org>
Reviewed-by: Brandon Jones <bajones@chromium.org>
Reviewed-by: Klaus Weidner <klausw@chromium.org>
Cr-Commit-Position: refs/heads/master@{#718364}
--
wpt-commits: 0c3a6b1df6317496373d9ce3044d19704e9a6379
wpt-pr: 20278
Automatic update from web-platform-tests
[wpt] Enable experimental features for Edge Canary
PR #16920 added Edge Dev & Canary to Azure but only enabled experimental
web platform features for Dev.
--
wpt-commits: e0bd3bf113da6f7f0936c76871c5568cd32a88f5
wpt-pr: 20240
Geoff Brown
Punam Dahiya
Andreea Pavel
Cosmin Sabou
Ciure Andrei
Tom Ritter
Mihai Alexandru Michis
Andrew Halberstadt
Gabriele Svelto
Simon Fraser
Thomas Nguyen
Ting-Yu Lin
Emilio Cobos Álvarez
Andrew Osmond
Daniel Varga
David Teller
moz-wptsync-bot
Ms2ger
Henrik Skupin
octavian.negru
yu han
Frédéric Wang
Adam Rice
Philip Jägenstedt
Wei Wang
autofoolip
Robert Ma
Alex Cooper
haozhe
James Graham