This patch uses the functionality introduced in bug 1366711 to launch the
pingsender without showing its console window nor a mouse throbber. This also
reverts the pingsender into a console application.
MozReview-Commit-ID: BTcqAkR9UKB
--HG--
extra : rebase_source : bf982d54a5a82c660ab980025498a624730520bf
Code search indicates that it is used neither internally nor in any
addon. It should be safe to remove.
MozReview-Commit-ID: K3dBoydIwGk
--HG--
extra : rebase_source : 984aee342b0006af94eec1cd7fce123bccea4bd7
Code search indicates that this is not used internally, and the only
addon uses this is Breadcrumbs, which hasn't been updated since 2009,
thus it is already not compatible with current Firefox.
MozReview-Commit-ID: 1lUs7ceaaE1
--HG--
extra : rebase_source : 87060c33291ba415c6c70767c132c4a5b74d29fb
Selection::SelectFrames() is an internal method of Selection, it always handles positioned range. So, neither aRange->GetStartParent() nor aRange->GetEndParent() never returns nullptr.
Additionally, nsIContentIterator::GetCurrentNode() shouldn't return nullptr until IsDone() returns true.
MozReview-Commit-ID: 1IS4nMLukt
--HG--
extra : rebase_source : a4eee06580519adf2233f535abfdf50ac8730a19
This also moves the result of deciding whether to recascade from the RestyleData into the RestyleHint.
Reviewed in https://bugzilla.mozilla.org/show_bug.cgi?id=1367647.
Source-Repo: https://github.com/servo/servo
Source-Revision: aa4aef379d0962523409668dbc301f6dc8138706
--HG--
extra : subtree_source : https%3A//hg.mozilla.org/projects/converted-servo-linear
extra : subtree_revision : e2d2e62ab8c60cc13ea288498a334c3d2b9fe91b
Test to confirm valid 'inherit' value of -moz prefixed properties during
animation. This also means to confirm the algorithm of clone_XX methods
of stylo.
NOTE: This file should have only animatable properties that have '-moz' prefix.
In this patch, appends following properties.
* -moz-box-align
* -moz-box-direction
* -moz-box-orient
* -moz-box-pack
* -moz-float-edge
* -moz-orient
* -moz-osx-font-smoothing
* -moz-user-focus
* -moz-user-input
* -moz-user-modify
* -moz-window-dragging
MozReview-Commit-ID: GfBfMkvfgGm
--HG--
extra : rebase_source : f2e220ccc0c6864ad15416a2cda470f64eeb62be
nsIDOMText is old interface and it needs QI to access node etc. So we should use Text etc.
MozReview-Commit-ID: 7VrTrE0p2Q9
--HG--
extra : rebase_source : baa6601708d4b71e624a4dc893cc413d7743dbeb
This function was initially added in bug 1304792, but its only usage was
later removed in bug 1352763.
The name conflicts with another function (which basically does the same
thing without refcount manipulation) I'm adding in a later patch, so I
have to remove it first.
MozReview-Commit-ID: 6fO4EDJUg7R
--HG--
extra : source : 3f7f683b64f42d22a09138cfe01d8ca42d435aa3
@import rules can only exist in top level rule lists, and we need the
stylesheet to construct the import rules.
MozReview-Commit-ID: APCyGW8re8f
--HG--
extra : source : b9b78672249f390d56d71fa46dfa4b4cd49ef182
It seems no one actually care about the order of the list, and the order
is completely meaningless if the script insert new @import rules.
Changing the order makes inserting faster, and make it easier for later
patch to get the latest inserted child sheet.
MozReview-Commit-ID: 72eKqVoPbZ7
--HG--
extra : source : 6b2b471b993f33f9d06af01e4863cd6c5d34ce3a
Initialization of mChildSheet will be implemented in a later patch.
MozReview-Commit-ID: 3SX3GJEhpBQ
--HG--
extra : source : e45a434d0e9d2e2d8c628b17c2074b8f5de4b1ee
This is the Servo side change of [bug 1352968](https://bugzilla.mozilla.org/show_bug.cgi?id=1352968).
Source-Repo: https://github.com/servo/servo
Source-Revision: 085743560caffc0d25c7225ac979a857efd82155
--HG--
extra : subtree_source : https%3A//hg.mozilla.org/projects/converted-servo-linear
extra : subtree_revision : 446fee2038c6da63ed23b4b162fd619e12cbc650
This patch do 6 things. They are related so I put them in the same patch.
1. Extract MmaEvent Name
2. If MMA is diabled, don't send event.
3. Add check before sending 'Set Default Borwser' deep link
4. Add user attribute for delay messaging focus install status.
5. If the user pref off at runtime, we ask Leanplum to stop and prevent our app sending event to Leanplum.
6. Fix proguard. Only keep necceary files.
MozReview-Commit-ID: APEmr1JXBLH
--HG--
extra : rebase_source : 35b54c11004905c950c1ace84507554a2e1b4f39
This should fix [bug 1331530](https://bugzilla.mozilla.org/show_bug.cgi?id=1331530).
Source-Repo: https://github.com/servo/servo
Source-Revision: 76daf462956a50c3348b6dac516d5f013355a88b
--HG--
extra : subtree_source : https%3A//hg.mozilla.org/projects/converted-servo-linear
extra : subtree_revision : acfcdeb21b6948f100e7d06f43dface47ea24056
The l10n builders don't have the access to secrets that the regular
builders do, so don't expect Leanplum SDK secrets in l10n repacks.
Since MOZ_ANDROID_MMA requires a Leanplum SDK token file, we'd also
need to opt-out of MOZ_ANDROID_MMA in this case. I interpret this to
show that the update channel is not the right mechanism with which to
enable the Nightly-only MOZ_ANDROID_MMA feature; it's better to just
opt-in for Nightly builds. This patch does that.
MozReview-Commit-ID: 81WTFjsT7br
--HG--
extra : rebase_source : 5338fb33c13733335ed4f9e58cc3ea969d6e705a
This is the equivalent of MOZ_INSTALL_TRACKING, but for MMA (Mobile
Marketing Automation) using the Leanplum SDK.
To test this locally, add lines like:
export MOZ_ANDROID_MMA=1
ac_add_options --with-adjust-sdk-keyfile=/path/to/adjust-sdk-developer.token
MOZ_ANDROID_MMA depends on MOZ_NATIVE_DEVICES and MOZ_ANDROID_GCM,
since Leanplum requires Google Play Services library that those flags
are a proxy for and enable, respectiviely.
We want to enable MOZ_ANDROID_MMA in Nightly, but only for
MOZILLA_OFFICIAL builds. Since MOZILLA_OFFICIAL is still defined in
old-configure.in, we can't interrogate it in
mobile/android/moz.configure, and therefore we enable using the
automation mozconfigs.
MozReview-Commit-ID: 1tiToeyH5Hx
--HG--
extra : rebase_source : f85706c5a0911c7d2edc109d8c47ecc1c1bc6ffc
This makes it easier to tell what's going on; whether we've created a
MediaKeySystemConfiguration which can persist state.
MozReview-Commit-ID: L4dbmMVYhsM
--HG--
extra : rebase_source : e47e60f5091b6b5477b2c8bd63ba408922706082
This will enable us to re-use the logging code in MediaKeySystemAccess to log
the configuration we end up instantiating the MediaKeySystemAccess with.
MozReview-Commit-ID: AMnauhMLJ1R
--HG--
extra : rebase_source : a2dfeb7b263108ac1c60bfe2f47755e0a73d6324
We want requests for MediaKeySystemAccess with persistentState to be rejected
if the window is in Private Browsing mode. This is primarily so that users in
Private Browsing mode don't unknowningly use up their "device limits"; some DRM
streamers have limits on the numbers of unique devices that can be
provisioned/used in a given time period, and the device ID is persisted in the
persistent state. So if we're flushing that state, the user will use up one of
their device quota on every new session, and quickly hit their limit, and be
unable to continue watching DRM video.
MozReview-Commit-ID: JWNO1kcU2ST
--HG--
extra : rebase_source : ad4e22629acfdd82aff8ead764949939726adbf4
