Bug 1329144 - Remove useless variable r=sebastian This variable is useless. So far we reference to a toolbar instance by local variable. Removing it makes less ambiguous. MozReview-Commit-ID: 8zrEKaB2H48

Bug 1337301 part 2 - modify the MarkAsContentSource() API; r=gerald MozReview-Commit-ID: 7hgZZUEvDEK

Bug 1337301 part 1 - Histogram for VIDEO_AS_CONTENT_SOURCE_IN_TREE_OR_NOT; r=bsmedberg,gerald MozReview-Commit-ID: HGA6yKbaFxE

Bug 973384 - Call |cb| before WebVTTListener::AsyncOnChannelRedirect returns. r=rillian MozReview-Commit-ID: 32nXdFpgCjg

Bug 1332206 - Don't clamp steps timing functions outside [0, 1] range; r=hiro MozReview-Commit-ID: AiSdxQvU2mj

Bug 1332206 - Add tests for non-clamping step timing function behavior; r=hiro MozReview-Commit-ID: 6L1RlrZQyMy

Bug 1332206 - Drop some unnecessary calls to pause(); r=hiro MozReview-Commit-ID: KCvFxh0DbQm

Bug 1332206 - Move invalid easing tests to the appropriate interface tests; r=hiro MozReview-Commit-ID: 4PYlZvwRD1L

Bug 1332206 - Move tests for timing functions with inputs outside [0, 1]; r=hiro These should be part of the tests for the transformed distance since that is currently the only place where they can occur. This patch also revises the test descriptions somewhat to make it clearer what is being tested. MozReview-Commit-ID: D4YfAiZUBYR

Bug 1332206 - Add missing tests for steps-end in delay phase; r=hiro (Once we remove the special clamping behvaior later in this patch series, the added test here will fail if we don't add special handling for the case when the progress is zero and we are in the delay phase.) MozReview-Commit-ID: Dnon2soE1Se

Bug 1332206 - Drop checking width in step timing function tests; r=hiro We only use this once to test the timing function when applied to a keyframe. Now that we have tests for this in animation-model/keyframe-effects/effect-value-transformed-distance.html we can drop the check here and simplify these tests considerably. Also, 'progress' is always set so we can drop the check for an undefined value. MozReview-Commit-ID: 39ajHZBRWBf

Bug 1332206 - Drop step timing function for compositor animations; r=hiro This seems like a Gecko-specific test and even then it's not clear why we expect the result could be different in this case. MozReview-Commit-ID: Ix8jZLobwcA

Bug 1332206 - Move step timing function tests; r=hiro MozReview-Commit-ID: HdBtYjbL2la

Bug 1332206 - Add tests for keyframe easing; r=hiro MozReview-Commit-ID: HkWyQXjr7P5

Bug 1332206 - Simplify invalid easing tests; r=hiro This doesn't need to be an array of objects when a simple array would do. MozReview-Commit-ID: 1gtdhG5RPSy

Bug 1332206 - Rename effect easing tests to easing tests; r=hiro These tests are generic enough to be used for either effect easing or keyframe easing. MozReview-Commit-ID: 5cpnkiCv0z1

Bug 1332206 - Rework tests for linear-equivalent cubic-bezier timing functions from effect-easing.html; r=hiro The purpose of these tests appears to be to check that a linear-equivalent cubic-bezier timing function (e.g. 'cubic-bezier(0, 0, 0, 0)') does not affect the result such as clamping values out of the [0, 1] range. This test really is testing the calculation of the 'transformed distance' in the "The effect value of a keyframe effect" so we move the test there and rework it to more clearly test what it is intended to cover. MozReview-Commit-ID: 9sEr7MlVZKL

Bug 1332206 - Move tests for effect easing to timing-model; r=hiro This set of tests are really just testing that we apply the timing function to the animation effect so they belong in the appropriate part of the timing model tests (and should check getComputedTiming not getComputedStyle). I've also started to update tests to ES6 where appropriate since it seems arrow functions, template literals, etc. are all supported on all UAs that are implementing or likely to implement Web Animations. MozReview-Commit-ID: 3kXao0Xi0BA

Bug 1332206 - Tidy up visibility tests to use single quotes and drop periods at end of test assertions; r=hiro MozReview-Commit-ID: E5jloD49U0a

Bug 1332206 - Split effect value tests into separate files; r=hiro The file naming here is based on the existing effect-value-context.html file, i.e. we break up all the tests for the calculation the effect value into separate files named effect-value-***.html. MozReview-Commit-ID: LY46vX3mHh7