We could try to move the EnforcePendingTaskGuarantee() bit into
PeekIdleDeadline, but then we'd need to check HasReadyEvent() on
mDeferredTimersQueue and mIdleQueue before we possibly unlock the mutex under
PeekIdleDeadline, and it's not clear that that state cannot change once the
mutex is unlocked...
The EnsureIsActive() call at the end of GetIdleDeadlineInternal in the !aIsPeek
case only makes sense if there are in fact idle tasks available to run when
GetDeadlineForIdleTask is called, because otherwise it would incorrectly set us
active when we are not running any tasks.
Differential Revision: https://phabricator.services.mozilla.com/D49696
--HG--
rename : xpcom/threads/PrioritizedEventQueue.cpp => xpcom/threads/IdlePeriodState.cpp
rename : xpcom/threads/PrioritizedEventQueue.h => xpcom/threads/IdlePeriodState.h
extra : moz-landing-system : lando
The DebuggerVector has been associated with the GlobalObject via a private slot
referencing a wrapper JS object (DebugggerVectorHolder). Moving this data into
the JS::Realm instance removes complexity and avoids needing the holder.
Differential Revision: https://phabricator.services.mozilla.com/D49570
--HG--
extra : moz-landing-system : lando
Servo doesn't use this flag or -webkit- prefixed media queries, so no point in
doing this conditionally.
Differential Revision: https://phabricator.services.mozilla.com/D49508
--HG--
extra : moz-landing-system : lando
There's no effort to disable it any time soon, so I don't think it's useful to
keep the pref around.
Differential Revision: https://phabricator.services.mozilla.com/D49507
--HG--
extra : moz-landing-system : lando
This is effectively superseded by the hover / any-hover media queries, which
actually are standard, and is also causing trouble in the wild.
Not even the browser fronted uses it, so we should be able to just remove it
everywhere at once.
Differential Revision: https://phabricator.services.mozilla.com/D49506
--HG--
extra : moz-landing-system : lando
This function assumed property names are null-terminated. It's also wrong
in other ways: it let the string chars escape the AutoCheckCannotGC scope.
The easiest fix is to remove this unsound debugging function for now.
There are a lot of (other) extraName overrides so fixing this isn't
trivial.
Differential Revision: https://phabricator.services.mozilla.com/D49749
--HG--
extra : moz-landing-system : lando
This also adds a GetLinearStringCharAt helper function to simplify GetArrayIndexFromId.
Differential Revision: https://phabricator.services.mozilla.com/D49723
--HG--
extra : moz-landing-system : lando
This is where it should have been in the first place. Those attributes belong there.
Differential Revision: https://phabricator.services.mozilla.com/D49577
--HG--
extra : moz-landing-system : lando
2019-10-18 J.C. Jones <jjones@mozilla.com>
* lib/nss/nss.h, lib/softoken/softkver.h, lib/util/nssutil.h:
Set version numbers to 3.47 final
[7ccb4ade5577] [NSS_3_47_RTM] <NSS_3_47_BRANCH>
* .hgtags:
Added tag NSS_3_47_BETA4 for changeset d3c8638f85cd
[d5bd7be1bf2a]
Differential Revision: https://phabricator.services.mozilla.com/D49813
--HG--
extra : moz-landing-system : lando
Bug 1102175 Part 1 only handles HTML documents correctly because they
always have a body element (even if the <body> tag is not written
explicitly in the document). For SVG documents and all other documents
lacking <body> element, we always want to propagate mWritingMode from
the root element, which is our old behavior prior to Bug 1102175.
Note that mDocElementContainingBlock (i.e. nsCanvasFrame) is using
viewport's style, so we need to use the root element's computed style to
compute WritingMode for propagating.
Differential Revision: https://phabricator.services.mozilla.com/D49695
--HG--
extra : moz-landing-system : lando
I had authored the test as a mozilla-only WPT which means we can't trivially
run a check for whether parent intercept is enabled from within the test via
consulting with nsIServiceWorkerManager.
Differential Revision: https://phabricator.services.mozilla.com/D49787
--HG--
extra : moz-landing-system : lando
Today I reviewed wrong usage of this API.
It'd be good if it crashed in debug builds when misused.
Differential Revision: https://phabricator.services.mozilla.com/D49778
--HG--
extra : moz-landing-system : lando
Using cmd+F in the Console/Debugger after using the inspector will be caught by inspector code and will not show the panel's search ui.
Differential Revision: https://phabricator.services.mozilla.com/D49756
--HG--
extra : moz-landing-system : lando
Andrea Marchesini
Boris Zbarsky
harry
Logan Smyth
Mats Palmgren
Razvan Maries
Jonathan Kingston
Andreea Pavel
Emilio Cobos Álvarez
Paolo Amadini
Jan de Mooij
Dão Gottwald
Bogdan Tara
Jean-Yves Avenard
Jeff Walden
Ed Lee
Geoff Lankow
Sam Foster
J.C. Jones
Jason Laster
Cosmin Sabou
Andrew Sutherland
Maja Frydrychowicz
Gijs Kruitbosch
Mark Banner
Ting-Yu Lin
Nicolas Silva
Kashav Madan
Gabriel Luong
Rob Wood
Matthew Noorenberghe
Julian Descottes