- From: youennf via GitHub <sysbot+gh@w3.org>
- Date: Thu, 31 Oct 2024 15:22:26 +0000
- To: public-webrtc-logs@w3.org
The following commits were just pushed by youennf to https://github.com/w3c/mediacapture-record: * Update https://w3c.github.io/mediacapture-record/#dom-blobeventinit-timecode. The spec text was unclear. From offline discussion with the original spec author it's believed that the intent of the spec language was meant to convey that the first produced timecode would contain an absolute timestamp. However, it's not clear what usecase is unlocked by that, as the user can construct their own absolute timestamp with performance.now() on event reception. This ignores the fact that the event handler can execute delayed, but since it's not clear what problem this fixes, this PR simply makes the timestamp sequence start with zero instead. Fixes #222. by Markus Handell https://github.com/w3c/mediacapture-record/commit/6d89746e8e5cf2eecea5ab6553a0fc174bb71cce * Address reviewer suggestion. Co-authored-by: Harald Alvestrand <hta+github@alvestrand.no> by handellm https://github.com/w3c/mediacapture-record/commit/5cf4f29d7fadcf07d0842a2851b78adb9a31adab * Merge pull request #223 from handellm/timestamp Update https://w3c.github.io/mediacapture-record/#dom-blobeventinit-timecode. by youennf https://github.com/w3c/mediacapture-record/commit/dbe375f40dc22a446e3eae65163e39e466e686bd -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 31 October 2024 15:22:27 UTC