new MediaMetadata() should not fail |
|||
Issue description
Chrome Version : 57.0.2951.0
OS Version: 9086.0.0
Steps to reproduce:
Open DevTools and type "new MediaMetadata();"
What is the expected result?
A stunning rainbow crosses the sky.
What happens instead of that?
VM62:1 Uncaught TypeError: Failed to construct 'MediaMetadata': 1 argument required, but only 0 present.
at <anonymous>:1:1
According to https://wicg.github.io/mediasession/#the-mediametadata-interface, MediaMetadataInit init object should be optional.
,
Jan 3 2017
,
Jan 3 2017
,
Jan 4 2017
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/1d78b4038dcf9d3d21f1045dcf1a2244a3118e3b commit 1d78b4038dcf9d3d21f1045dcf1a2244a3118e3b Author: mlamouri <mlamouri@chromium.org> Date: Wed Jan 04 09:42:59 2017 Media Session: MediaMetadata constructor may have 0 parameters. Per spec. Also, because the dictionary has a default value for each field so passing {} or no parameter should have the same effect. BUG= 677955 R=zqzhang@chromium.org Review-Url: https://codereview.chromium.org/2614463002 Cr-Commit-Position: refs/heads/master@{#441349} [modify] https://crrev.com/1d78b4038dcf9d3d21f1045dcf1a2244a3118e3b/third_party/WebKit/LayoutTests/media/mediasession/mediasessionmetadata.html [modify] https://crrev.com/1d78b4038dcf9d3d21f1045dcf1a2244a3118e3b/third_party/WebKit/Source/modules/mediasession/MediaMetadata.idl
,
Jan 4 2017
|
|||
►
Sign in to add a comment |
|||
Comment 1 by mlamouri@chromium.org
, Jan 3 2017Owner: mlamouri@chromium.org
Status: Assigned (was: Unconfirmed)