Intent to unship: URL.createObjectURL(MediaStream)

2018-04-23 Thread Andrea Marchesini
Per spec ( https://w3c.github.io/mediacapture-main/ ), this was removed in 2013. I introduced a deprecated message in bug 1334564, the 7th, February 2017. I think it's time to remove this method completely. I wrote the patch in bug 1454889. About other browsers: . chrome has a deprecated message

Re: Intent to unship: URL.createObjectURL(MediaStream)

2018-04-23 Thread Anne van Kesteren
On Mon, Apr 23, 2018 at 9:50 AM, Andrea Marchesini wrote: > . I haven't checked edge (I don't run windows locally) Ask for a BrowserStack account (not entirely sure who arranges these though, I got mine via jst). Edge still supports it: https://developer.microsoft.com/en-us/microsoft-edge/platfo

Intent to require Node 8.9.1/npm 5.5.1 for ESLint

2018-04-23 Thread Mark Banner
I would like to increase the minimum requirements for node with ESLint to node v8.9.1, npm v5.5.1 for the following reasons: * ESLint 5.x is now in alpha, and raises its minimum node requirement level to 6.14.0 (ours is currently 6.9.1) * MozillaBuild & our automation already use node 8.9.1

Re: Intent to unship: URL.createObjectURL(MediaStream)

2018-04-23 Thread Mats Palmgren
On 4/23/18 10:01 AM, Anne van Kesteren wrote: On Mon, Apr 23, 2018 at 9:50 AM, Andrea Marchesini wrote: . I haven't checked edge (I don't run windows locally) Ask for a BrowserStack account (not entirely sure who arranges these though, I got mine via jst). Or you can get a gratis Win10 VM h

Re: Intent to unship: URL.createObjectURL(MediaStream)

2018-04-23 Thread Boris Zbarsky
On 4/23/18 3:50 AM, Andrea Marchesini wrote: I introduced a deprecated message in bug 1334564, the 7th, February 2017. When we have this data, it's worth mentioning what telemetry shows for such a deprecation message. I just checked and out of about 5.8 billion pageloads on Beta 60, about 1

Re: Intent to require Node 8.9.1/npm 5.5.1 for ESLint

2018-04-23 Thread Nicholas Alexander
On Mon, Apr 23, 2018 at 4:20 AM, Mark Banner wrote: > I would like to increase the minimum requirements for node with ESLint to > node v8.9.1, npm v5.5.1 for the following reasons: > >- ESLint 5.x is now in alpha, and raises its minimum node requirement >level to 6.14.0 (ours is currently

PSA: Deprecating JS-Implemented WebIDL

2018-04-23 Thread Bobby Holley
For reasons outlined in bug 1450827, the DOM peers have decided to deprecate support for JS-implemented WebIDL APIs. This means that new additions of |JSImplementation="foo"| are no longer permitted. If you maintain an existing JS WebIDL implementation, or are considering designs for a new API, pl

Re: PSA: Deprecating JS-Implemented WebIDL

2018-04-23 Thread Andreas Tolfsen
Also sprach Bobby Holley: > For reasons outlined in bug 1450827, the DOM peers have decided to > deprecate support for JS-implemented WebIDL APIs. This means that > new additions of |JSImplementation="foo"| are no longer permitted. Out of curiosity, and mostly because my knowledge of how this wo