Container Timing API

[keithamus]

Request for Mozilla Position on an Emerging Web Specification

• Specification title: Container Timing
• Specification or proposal URL (if available): https://github.com/bloomberg/container-timing
• Explainer URL (if available): https://github.com/bloomberg/container-timing
• Proposal author(s) (@-mention GitHub accounts): @jasonwilliams @jdapena
• Caniuse.com URL (optional): N/A
• Bugzilla URL (optional): https://bugzilla.mozilla.org/show_bug.cgi?id=1940240
• Mozillians who can provide input (optional): @sefeng211
• WebKit standards-position: Container Timing API WebKit/standards-positions#442

Other information

[keithamus]

Relates to #192 - element timing API

[tomrittervg]

Because I know someone will ask me, as with most "We'd like to add a timestamp" proposals, Firefox's timer resolution protections are comprehensive, and all timestamps will (or should, otherwise its a bug) respect our settings on both jitter and time resolution, adjusting the resolution based on user settings (RFP), preferences (about:config values), and site permissions (SAB-allowed or not).