If you happen to be unfortunate enough to be testing changes that crash
xpcshell during the xpcshell self-tests, you'll be presented with error
messages like:
PROCESS-CRASH | test_child_assertions.js | application crashed [unknown top frame]
Crash dump filename: c:\users\task_1522676338\appdata\local\temp\xpc-other-mtot6h\cfaea928-e995-4430-baf9-0066c6b91be9.dmp
MINIDUMP_STACKWALK binary not found: z:\build\build\tools\breakpad\win64\minidump_stackwalk.exe
and then be told that, essentially, "your test failed because it
failed", which is unhelpful for figuring out what went wrong.
Apparently we had MINIDUMP_STACKWALK set at one point, and then it got
moved. Let's fix this situation by a) downloading minidump_stackwalk
out of tooltool (our test harnesses do this already); and b) pointing
MINIDUMP_STACKWALK at the correct location. With these changes, we can
once again get crash stacks if xpcshell (and probably a few other
things) fail their self tests.
Calling setResourceSubstitutions in the child process was causing an
error that prevented the prompt code from initializing in the child
process.
MozReview-Commit-ID: 9bE7jvglPPw
--HG--
extra : rebase_source : 87e622d52b97407aab7ec98d576b97b40c83bc5c
Enable the level 1 Mac Flash sandbox by default on Nightly,
controlled by pref dom.ipc.plugins.sandbox-level.flash.
Enable the level 1 Mac Flash sandbox as the default for
other plugins so that the sandbox is used for plugin
tests. (Flash is the only non-test plugin allowed by the
browser.) Controlled by pref dom.ipc.plugins.sandbox-level.default.
MozReview-Commit-ID: 37gLKpHCQwp
--HG--
extra : rebase_source : 941beccd351a3d97df3a1d409bb20d70df0bd5ef
This hides the changes in #20391 from Gecko builds that use the malloc_size_of crate.
Source-Repo: https://github.com/servo/servo
Source-Revision: c0bf170a11f61e721ee88d661fa0d97a464fbb69
--HG--
extra : subtree_source : https%3A//hg.mozilla.org/projects/converted-servo-linear
extra : subtree_revision : e2e29829d3301d5d290d549700e5caff00e99137
1. Add testShowWithXXX tests to test PaymentRequest.show() with
PaymentDetailsUpdate promise.
2. Improve the test case implementation by removing the redundant code.
--HG--
extra : histedit_source : 9c68ba8eb6ea4db7e6a158baf19f170b5736a9db
1. Add "optional Promise<PaymentDetailsUpdate> detailsPromise" as a parameter
of PaymentRequest.show() in PaymentRequest.webidl.
2. Let PaymentRequest inherit from PromiseNativeHandler, and implement the
ResolvedCallback() and RejectedCallback() to handle the PaymentDetailsUpdate
promise.
3. Update PaymentRequest.show() implementation. If PaymentDetailsUpdate Promise
is not nullptr, the show request would not be transferred to chrome process
immediately until the promise is resolved/rejected.
4. Update selectedShippingOption when requestShipping is true.
5. Change the PaymentMethod id validation sequence according to the spec.
--HG--
extra : histedit_source : e591c759037cce4f66701b2faa5ecbe01c00e246
There's no reason to ask GL since we should know the answers.
Also GL is tricky on how it handles these semi-deprecated queries.
Official GL stance is "don't ask questions you know the answer to".
MozReview-Commit-ID: F7p73eSTrYw
The CSS for page action icons doesn't handle fallback when only one variable
is defined, so for widgets that don't define their icons using CSS, we always
need to provide both.
MozReview-Commit-ID: 7UgMSVS3W6K
--HG--
extra : rebase_source : d8e38c256b45efecf04f1e20b5fcc6024e839f25
Nathan Froyd
Florian Quèze
Coroiu Cristina
Jason Laster
ui.manish
Csoregi Natalia
Andrea Marchesini
ffxbld
Narcis Beleuzu
Brindusan Cristian
Jim Chen
Cosmin Sabou
Thom Chiovoloni
Chris Manchester
Francesco Lodolo (:flod)
Brian Grinstead
Haik Aftandilian
Emilio Cobos Álvarez
Johann Hofmann
Servo VCS Sync
Josh Matthews
Noemi Erli
J.C. Jones
Eden Chuang
shindli
Nicolas Chevobbe
sotaro
Jeff Gilbert
Kris Maglione
Steve Fink
Matthew Gaudet
Michal Novotny
Tim Nguyen
Geoff Brown
David Major
Ben Kelly