Issue metadata
Sign in to add a comment
|
Transition of the custom property doesn't do the 50% flip on duration
Reported by
gwhi...@gmail.com,
Oct 11 2016
|
||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/52.0.2743.116 Safari/537.36 Edge/15.14942 Steps to reproduce the problem: 1. Open http://jsbin.com/huxisomisa/edit?html,css,output 2. Mouse over the red box What is the expected behavior? The animation cannot be interpolated because you don't know the type of --prop, but you should still transition the custom property following the spec and flipping at 50% between that of red and green. What went wrong? The custom properties are not being transitioned since the type is not known. Did this work before? N/A Does this work in other browsers? N/A Chrome version: 53.0.2785.143 Channel: n/a OS Version: 10.0 Flash Version: Shockwave Flash 23.0 r0 Here is the text from the specification regarding custom properties: "Notably, they can even be transitioned or animated, but since the UA has no way to interpret their contents, they always use the "flips at 50%" behavior that is used for any other pair of values that can’t be intelligently interpolated"
,
Oct 12 2016
This is a separate feature request to transition on non-interpolable properties with a 50% flip. Spec: https://drafts.csswg.org/css-transitions/#step-types Resolving issue 644148 will help us achieve this but we should be implementing this for all properties, not just custom properties.
,
Oct 12 2016
,
Oct 13 2016
,
Oct 13 2017
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue. Sorry for the inconvenience if the bug really should have been left as Available. If you change it back, also remove the "Hotlist-Recharge-Cold" label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Oct 15 2017
,
Oct 16
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue. Sorry for the inconvenience if the bug really should have been left as Available. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Oct 17
|
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by shans@chromium.org
, Oct 11 2016Status: Duplicate (was: Unconfirmed)