Gonk, Android, and the generic cross-compilation setup all were using a
different yet similar way to prefix the toolchain. The latter was even
wrong, since the target and target alias usually don't match actual
toolchain prefixes (which don't include the machine part of the target).
Note that this removes force-setting cross_compiling to yes in
old-configure, which wasn't working because every AC_TRY_COMPILE
resets it with $ac_cv_prog_cc_cross or $ac_cv_prog_cxx_cross.
Recent config.sub better handles all the broken android triplets (which
would have worked around bug 1257793), and added the -ios variant that
we've been relying on since bug 1257051, but that bug 1257648 broke by
using config.sub, which didn't support it)
The new config.guess interestingly now returns pc instead of unknown as
maching type on linux, which will, unfortunately, make objdir names
change when they are not manually set.
_DefineDataProperty was used to ensure that modifying Array's setter wouldn't
impact sorting, however, this is both not necessary and against the spec.
--HG--
extra : rebase_source : f7d1301abf3207e2091f4c1e3b7e3949c0961ec8
In some of these cases, this increase isn't strictly necessary, because we only
check state immediately after creating the animation, before it could have
completed (regardless of its duration). Still: we should consistently use long
durations for any animations that aren't expected to complete during the test
run, because short durations might accidentally get copypasted into new tests
where they might cause intermittent failures.
MozReview-Commit-ID: 8wSRqHMI12L
--HG--
extra : rebase_source : 12e6a054dce047351b06e064bcedd9cdec58150f
MozReview-Commit-ID: HXLTybsEb4R
This patch exchanges all old and deprecated API calls with the ones in PlacesUtils. As a side-effect we can also condense some other code by using promises.
--HG--
extra : rebase_source : 36c0ca5704c6f94734bc0796e97cabf776bf42f5
Before this patch, the default policy for the use of SHA1 in certificate
signatures was "allow all" due to compatibility concerns.
After gathering telemetry, we are confident that we can enforce the policy of
"allow for locally-installed roots" (or certificates valid before 2016) without
too much breakage.
MozReview-Commit-ID: 8GxtgdbaS3P
--HG--
extra : rebase_source : d1bed911f2d5d40229ea06556fee0848668e98b6
This patch makes NativeProperties variable-length and reduces static data by
110,336 bytes on 64-bit, and half that on 32-bit.
MozReview-Commit-ID: 2etZ5AnEhgO
--HG--
extra : rebase_source : 6a167b64df7da3c6940114782fe08337f04a694d
https://www.w3.org/TR/css-pseudo-4/#first-letter-pseudo
"Punctuation (i.e, characters that belong to the Punctuation (P*)
Unicode general category [UAX44]) that precedes or follows the first
typographic letter unit must also be included in the ::first-letter
pseudo-element."
nsCaret::GetFrameAndOffset may return a text frame also when aParentNode
is the container of a text node and aOffset is just after it. In this
case we also want CARET_ASSOCIATE_AFTER if the text ends with
a significant newline. (follow-up from bug 1258308)
Even if there is not a traditional race between uses of the protected data and
the `ExclusiveData<T>`'s destruction, the thread running the destructor has no
guarantee that its cache is up to date with changes already made by other
threads. The new acquire and release surrounding the destructor ensures that the
destructor doesn't run on stale cache lines.
MozReview-Commit-ID: 1fewYlhuEIa
--HG--
extra : histedit_source : 962af09fc4dffa7974f94941e442b884ad4d6f62
This commit adds OOM checks that were missing to
`GetDefaultBreakdown`. Additionally, it replaces uses of `js_new<T>` with
`cx->new_<T>` so that OOMs are automatically reported on the context.
MozReview-Commit-ID: KUqWdjSBLKn
