W3C home > Mailing lists > Public > public-audio@w3.org > July to September 2013

[Bug 21545] AudioParam - min/maxValue, intrinsic value, computedValue

From: <bugzilla@jessica.w3.org>
Date: Tue, 16 Jul 2013 21:19:30 +0000
To: public-audio@w3.org
Message-ID: <bug-21545-5429-mZDq7GiSLy@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=21545

--- Comment #6 from Ehsan Akhgari [:ehsan] <ehsan@mozilla.com> ---
(In reply to comment #5)
> (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.).

But then we will face the same problems discussed in this message:
<http://lists.w3.org/Archives/Public/public-audio/2012OctDec/0623.html>...

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Tuesday, 16 July 2013 21:19:31 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:03:23 UTC