-
Notifications
You must be signed in to change notification settings - Fork 32
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
Consider to have a separate spec for Long Animation Frame API #132
Comments
That makes general sense. Here's a suggested plan:
I'd love y'all's thoughts on the above! |
-frames or -frame ?
yes
No need for a change, it's also a spec split. A WG CfC will be sufficient. |
This was referenced Mar 11, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
At the moment Long Animation Frame and Long Task are both included in the same spec, I think this could potentially lead to the same issue as LCP. When one implementer only implements half of the spec and they only want to adopt half of the spec to the charter.
Should we consider to have a standalone spec just for Long Animation Frame?
The text was updated successfully, but these errors were encountered: