[prev in list] [next in list] [prev in thread] [next in thread] 

List:       whatwg
Subject:    Re: [whatwg] Removing mediagroup/MediaController from HTML
From:       Silvia Pfeiffer <silviapfeiffer1 () gmail ! com>
Date:       2015-10-03 20:39:31
Message-ID: CAHp8n2n2QTTRDVzFNwCShWKWzatSg6E6itw9bVyKCpDChcNhGA () mail ! gmail ! com
[Download RAW message or body]

On Fri, Oct 2, 2015 at 10:27 AM, Domenic Denicola <d@domenic.me> wrote:
> From: whatwg [mailto:whatwg-bounces@lists.whatwg.org] On Behalf Of
>
>> is removal really the right thing to do, given that we have an
>> implementation?
>
> I agree this is a problematic question. I opened https://github.com/whatw=
g/html/issues/209 for the more general issue but am happy to have the discu=
ssion here since that hasn't gotten much replies. Do check out the examples=
 listed there though. E.g. Blink is in similar situations with <dialog> and=
 HTML imports.
>
> The web seems to end up with a lot of APIs like this, where the spec ends=
 up just being documentation for a single-vendor implementation. I don't re=
ally know what to do in these cases. If our goal in writing these specs is =
to produce an interoperable web platform, then such features seem like they=
 shouldn't be part of the platform.


There is also a question about the why of the current state: is it
just a single-vendor implementation because nobody at the other
vendors has gotten around to implementing it or is it because they
fundamentally object to implementing it. If there are objections, then
it's reasonable to consider removing the feature. Otherwise, it would
be premature to remove it IMHO.

Silvia.
[prev in list] [next in list] [prev in thread] [next in thread]