- From: <bugzilla@jessica.w3.org>
- Date: Tue, 16 Jul 2013 21:02:27 +0000
- To: public-audio@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=21545 --- Comment #5 from Chris Rogers <crogers@google.com> --- (In reply to comment #4) > Thanks, I actually missed that part of the prose, but I agree that it should > have been removed. :-) > > My question was about this part of the prose (about the intrinsic value): > "When read, the .value attribute always returns the intrinsic value for the > current time." This basically has the same problems as the old > computedValue property, which is the problem I was talking about in comment > 2. It's not quite the same as computedValue, since at a specific time, it's a very straightforward mapping and it's possible to get the exact value based on the "scheduled" events (from setValueAtTime(), linearRampToValueAtTime(), etc.). -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Tuesday, 16 July 2013 21:02:29 UTC