Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[web-animations-1] Mapping between IDL and resolved/unresolved time values should be defined #4677

Open
bzbarsky opened this issue Jan 17, 2020 · 2 comments

Comments

@bzbarsky
Copy link

Consider the setter for https://drafts.csswg.org/web-animations/#dom-animation-currenttime

This takes a nullable double. It passes this nullable double to https://drafts.csswg.org/web-animations/#set-the-current-time which then passes it to https://drafts.csswg.org/web-animations/#silently-set-the-current-time

This then talks about whether time values are "resolved" or not. But nothing defines what that actually means in this case. Presumably the intent is that IDL null map to the "unresolved" state, but that needs to be defined. Perhaps what's needed here is a mapping from nullable double values to time values (and vice versa; it's not clear to me what happens with getters in this specification that are supposed to return a nullable double if a time value is not representable as a double, for example).

@birtles
Copy link
Contributor

birtles commented Jan 17, 2020

This then talks about whether time values are "resolved" or not. But nothing defines what that actually means in this case.

That's covered in https://drafts.csswg.org/web-animations/#time-values-in-the-programming-interface

it's not clear to me what happens with getters in this specification that are supposed to return a nullable double if a time value is not representable as a double, for example).

That part, however, is unspecified.

@bzbarsky
Copy link
Author

That's covered in https://drafts.csswg.org/web-animations/#time-values-in-the-programming-interface

Ah, I see. That was ... not very discoverable from the algorithm steps. :(

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants