W3C home > Mailing lists > Public > whatwg@whatwg.org > October 2015

Re: [whatwg] VIDEO and pitchAdjustment

From: Philip Jägenstedt <philipj@opera.com>
Date: Mon, 19 Oct 2015 15:55:16 +0200
Message-ID: <CAMQvoC=GF6tF5YNXaVG8B4FB9ARVBOnX6QHjLufn1RG5Qe3ibw@mail.gmail.com>
To: Domenic Denicola <d@domenic.me>
Cc: WHAT Working Group <whatwg@lists.whatwg.org>, Michael Enright <mike@kmcardiff.com>, Garrett Smith <dhtmlkitchen@gmail.com>, "robert@ocallahan.org" <robert@ocallahan.org>, Eric Carlson <eric.carlson@apple.com>
On Tue, Sep 1, 2015 at 11:21 AM, Philip Jägenstedt <philipj@opera.com> wrote:
> On Mon, Aug 31, 2015 at 9:48 PM, Domenic Denicola <d@domenic.me> wrote:
>> From: Eric Carlson [mailto:eric.carlson@apple.com]
>>>   FWIW, Safari supports negative playback rates on the desktop and on iOS.
>>> ...
>>>   The crash Garrett noted in Safari 8 is a bug that “only" happens with MSE
>>> content.
>> That's really helpful, thanks. Combined with Edge's keyframes-only support, it sounds like we should probably leave the spec as it is.
>> Do you have thoughts on a mozPreservesPitch equivalent?
> Should we just standardize HTMLMediaElement.preservesPitch, perhaps?
> Note that WebKit also has webkitPreservesPitch, but I removed it from
> Blink because it didn't actually do anything in Chromium.
> In both Gecko and WebKit it defaults to true. Is there anything else
> worth knowing before writing the spec for this?

I've filed a spec issue to make it so:

If there's any implementor interest in pitch control that goes beyond
(independently) or that, please file a separate issue.

Received on Monday, 19 October 2015 13:55:54 UTC

This archive was generated by hypermail 2.4.0 : Wednesday, 22 January 2020 17:00:36 UTC