On Fri, 4 May 2018 14:32:20 -0400, Boris Zbarsky wrote:
> On 5/4/18 3:34 AM, Karl Tomlinson wrote:
>> Not sure I understand your question, but the observable behavior
>> described by this section, or specifically "Before an AudioNode is
>> deleted, it will disconnect itself from any other
On 5/4/18 3:34 AM, Karl Tomlinson wrote:
Not sure I understand your question, but the observable behavior
described by this section, or specifically "Before an AudioNode is
deleted, it will disconnect itself from any other AudioNodes"
Right. So that observably influences the sound produced or
Boris Zbarsky writes:
> So if there is in fact a problem still remaining, convincing Alex
> that it's there is pretty valuable. Having him convinced it
> doesn't exist is actively harmful as far as getting it fixed goes.
Thank you. Alex sounds like a very valuable person to get on side.
We
On 5/3/18 6:21 PM, Karl Tomlinson wrote:
I didn't understand why he was highlighting "order of object
tear-down", nor why he was implying that only "VERY fine-grained"
knowledge was a problem.
Alex, depending on whether he's speaking with his TAG hat or Google hat
on, is either trying to
I read the threads you referenced and the latest spec, and I think you're
absolutely right about everything :-).
On Fri, May 4, 2018 at 10:21 AM, Karl Tomlinson wrote:
> Thank you for taking a look, Boris. I'm quite unclear how any of
> the changes proposed in the [[March
On Friday 2018-05-04 10:21 +1200, Karl Tomlinson wrote:
> Is having web specifications try to describe object lifetimes
> helpful, or is it just over-prescribing?
>
> Should specifications instead just focus on observable behavior,
> and leave it to implementations to optimize and to reclaim
>
Boris Zbarsky writes:
> On 5/2/18 5:21 AM, Karl Tomlinson wrote:
>> [[AudioNode Lifetime]] https://github.com/WebAudio/web-audio-api/issues/1471
>
> I've read through that thread, but I'm still a little unclear on
> where thing stand. With the latest proposal, can there be
> observable
7 matches
Mail list logo