[Bug 19676] timestampOffset accuracy

https://www.w3.org/Bugs/Public/show_bug.cgi?id=19676

Aaron Colwell <acolwell@chromium.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|REOPENED                    |RESOLVED
         Resolution|---                         |FIXED

--- Comment #19 from Aaron Colwell <acolwell@chromium.org> ---
Change committed that clarifies text mentioned in comment 18
https://dvcs.w3.org/hg/html-media/rev/1e6898152c5b

Please keep this bug closed. The main accuracy issues have been address and I
think we should wait until we have implementation experience before determining
whether further changes in this area are really needed. If an application is
really worried about errors introduced by timestampOffset, it can simply author
the content with the desired timestamps and not use the timestampOffset
mechanism at all. I believe the current mechanism is "good enough" for most
practical uses and I think we should wait until issues arise in actual
implementations before reopening this.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.

Received on Tuesday, 26 March 2013 17:54:39 UTC