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 19:15:46 +0000
To: public-audio@w3.org
Message-ID: <bug-21545-5429-VaGyZmPbkG@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=21545

--- Comment #3 from Chris Rogers <crogers@google.com> ---
(In reply to comment #2)
> Following up on this bug, the prose for the intrinsic value is currently
> saying that when read, AudioParam.value should return the current instrinsic
> value based on the current time.  This is similar to what the computedValue
> attribute used to return, and there are some concerns about this (see
> <http://lists.w3.org/Archives/Public/public-audio/2012OctDec/0623.html> for
> example.)
> 
> Chris, are you planning to make AudioParam.value a simple value which can be
> get/set like any other attribute?

The .computedValue attribute was removed awhile ago as a publicly available
attribute in the spec.  There is still a section talking about
"computedValued", but only as an implementation detail to describe that this is
the final internally computed value that will be used by the DSP algorithm.

I now see that I forgot to remove a couple of sentences relating to this - now
fixed:
https://dvcs.w3.org/hg/audio/rev/4f8714b58ef1

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

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:50:10 UTC