Intent to unship: rel=preload for firefox 57

2017-10-12 Thread Dragana Damjanovic
rel=preload currently works only for cacheable resources. For web compatibility issues like bug Bug 1405761, rel=preload will be disabled on 57. I intent to land rel=preload for non-cacheable resources as well in next couple of days. This will be on Firefox 58 and I will turn rel=preload back on w

Re: Intent to unship: rel=preload for firefox 57

2017-10-12 Thread Chris Mills
> On 12 Oct 2017, at 08:43, Dragana Damjanovic wrote: > > rel=preload currently works only for cacheable resources. For web > compatibility issues like bug Bug 1405761, rel=preload will be disabled on > 57. I’ve updated the MDN docs about preload to make this clear. > > I intent to land rel=p

Re: #pragma once?

2017-10-12 Thread Gian-Carlo Pascutto
On 11-10-17 11:45, Emilio Cobos Álvarez wrote: > Hi, > > I'm adding a header to the build, and I'm wondering: Can we use pragma once? > > I don't see it anywhere in the build except third-party paths and: > > dom/svg/nsISVGPoint.h > xpcom/io/nsAnonymousTemporaryFile.h > > So I'm not sure if

Re: #pragma once?

2017-10-12 Thread Nicholas Alexander
On Thu, Oct 12, 2017 at 8:16 AM, Gian-Carlo Pascutto wrote: > On 11-10-17 11:45, Emilio Cobos Álvarez wrote: > > Hi, > > > > I'm adding a header to the build, and I'm wondering: Can we use pragma > once? > > > > I don't see it anywhere in the build except third-party paths and: > > > > dom/svg/

Re: #pragma once?

2017-10-12 Thread Kris Maglione
On Wed, Oct 11, 2017 at 11:45:54AM +0200, Emilio Cobos Álvarez wrote: Hi, I'm adding a header to the build, and I'm wondering: Can we use pragma once? I don't see it anywhere in the build except third-party paths and: dom/svg/nsISVGPoint.h xpcom/io/nsAnonymousTemporaryFile.h The last time

Re: Intent to implement: CSS media queries, interaction media features

2017-10-12 Thread fantasai
On 10/03/2017 01:12 PM, Thomas Wisniewski wrote: Summary: Implement the CSS features [any-]pointer:{none|coarse|fine} and [any-]hover:{none|hover} > ... How stable is the spec: the last point of contention that I'm aware of was resolved by other vendors a year ago when the "on-demand" feature w