RE: MSE testing status update

> Many of the *Track interface pieces are yet to be implemented in Chrome,

Are these currently interfaces implemented in any other MSE implementations?

/paulc

Paul Cotton, Microsoft Canada
17 Eleanor Drive, Ottawa, Ontario K2E 6A3
Tel: (425) 705-9596 Fax: (425) 936-7329

From: Matt Wolenetz [mailto:wolenetz@google.com]
Sent: Wednesday, June 24, 2015 7:21 PM
To: Michael[tm] Smith
Cc: <public-html-media@w3.org>; Paul Cotton
Subject: Re: MSE testing status update

Those MSE interface test Chrome failures are concerning. I reran the test suite against current tip-of-tree Chrome, and found similar failures. Many of the *Track interface pieces are yet to be implemented in Chrome, but there are multiple other interface failures.

I've filed https://code.google.com/p/chromium/issues/detail?id=504170 to track investigation within Chromium.


On Tue, Jun 23, 2015 at 5:02 AM, Michael[tm] Smith <mike@w3.org<mailto:mike@w3.org>> wrote:
Hi Matt,

Matt Wolenetz <wolenetz@google.com<mailto:wolenetz@google.com>>, 2015-06-16 07:58 -0700:
> Archived-At: <http://www.w3.org/mid/CAADho6NHF=oOC0sNz_Tw1BuiKsF=JgJ8mLMjW+=VzZojtpd1FQ@mail.gmail.com>
>
> Hi Paul,
>
> Sharing progress more widely, I have updated the MSE test result report
> with Chrome M43's current MSE test results [1], following along the path
> and instructions laid out most recently by Cyril [2].

I’m curious why Chrome is failing so many of the interface (WebIDL) tests.
I mean the tests in http://www.w3c-test.org/media-source/interfaces.html


They’re failing for a variety of different different errors, but many
(most) of them seem like they might be WebIDL conformance issues; e.g.:

A.「self does not have own property “SourceBuffer” expected property
   “SourceBuffer” missing」and「The prototype object must have a property
   “sourceBuffer” expected true got false」(which seem like problems with
   sourceBuffer maybe being implemented as an instance property instead of as
   a property of the prototype, as the WebIDL interface definition requires)

B.「PutForwards, Replaceable, or non-readonly attributes expected “function”
   but got “undefined”」

C.「class string of MediaSource.prototype expected “[object
   MediaSourcePrototype]” but got “[object Object]”」

D.「Called with 0 arguments function “function () { [native code] }” did
   not throw」

Otherwise I’m wondering if some indicate that there’s a problem with that
test (e.g., the test doesn’t match the current spec) or they’re failing
because Chrome’s implementation diverges from the spec and the spec hasn’t
been updated to match what’s implemented, or what.

  —Mike

> [1] http://w3c.github.io/test-results/media-source/all.html

> [2] http://lists.w3.org/Archives/Public/public-html-media/2014Dec/0012.html

--
Michael[tm] Smith https://people.w3.org/mike