Implement chrome.i18n.getUILanguage including tests
Add API to content scripts
MozReview-Commit-ID: IcDlLj8Et73
--HG--
extra : rebase_source : 9996c7da79d3a132bce73b167dfea7031083ad3a
Also, an assert could have been incorrectly triggered, if eviction occurred on a source buffer while data was also being appended to it.
MozReview-Commit-ID: 6gVHZdbL07B
Currently endTime is calculated when getComputedTiming() is called. As a
result, the value returned there doesn't necessarily reflect what we are using
in the model. It would be more simple, consistent and useful if we simply
calculate this as part of GetComputedTimingAt and use it both internally and in
the result to getComputedTiming().
Before we go fixing endTime, we should add tests that activeDuration (which
endTime builds on) is being calculated correctly. (Spoiler: it wasn't, hence
parts 2 and 3 in this patch series.)
With the added tests in part 4 we crash without this change because we end up
trying to multiply an infinite iteration duration by a zero iteration count
which trips an assertion in StickyTimeDuration. Hence we fix this behavior
before adding the tests.
This patch brings the behavior of this method into line with the comment that
describes it and other methods in this class that have a similar test.
I discovered this bug while exercising this code from animation code and was
getting test failures due to returning -Infinity instead of the expected
Infinity.
This patch just simplifies the keyframe-effect tests so that we don't have to
repeat default values. This makes the tests shorter, easier to scan, and
easier to understand what is being tested.
In some cases we still repeat the default values in order to indicate that
we're testing that we get a particular default value.
These functions have been replaced by the shiftRightByScalar function which
behaves differently on signed and unsigned SIMD types.
Add some Uint32x4 tests to make up for the reduced test coverage.
MozReview-Commit-ID: 6BKSMR07zDa
With part 1, many more GCs are compartmental, so it is no longer a
good indication that there is heavy activity. If we don't regularly
try to shrink GC buffers, we don't decommit arenas enough, causing a
large regression in memory usage.
Specifically we make the following changes:
1) Remove WorkerSameThreadRunnable::PostRun, because it does exactly the same
things as WorkerRunnable::PostRun.
2) Always treat ModifyBusyCountFromWorker as infallible in terms of throwing
JS exceptions.
3) Change ExtendableFunctionalEventWorkerRunnable::PostRun to properly call
its superclass PostRun so we will correctly decrement the busy count our
PreDispatch incremented.
4) Document why some overrides of PreDispatch/PostDispatch are needed and
don't call into the superclass
This already had review, landed, and got backed out in Bug 1247375.
The backout was just a precaution; this should work fine, and be
scheduled just like android-b2gdroid is scheduled.
MozReview-Commit-ID: C3I7HOrcfFf
--HG--
extra : rebase_source : 015008a664851e93fea102c1515273aa030849cb
extra : source : 9f635a038f2c62eeb2310a81688169c66dcfb097
Mark Finkle
Michael Kaply
Ryan VanderMeulen
Carsten "Tomcat" Book
Gijs Kruitbosch
Randell Jesup
Jean-Yves Avenard
Wes Kocher
Chenxia Liu
bsilverberg
Jeff Gilbert
Lee Salzman
Kyle Huey
Sambuddha Basu
Thinker K.F. Li
Brian Birtles
Jakob Olesen
Andrew McCreight
Jordan Lund
Boris Zbarsky
Alexander Surkov
Ben Kelly
Eric Faust
Mike Hommey
Nathan Froyd
Paul Kerr [:pkerr]
Hannes Verschore
Justin Dolske
Nick Alexander
Morris Tseng
Kyle Machulis