The Timing Object - A Pacemaker for the Web
summary
The talk explains the W3C Draft called the Timing Object, a web pacemaker designed to synchronize multiple timed sources (slides, audio, animations) that currently use different timelines and units. It presents a user-space implementation strategy including a TimingProvider that uses WebRTC to sync Timing Objects across devices, shows what can be done now without browser support, and encourages contributions to the spec so browser vendors may implement it natively.
AI-written summary · about
chapters (6)
- 0:00Introduction to timing objects
- 2:18Timing object in practice
- 6:06Developer experience challenges
- 8:07Broadcasting with timing objects
- 10:20Technical implementation details
- 12:11Q&A or summary
related talks
05mMeasuring what matters
29mTrusted Browsers for Uncertain Times
01h 02mWeb Performance Tuning with browser APIs
58mIt's Time to Talk About Time
48mPopcorn & Clocks; A story about scheduling in the browser
46mMaking the Web Rock: The Web Audio API
30mSave Time by Building Extensions for Your Browsers
37mGetting Close with the Web