-
Notifications
You must be signed in to change notification settings - Fork 27
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
[animation-frame-rate] attribute (FramesPerSecond or AnimationFrameRatePreset) frameRate; is surprising #86
Comments
First, let me explain why we made this proposal. We felt it was important that known values, those from the In order to allow this value to be round-tripped and shared across several animations, we felt it was important that it could be read back as-is without being computed. I think there are several ways this could be addressed:
There may yet be other options. |
I agree I find this very confusing. In particular, the actual values applied for { "auto", "low", "high", "highest" } seem like they would be hard to predict, and could easily vary from device to device or UA to UA. Is what is defined as "high" now going to change in the future if the expected high animation rate increases? I think if the only special case is making animations run as fast as possible, we could flip the value to be the interval between ticks rather than the framerate. This way, a developer could specify 0 to indicate to the browser to animate as fast as it can. |
Having an attribute which value is either a string or number (from JS point of view) is rather surprising.
The text was updated successfully, but these errors were encountered: