PSA: Deprecating JS-Implemented WebIDL

[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, please get in touch with me or another DOM peer to
discuss alternatives.

Cheers,
bholley
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform

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

[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 6.9.1)
>- MozillaBuild & our automation already use node 8.9.1
>- node 8.9.1 ships with npm 5.5.1
>- A lot has changed in npm between 3.10.x and 5.5.x, upgrading the
>minimum will provide better consistency for developers, especially with
>respect to npm-shrinkwrap.json/package-lock.json
>- This brings us closer to what was suggested in the "Intent to
>require Node to build..." thread.
>
> I'm thinking about bumping this the week of 7th May - after the merges
> have completed.
>
> I would like to hear feedback - positive or negative - from anyone likely
> to be affected by this proposal.
>
Full steam ahead from me!

Nick
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform

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

[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 
160,000 used this method [1].  For Beta 59 those numbers are 7.6 billion 
and 700,000 respectively [2].


So about .01% of pageloads are using this feature on beta 59; about 
.003% on beta 60.


That does seem low enough that removal might be reasonable, as long as 
there isn't some site like Hangouts which uses it, and is not usable in 
Firefox yet but we would like to be usable...


-Boris

[1] 
https://telemetry.mozilla.org/new-pipeline/dist.html#!cumulative=0_date=2018-04-18=__none__!__none__!__none___channel_version=beta%252F60=USE_COUNTER2_DEPRECATED_URLCreateObjectURL_MediaStream_PAGE_channel_version=null=*=Firefox=1_keys=submissions_date=2018-03-04=0=1_submission_date=0


[2] 
https://telemetry.mozilla.org/new-pipeline/dist.html#!cumulative=0_date=2018-03-01=__none__!__none__!__none___channel_version=beta%252F59=USE_COUNTER2_DEPRECATED_URLCreateObjectURL_MediaStream_PAGE_channel_version=null=*=Firefox=1_keys=submissions_date=2017-11-13=0=1_submission_date=0

___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform

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

[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 here:
https://developer.microsoft.com/en-us/microsoft-edge/tools/vms/

/Mats
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform

Intent to require Node 8.9.1/npm 5.5.1 for ESLint

[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
 * node 8.9.1 ships with npm 5.5.1
 * A lot has changed in npm between 3.10.x and 5.5.x, upgrading the
   minimum will provide better consistency for developers, especially
   with respect to npm-shrinkwrap.json/package-lock.json
 * This brings us closer to what was suggested in the "Intent to
   require Node to build..." thread.

I'm thinking about bumping this the week of 7th May - after the merges 
have completed.


I would like to hear feedback - positive or negative - from anyone 
likely to be affected by this proposal.


Please send comments to dev-platform or comment on bug 1456085. 



Thanks

Mark

___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform

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

[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/platform/issues/17021183/.


-- 
https://annevankesteren.nl/
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform

Intent to unship: URL.createObjectURL(MediaStream)

[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 as well but the method has not removed
yet: https://bugs.chromium.org/p/chromium/issues/detail?id=591719
. safari throws
. I haven't checked edge (I don't run windows locally)
. We have WPT.
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform

Intent to unship: SVGViewElement.viewTarget

[longsonr]

In https://bugzilla.mozilla.org/show_bug.cgi?id=1455763 I plan to remove our 
partial implementation of SVGViewElement.viewTarget

This was originally in SVG 1, but it never had much use, and we never 
implemented support for it either, if you actually try to use it you get an 
error.

It has been removed from SVG 2 and doesn't exist in Chrome either. 
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform

Intent to unship constructors on SVGNumber

[longsonr]

In https://bugzilla.mozilla.org/show_bug.cgi?id=1455940 I plan to remove the 
webidl constructors from SVGNumber 

This functionality is not in any version of the SVG spec, no other browser 
implements them and we fail a web platform test because of it.
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform