1. Adding a new attribute chromeContext in ConsoleEvent
2. Adding a new boolean attribute isFromChromeContext in nsIConsoleMessage
3. Sending IsFromChromeContext to the parent process
Differential Revision: https://phabricator.services.mozilla.com/D23330
--HG--
extra : moz-landing-system : lando
In Bug 1448408 ("Don't listen to visibility events"), it became possible to
close a tab without a visibility event to cause transactions to cancel. This
is a longstanding bug that was covered up by the visibility events. This patch
updates the cycle collection code to ensure that transactions get cleared out
safely, and we don't proceed to RejectTransaction (and subsequent code) on
already-cycle-collected objects.
Differential Revision: https://phabricator.services.mozilla.com/D25641
--HG--
extra : moz-landing-system : lando
This functionality has been replaced by beetmover. Also remove `mozharness.mozilla.aws`,
of which this was the only consumer.
Differential Revision: https://phabricator.services.mozilla.com/D25676
--HG--
extra : moz-landing-system : lando
Record the size of allocation in crashreporter to determine if these are
genuine small OOM or if something problematic has happened.
Differential Revision: https://phabricator.services.mozilla.com/D25152
--HG--
extra : moz-landing-system : lando
Only place reps can display a ::marker currently is in the animation panel.
Differential Revision: https://phabricator.services.mozilla.com/D25165
--HG--
extra : moz-landing-system : lando
So ::marker pseudo elements can be found via searching for "::marker" in the
markup view.
Differential Revision: https://phabricator.services.mozilla.com/D25109
--HG--
extra : moz-landing-system : lando
Prior to this the tab would crash with signature [@ nsINode::InsertChildBefore ]
if trying to insert before the ::marker.
Differential Revision: https://phabricator.services.mozilla.com/D25106
--HG--
extra : moz-landing-system : lando
At the moment when devtools.inspector.showAllAnonymousContent is true shadow
hosts with ::marker and ::before pseudos will stop showing the ::before and
won't show the ::marker either.
Differential Revision: https://phabricator.services.mozilla.com/D25058
--HG--
extra : moz-landing-system : lando
Changes:
- add new manifest file to define expected outcome for windows10-aarch64
Differential Revision: https://phabricator.services.mozilla.com/D25666
--HG--
extra : moz-landing-system : lando
On android, we want to use only RenderCompositorEGL for using sharedGL. Further RenderCompositorOGL does not work well with android SurfaceTexture.
Differential Revision: https://phabricator.services.mozilla.com/D25201
--HG--
extra : moz-landing-system : lando
Using the same flags as JSScript gives a consistent story of how to
handle flag preservation (in XDR and other cases). This also provides
consistent naming of flags which cover the same concept and will make it
simpler to inherit flags in de-lazification.
The LazyScript::packedFieldsForXDR concept exactly matches immutable
flags behaviour (which is on purpose). As a result of the split we don't
need to manually reset runtime flags in LazyScript::CreateRaw.
Differential Revision: https://phabricator.services.mozilla.com/D23402
--HG--
extra : moz-landing-system : lando
The Span abstraction lets us use range-based iteration and simplifies
changes if we move where the underlying data is stored.
Differential Revision: https://phabricator.services.mozilla.com/D23403
--HG--
extra : moz-landing-system : lando
As discussed on IRC, fixed is only used for prefs right now, and:
* We already copy the fixed size to the monospace font.
* We already serialize the fixed family as "monospace" in the style system.
So it already works somewhat inconsistently. Making it an alias makes it
work consistently.
Differential Revision: https://phabricator.services.mozilla.com/D24288
--HG--
extra : moz-landing-system : lando
To be more similar between Rust and C++. This introduces GenericFontFamily and
exposes that plus FontFamilyNameSyntax to C++, using that where appropriate
instead of plain uint8_t as we were doing.
As a follow-up, as discussed on IRC with Jonathan, we can remove the -moz-fixed
family, and turn it just into an alias of Monospace.
The only non-trivial change is the MatchType changes, but they're ok I think.
The code already assumed at most one CSS generic, and the struct still takes 8
bits. I've verified that the relevant tests are passing (though try is closed).
Differential Revision: https://phabricator.services.mozilla.com/D24272
--HG--
extra : moz-landing-system : lando
