The problem was because on API >=26 the JobIntentServices used for the updater
functionality will be used by JobScheduler by binding to them.
But because they were set to run in a different process the binding was not
possible.
MozReview-Commit-ID: I8rbcoLyhyJ
--HG--
extra : rebase_source : 1bc423f6012aff6c9b0d960b046af04f32b8bd7b
Wrappers are per-compartment, not per-realm, so this will simplify the next patch. Also, considering the upcoming Realms proposal, it might eventually be possible to have multiple globals in a sandbox compartment.
GetOrCreateMapEntryForPrototype is the only caller where the object could be a CCW. However there cx and proto are same-compartment (GetOrCreateMapEntryForPrototype asserts this) so I changed that code to use JS::CurrentGlobalOrNull.
The optimization this code was working around has now been fixed.
Differential Revision: https://phabricator.services.mozilla.com/D2419
--HG--
extra : rebase_source : 586f19d9254c4aab88f54bd7b4122b613e1b39e8
extra : histedit_source : 4555f3e34c9863ae9db41f437f2c9ce6a3fed006
As discussed here:
https://github.com/w3c/csswg-drafts/issues/2691
We have a similar check in SetCurrentTime (with the exception that, according to
the spec, this behavior applies to either play OR pause pending, instead of just
pause-pending) so this patch tries to match the comment and format of that
check.
Differential Revision: https://phabricator.services.mozilla.com/D2410
--HG--
extra : rebase_source : 519a976424b021203a369926344c2174662e6156
PromptService will be informed when the screen is rotated and in turn it will
ask every Prompt shown to reset it's current layout.
For this, every Prompt will
- save it's current input value in PromptInput's mValue or similar field
already used for storing the default PromptInput value.
- create a new widget to be used in the new AlertDialog, with a new appropriate
layout for portrait / landscape. This is when the mValue field will be used
to initialize the new widget with the previous input.
MozReview-Commit-ID: L6eHyGNDt3d
--HG--
extra : rebase_source : ada913a8e6ada99a7d49eb47d1c64831a8f698da
This then can be used directly in the console, or passed to reps
and ObjectInspector so it can be called from there.
MozReview-Commit-ID: uQOiGuYbJK
--HG--
extra : rebase_source : a8a84b558dea69b7c2793b9e2d67a44a0809eb43
This saves about 37 KiB of memory across the UA style sheets.
MozReview-Commit-ID: EoZnlmyWwxX
--HG--
extra : rebase_source : 471fc63e521a4332bb92b4a73cd31a4bbe0b2dfe
Use adoptFd and detachFd so we don't duplicate FDs unnecessarily. Also
fix a bug where we didn't close the pref FDs.
MozReview-Commit-ID: Gugcyi4cj7V
--HG--
extra : rebase_source : 035f62d8ba4d1ec964d5b7f7556bae7164ab78b3
Unfortunately, EditorBase::SetFlags() is virtual call even though
AutoRestoreEditorState always works only with TextEditor (the method is
overridden only by HTMLEditor). And AutoRestoreEditorState is a hot path
when <input>.value or <textarea>.value is set a lot.
Fortunately, EditorBase::Flags() can be an inline method. So, we can make
both constructor and destructor of the class check if it'll change flags
actually.
Additionally, this patch fixes nsTextEditorState::PrepareEditor() too.
MozReview-Commit-ID: 7S4hLRRrbfB
--HG--
extra : rebase_source : 3c3e7438cd7e6c9853e5cf876277d7459b86c343
This is easier to understand as we don't have to round-trip the whole success and error states to the privileged wrapper which could potentially lead to stale state changes.
This is also much simpler for the basic-card-form as it doesn't need a lot of the complexity of the previous implementation.
* Move selectedStateKey from page to address-page since it doesn't apply to basic-card-page
MozReview-Commit-ID: B4kiZNWElGI
--HG--
extra : rebase_source : 183a3bd44ed33566fccdc024eabdccef83554d50
* Provide an cc-exp-year option to match cc-exp-month
* Make cc-number and cc-name required in the basic-card-form
* Disable the basic-card-page save button when the form is invalid.
MozReview-Commit-ID: LjzsnAKJp6R
--HG--
extra : rebase_source : 467fa09ea07c0234e1839b6dfd7e53375c118104
This should prevent introducing further delay when opening DevTools.
MozReview-Commit-ID: D9XDieFoU8a
--HG--
extra : rebase_source : f7a5309ed2f64ec358fee13068efd6da8acfbdd2
This is to avoid rendering for a frame or two without the menu item icons being
visible which causes flicker, particularly on lower-end machines.
MozReview-Commit-ID: Aq7AOkPwu9V
--HG--
extra : rebase_source : ee371cf848dcf39ec9f3cd9689268c3e9ef41c54
This is so that we can hook into the componentDidMount method.
MozReview-Commit-ID: 5NCDgvDPbe1
--HG--
extra : rebase_source : 3768f50b20d208f5d9bb5724194fcdc2927a873c
- Access nsISSLStatus directly as a member of nsITransportSecurityInfo
and nsISecureBrowserUI. This is part of a larger effort to consolidate
nsISSLStatus and nsITransportSecurityInfo.
- The TabParent implementation of GetSecInfo will always return null.
- Removed unnecessary QueryInterface calls
- Style adherence updates
MozReview-Commit-ID: Dzy6t2zYljL
--HG--
extra : rebase_source : 9c400bed3c9d29a186fc987c9bd0ffceb37bfd94
shindli
Narcis Beleuzu
Mark Banner
Petru Lingurar
Benjamin Bouvier
Makoto Kato
Jan de Mooij
Brian Birtles
Mark Hammond
Nicolas Chevobbe
prathiksha
Cosmin Sabou
Jeff Walden
Cameron McCormack
Jim Chen
Masayuki Nakano
Matthew Noorenberghe
Dipen Patel