This removes the 'use-artifacts' mechanism in favour of fetches. There are a
few pieces here that need to land atomically:
1. Remove use-artifact related code
2. Call 'fetch-content' from the run-task script
3. Convert existing tasks on top of fetches (jsshell, python unittest)
4. Stop calling 'fetch-content' from toolchain setup tasks (as this now gets handled in run-task)
Depends on D2166.
Differential Revision: https://phabricator.services.mozilla.com/D2167
--HG--
extra : moz-landing-system : lando
On Api >=21 the Material DatePicker will have applied a Photon style.
Below Api 21 DatePicker will still be using spinners.
MozReview-Commit-ID: LuWP6C1o4Ej
--HG--
extra : rebase_source : 91eccfdeb0c4f17e9f0616fa25463d1b5558009a
On Api >=21 the Material TimePicker will have applied a Photon style.
Below Api 21 TimePicker will still be using spinners.
MozReview-Commit-ID: 2jZLPGCx4rI
--HG--
extra : rebase_source : a57376bf59077b6d64bcca8ba704ca1b6324383e
Previously we set this window size when restoring all default
values for a session during test teardown. Which means that
the very first test after the browser has been started will
run with the browser window default size.
This change enforces that all tests use the default window
size of 800x600.
MozReview-Commit-ID: Kiog3Ri2RJT
--HG--
extra : rebase_source : 971c1a17cdcc97d7880db8d8bdd50314369a2a91
This goes back to relying on rows being the same height.
Places where we replace the popup will likely not use the richlistbox,
and we no longer have code that changes the height or exceeds the maximum
number of visible children with a scrollbar, so we should be OK.
To determine the padding on the richlistbox and the height of the initial
row, I've used a promiseDocumentFlushed callback. It's possible this causes
flicker the first time the popup opens. I can't see any, but it's quite
possible I'm missing something.
Differential Revision: https://phabricator.services.mozilla.com/D2242
--HG--
extra : moz-landing-system : lando
IsComposited() does not reflect Visual selected by GLContextGLX::FindVisual()
which is used by WebRender which leads to shaped window rendering with WebRender.
IsComposited() is replaced by mHasAlphaVisual variable which is explicitly
set when we have an alpha visual and we don't need to use shape X11 extension.
MozReview-Commit-ID: 1kDLwkUyHte
--HG--
extra : rebase_source : 3a60fe8fd66f9e89bfcc729fe5e1fa9e1ce8920d
The test name was passed as a third argument to `ArrayBuffer.slice`, silently
ignored.
MozReview-Commit-ID: KHel7Bc2Qej
--HG--
extra : rebase_source : 4c5e300e140b18d62344cfec083bd39ea426f514
AV1 is still preffed off by default and is still disabled for Android and
32 bit Windows.
Differential Revision: https://phabricator.services.mozilla.com/D2362
--HG--
extra : moz-landing-system : lando
As explained in the comment of TextEditor::InsertWithQuotationsAsSubAction(),
it excepts that TextEditRules::WillDoAction() won't handle it. So, the
MOZ_ASSERT() should check |!handled|, not |handled|.
Caused this regression means that we do not have test to paste text into
<textarea>. Therefore, this patch adds the tests.
MozReview-Commit-ID: 2UUSVrmmNVK
--HG--
extra : rebase_source : 912d5428aeed83a7a46ec7e4a49c73c33dd7b295
The crash at this point may be caused by unexpected behavior change. However,
it's difficult to investigate what causes the crash. So, let's just avoid
the crash to investigate what unexpected behavior occurs.
MozReview-Commit-ID: P6YZTqP7zI
--HG--
extra : rebase_source : 24620884511aa3f1bc9fddb6049fcf6554150439
This new API allows to instanciate an actor in the parent process from actors running in the parent process.
The created actors are returned to the client from the actors running in content,
but after that, the client communicates directly with the created actors running in the parent process.
MozReview-Commit-ID: 5B3wRQ94UEx
--HG--
extra : rebase_source : 808ea31fe8a467d0185fc27056c6524873cddbce
So that LTO doesn't eliminate it, leaving the assembly from RR_objc_msgSend
unable to find it.
--HG--
extra : rebase_source : 457c2f4612fd3485d4e099b51e324a6e085016e6
Changes:
Pretty much all files contain changes to the order of events and properties... these are to stop subtle issues with events not being logged because not all properties were sent and some events were sent in the wrong order.
-devtools/client/framework/test/browser_devtools_api.js
- Renamed test-tool-1 and 2 because we need to include the panel names in Events.yaml and "-" is not allowed.
- devtools/client/framework/toolbox.js
- Removed unneeded const REGEX_PANEL.
- Generally shifted things around to ensure we send events from all codepaths.
- toolkit/components/telemetry/Events.yaml
- Changed telemetry event `"devtools.main", "enter"` to include all built-in panel names including "other."
MozReview-Commit-ID: 2G3Z9pzj1QC
--HG--
extra : rebase_source : bc691ae42b521e3a58c1a4aa9dbd455a3aa258a0
The language parameter of mozIPersonalDictionary is unused, so we should remove
this from parameter. Then, no one uses mLanguage member of mozHunspell now.
Differential Revision: https://phabricator.services.mozilla.com/D2349
--HG--
extra : moz-landing-system : lando
This adds a test with an extension signed by autorgraph with cose and pk7.
Differential Revision: https://phabricator.services.mozilla.com/D1855
--HG--
extra : moz-landing-system : lando
The tagging API is moving to the bookmarking API, this is part of it.
This will break the tags root open glyph in the Library, for now we don't have
an alternative, we'll re-evaluate in the future in bug 1477934.
Differential Revision: https://phabricator.services.mozilla.com/D2318
--HG--
extra : moz-landing-system : lando
__wrap_dlerror uses a single pointer for all threads, which means one
thread could get the dlerror result from another thread. Normally this
wouldn't cause crashes. However, because dlerror results come from a
per-thread buffer, if a thread exits and our saved dlerror result came
from that thread, the saved pointer could then refer to invalid memory.
The proper way to fix this is to use TLS and have a per-thread pointer
for __wrap_dlerror. However, instead of using up a TLS slot, this patch
keeps the single pointer for custom messages, and fallback to per-thread
dlerror call for system messages. While the race condition still exists,
I think the risk is acceptable. Even when races occur, they should no
longer cause crashes.
MozReview-Commit-ID: 4hGksidjiVz
--HG--
extra : rebase_source : 373000686c426b81ffd7cee88264e89b7a733957
Andrew Halberstadt
Gijs Kruitbosch
Mark Striemer
Dão Gottwald
Petru Lingurar
Henrik Skupin
Ian Moody
Tarek Ziadé
Julian Descottes
Paolo Amadini
Martin Stransky
Paul Adenot
Narcis Beleuzu
Dan Minor
Masayuki Nakano
Alexandre Poirot
Mark Banner
Mike Hommey
Michael Ratcliffe
Makoto Kato
Delphine Lebédel
Belén Albeza
Franziskus Kiefer
Marco Bonardo
Jim Chen