That's what I meant, yeah. Ramps in web audio params don't go from the current value to the target value, they're treated as starting from whatever the previous

That's what I meant, yeah. Ramps in web audio params don't go from the current value to the target value, they're treated as starting from whatever the previously scheduled value was. In this case there wasn't a previously scheduled value, so I guess behavior was undefined and the browsers differed in how they handled it.