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
--HG--
extra : rebase_source : 778034d7bd02431cb2ebaee7da7e1fe3f745c400
(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
--HG--
extra : rebase_source : c1045d168211bf73ff28102e7177653eedc8b6f2
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
--HG--
extra : rebase_source : 548fcfadd97888be126f746bcd1b0113156ce034
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
--HG--
extra : rebase_source : 9068b8bbd3efc30a588d704eaee3d172824f176c
This doesn't need to be an array of objects when a simple array would do.
MozReview-Commit-ID: 1gtdhG5RPSy
--HG--
extra : rebase_source : ebe92fc91cd94d3b54277810e300b6bba570c8c5
These tests are generic enough to be used for either effect easing or keyframe
easing.
MozReview-Commit-ID: 5cpnkiCv0z1
--HG--
rename : testing/web-platform/tests/web-animations/resources/effect-easing-tests.js => testing/web-platform/tests/web-animations/resources/easing-tests.js
extra : rebase_source : eef374243f4a03c7a1fa8f01d04bf0457177848a
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
--HG--
extra : rebase_source : 290f5d875db32f9396264b76652c02d8b2976bee
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
--HG--
extra : rebase_source : dd46913675b83fcb4c8c263b02c4d1c9cc23855f
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
--HG--
rename : testing/web-platform/tests/web-animations/animation-model/keyframe-effects/the-effect-value-of-a-keyframe-effect.html => testing/web-platform/tests/web-animations/animation-model/keyframe-effects/effect-value-overlapping-keyframes.html
rename : testing/web-platform/tests/web-animations/animation-model/keyframe-effects/the-effect-value-of-a-keyframe-effect.html => testing/web-platform/tests/web-animations/animation-model/keyframe-effects/effect-value-visibility.html
extra : rebase_source : bdd2ce7259de59d802b6e45800b238df520ec648
The test-info command provides a report of test results for a named
test on a set of branches over a time period. Test results include
a pass/fail summary, average/min/max duration, and open bugs.
Branches and time period can be modified with optional parameters.
THA was removed in Bug 1196988.
After Bug 1235869 and Bug 1238079, Firefox Marketplace apps are at most
supported by B2G, and B2G only code doesn't need to be in m-c anymore.
MozReview-Commit-ID: DAx5lRdYQo0
--HG--
extra : rebase_source : e7fc32195def3acda2d53a6e3cb969f1e8a9a9a1
Fork from bug1336309 comment2, unmuteTab used "M" as access key, but we should
change to "m" because the character is lowercase in the label.
MozReview-Commit-ID: 3q2luFLbFlQ
--HG--
extra : rebase_source : ec88c660372fc41f10b3c20faa2d4d6e20f11a65
For components also referencing it in code, see the blockers of bug 1336311.
MozReview-Commit-ID: 4tUZ24HKBWy
--HG--
extra : rebase_source : ec16149f525b9b7eaca7f96f1369929d21497121
