Re: Intent to ship: PerformanceServerTiming

On 24 April 2018 at 22:44, James Graham wrote: > On 24/04/2018 20:32, Valentin Gosu wrote: > >> Bug 1423495 is set >> to land on m-c and we intend to let it ride the release train, meaning we >> are targeting Firefox

Re: Intent to ship: PerformanceServerTiming

On 24/04/2018 20:32, Valentin Gosu wrote: Bug 1423495 is set to land on m-c and we intend to let it ride the release train, meaning we are targeting Firefox 61. Chromium bug: https://bugs.chromium.org/p/chromium/issues/detail?id=702760

Intent to ship: PerformanceServerTiming

Bug 1423495 is set to land on m-c and we intend to let it ride the release train, meaning we are targeting Firefox 61. Chromium bug: https://bugs.chromium.org/p/chromium/issues/detail?id=702760 This affects web-compat, since per our

Re: PSA: Deprecating JS-Implemented WebIDL

On Tue, Apr 24, 2018 at 07:25:18AM +0100, Andreas Tolfsen wrote: 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.

QA Firefox 62 feature testing pi-requests deadline is May 2

Hi, Similar to what QA did for previous Firefox feature testing prioritization , we would like to do the same for Fx62. In order to help with the process, *please submit your pi-request

Re: License of test data?

On 2018-04-24 10:24 AM, David Teller wrote: Ideally, I'd like to put a few well-known frameworks in jsapi tests, to be used as data for SpiderMonkey integration tests. What's our policy for this? Are there any restrictions? All the frameworks I currently have at hand are have either an MIT-

Re: License of test data?

On Tue, Apr 24, 2018 at 4:24 PM, David Teller wrote: > Ideally, I'd like to put a few well-known frameworks in jsapi tests, to > be used as data for SpiderMonkey integration tests. > > What's our policy for this? Are there any restrictions? All the > frameworks I currently

License of test data?

Ideally, I'd like to put a few well-known frameworks in jsapi tests, to be used as data for SpiderMonkey integration tests. What's our policy for this? Are there any restrictions? All the frameworks I currently have at hand are have either an MIT- or an MIT-like license, so in theory, we need to

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

This seems like it's about time. bz's numbers aren't awe-inspiring, but low enough that I think we'll manage. I checked, and there was a question about reviving this in the spec, but that resolved over a year ago (just before when the deprecated message was added in Firefox, perhaps

Re: PSA: Deprecating JS-Implemented WebIDL

On 04/24/2018 09:25 AM, Andreas Tolfsen wrote: 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,

Re: PSA: Deprecating JS-Implemented WebIDL

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