mirror of
https://github.com/mozilla/gecko-dev.git
synced 2024-10-20 08:45:46 +00:00
99a1a632e3
In KeyframeEffectReadOnly::ComposeStyle we call StyleAnimationValue::Interpolate but assume that it always passes. That was true when that code was only used for CSS animations and CSS transitions since they check that their animation values can be interpolated before setting up segments. However, when we set up animations using the Web Animations API we don't perform that check so it is possible for this call to fail. In that case, we could just bail, but, according to CSS Transitions we should apply a 50% switch in this case: https://drafts.csswg.org/css-transitions/#step-types (In Web Animations, specifying this is an open issue. See: https://w3c.github.io/web-animations/#specific-animation-behaviors). Bug 1064937 tracks doing this in general (we'll likely need to mark various properties as being no longer unanimatable but instead as supporting discrete animation) but we can start to introduce it now. Later in bug 1245748, CSS animations and transitions will likely start using the same code path as the Web Animations API for setting up keyframes. As a result, unless we take care to add checks that the values we set are interpolable, the 50% switch behavior will begin to apply to CSS animations and transitions too at that point. Some concerns have been raised about possible web compatibility issues around the 50% switch behavior (see [1] and [2]). For CSS animations, Chrome already supports this behavior so it should be ok at least for CSS animations. When we switch CSS transitions over to the same code path, however, we will need to be careful to add checks that the transition endpoints are interpolable (we can investigate introducing this behavior to transitions as a separate bug that can be easily backed out / preffed off). Regarding the naming of the test added here, going forward we would like to restructure the tests under web-platform-tests to better match the structure of the Web Animations since that seems to be the convention there. However, this doesn't *quite* match the structure of the spec since there are upcoming changes to the spec in this area (e.g. renaming animation behaviors to animation types). However, it should be close enough that we don't have to move it around too much in future. [1] https://drafts.csswg.org/css-transitions/#step-types [2] https://bugzilla.mozilla.org/show_bug.cgi?id=1064937#c0 MozReview-Commit-ID: KcxILrckJg9 |
||
---|---|---|
.. | ||
activities | ||
alarm | ||
animation | ||
apps | ||
archivereader | ||
asmjscache | ||
audiochannel | ||
base | ||
battery | ||
bindings | ||
bluetooth | ||
broadcastchannel | ||
browser-element | ||
cache | ||
camera | ||
canvas | ||
cellbroadcast | ||
contacts | ||
crypto | ||
datastore | ||
devicestorage | ||
downloads | ||
encoding | ||
engineeringmode | ||
events | ||
fetch | ||
filehandle | ||
filesystem | ||
fmradio | ||
gamepad | ||
geolocation | ||
html | ||
icc | ||
identity | ||
imptests | ||
indexedDB | ||
inputmethod | ||
inputport | ||
interfaces | ||
ipc | ||
json | ||
jsurl | ||
locales | ||
manifest | ||
mathml | ||
media | ||
messagechannel | ||
messages | ||
mobileconnection | ||
mobileid | ||
mobilemessage | ||
network | ||
newapps | ||
nfc | ||
notification | ||
offline | ||
payment | ||
permission | ||
phonenumberutils | ||
plugins | ||
power | ||
presentation | ||
promise | ||
push | ||
quota | ||
requestsync | ||
res | ||
resourcestats | ||
secureelement | ||
security | ||
settings | ||
simplepush | ||
smil | ||
speakermanager | ||
storage | ||
svg | ||
system | ||
telephony | ||
tests | ||
tethering | ||
time | ||
tv | ||
u2f | ||
voicemail | ||
vr | ||
wappush | ||
webidl | ||
wifi | ||
workers | ||
xbl | ||
xml | ||
xslt | ||
xul | ||
jar.mn | ||
moz.build |