> I'm using only one offset value in my implementation as I'm still not sure why keeping both specified/computed offsets would be required. Right, it's mostly so that authors can roundtrip `null` offsets. e.g. ```js const anim = elem.animate({ left: ['0px', '100px'] }, 2000); anim.effect.setKeyframes(anim.effect.getKeyframes().concat('-50px')); ``` Without distinguishing between specified and computed, the returned keyframes would have resolved computed offsets and you'd lose the auto-spacing behavior. -- GitHub Notification of comment by birtles Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/5664#issuecomment-717201973 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-configReceived on Tuesday, 27 October 2020 12:13:27 UTC
This archive was generated by hypermail 2.4.0 : Tuesday, 5 July 2022 06:42:21 UTC