- From: Brian Birtles via GitHub <sysbot+gh@w3.org>
- Date: Mon, 07 Aug 2023 09:10:08 +0000
- To: public-css-archive@w3.org
Yes, I agree that in the absence of any particular spec text here it should be when the event is enqueued. For what it's worth, we already have the concept of the [scheduled event time](https://drafts.csswg.org/web-animations-1/#scheduled-event-time) which we use for sorting events queued at the same time. I think we _could_ use that for the `timeStamp` if it's more useful to authors but I can't recall the implications of doing that. Would it be weird if animation and transitions events appeared to be out of order compared to other non-animation events based on their `timeStamp`s? Also, I think animation events from scroll-based animations have no scheduled event time so we'd have to decide what `timeStamp` they get. -- GitHub Notification of comment by birtles Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/9167#issuecomment-1667487658 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 7 August 2023 09:10:09 UTC