public-webtiming@w3.org from February 2016 by author

François Daoust via GitHub

• Re: [timingobject] Access restrictions for timing objects (Monday, 29 February)
• Re: [timingobject] Management of range restrictions (Monday, 29 February)

Ingar Arntzen via GitHub

• [timingobject] Need another event type for the Timing Object? (Monday, 29 February)
• [timingobject] Multiple timing objects from same (online) timing provider (Monday, 29 February)
• [timingobject] Adding a clock object to the spec (Wednesday, 24 February)
• [timingobject] Access restrictions for timing objects (Wednesday, 24 February)
• [timingobject] Matching change events to update requests (Wednesday, 24 February)
• Re: [timingobject] Chaining timing objects (Wednesday, 24 February)
• [timingobject] Timestamps on update requests (Tuesday, 23 February)
• [timingobject] Management of range restrictions (Tuesday, 23 February)

Ingar Mæhlum Arntzen

• Feedback TimingObject spec (Tuesday, 23 February)

W3C Community Development Team

• currentTime reporting, Chromium on Android [via Multi-device Timing Community Group] (Thursday, 25 February)

Last message date: Monday, 29 February 2016 16:52:10 UTC