Re: Intent to ship: PerformanceServerTiming

2018-04-25 Thread Boris Zbarsky
On 4/25/18 8:12 AM, James Graham wrote: If there is general agreement about restricting the feature to secure contexts There is not. Given the discussion in the spec issue, I fully expect Chrome to ship it in all contexts. -Boris ___ dev-platform

Re: Intent to ship: PerformanceServerTiming

2018-04-25 Thread James Graham
On 24/04/2018 22:36, Valentin Gosu wrote: On 24 April 2018 at 22:44, James Graham This affects web-compat, since per our "restrict new features to secure origins policy" the serverTiming attribute wil

Re: Intent to ship: PerformanceServerTiming

2018-04-24 Thread Valentin Gosu
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 61. >> >> Chromium bug: h

Re: Intent to ship: PerformanceServerTiming

2018-04-24 Thread James Graham
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 This

Intent to ship: PerformanceServerTiming

2018-04-24 Thread Valentin Gosu
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 "restrict