On Fri, Dec 23, 2016 at 4:02 PM, Martin Thomson <m...@mozilla.com> wrote: > On Fri, Dec 23, 2016 at 6:20 PM, Boris Zbarsky <bzbar...@mit.edu> wrote: >>> I mean, the attribute is probably a lost cause >> >> Why? Is there significant usage, or at least wide implementation, of that >> part of the API already? The original intent said that only Chrome is >> shipping this. > > Fair point. I guess the question becomes whether Chrome compatibility > is the reason we are doing this.
Yes this is the key question. IF there is a webcompat issue now, THEN we have little choice but to implement the API as is. IF there is no webcompat issue, THEN * We should NOT implement this "legacy" API, as us implementing in addition to Chrome may be enough to create a compat issue (for everyone else for this API design, and provide another point of inconsistency for web developers). Let's avoid a platform wart if we can. * We should be prepared to propose fixes/updates to the API that use a Promise per points from Joe, mt, bz, and then prototype/implement accordingly. Is there some other time pressure / use-case need to ship this feature "soon" that hasn't been discussed in this thread so far? Thanks, Tantek _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
