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

Paint/presentation timestamps in performance APIs #1013

Open
1 task done
noamr opened this issue Nov 12, 2024 · 1 comment
Open
1 task done

Paint/presentation timestamps in performance APIs #1013

noamr opened this issue Nov 12, 2024 · 1 comment

Comments

@noamr
Copy link

noamr commented Nov 12, 2024

こんにちは TAG-さん!

I'm requesting an early TAG design review of Paint/presentation timestamps in performance APIs.

Aligning different paint-related timestamps in all the relevant performance APIs, by having one "interoperable" timestamp
and one coarsened platform-specific "VSync" (or "pixels on screen") timestamp.

Further details:

  • I have reviewed the TAG's Web Platform Design Principles
  • The group where the incubation/design work on this is being done (or is intended to be done in the future):
  • The group where standardization of this work is intended to be done ("unknown" if not known):
  • Existing major pieces of multi-implementer review or discussion of this design:
  • Major unresolved issues with or opposition to this design:
  • This work is being funded by:

You should also know that...

This has been discussed in the WebPerfWG in detail over the last 2 years.

@matatk
Copy link

matatk commented Jan 15, 2025

Hi @noamr, thanks for this review request also. We have been discussing paint/presentation timestamps today too, and have a couple of question about the explainer. We would really like to see the (end-)user needs made explicit. We'd also like to know about the alternatives that were considered, and why they found to be unsuitable, again this helps us weigh up the trade-offs. Thank you in advance for any further info you can provide.

Just in case it eases future reference: we put some background info on explainers in the other thread

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

5 participants