You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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.
こんにちは 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.
paintTime
andpresentationTime
in performance APIs mozilla/standards-positions#1110Further details:
You should also know that...
This has been discussed in the WebPerfWG in detail over the last 2 years.
The text was updated successfully, but these errors were encountered: