On 9/25/17 11:45 AM, L. David Baron wrote:
So I don't think this requires any new *features* to be spec'd in
CSS (since @supports would work, and is the right thing to use),
although it probably does require a small amount of new spec prose
to explain how it works.
Well, it would need spec text
On Monday 2017-09-25 09:12 -0400, Boris Zbarsky wrote:
> On 9/25/17 9:01 AM, Anne van Kesteren wrote:
> > It does not seem hard to come up with solutions to those problems, if
> > we're actually committed to going down this path.
>
> If we are, yes. We need to decide whether we are...
>
> > (E.g
On 9/25/17 9:01 AM, Anne van Kesteren wrote:
It does not seem hard to come up with solutions to those problems, if
we're actually committed to going down this path.
If we are, yes. We need to decide whether we are...
(E.g., just like globals have isSecureContext,
there could be a media query
On Mon, Sep 25, 2017 at 2:47 PM, Boris Zbarsky wrote:
> On 9/25/17 3:18 AM, Anne van Kesteren wrote:
>> But it would also be good if we could all communicate this on behalf
>> of Mozilla without caveats. E.g., Chrome might ship worklets soon and
>> being able to object to that happening (specifica
On 9/25/17 3:18 AM, Anne van Kesteren wrote:
But it would also be good if we could all communicate this on behalf
of Mozilla without caveats. E.g., Chrome might ship worklets soon and
being able to object to that happening (specification-wise) on
insecure contexts on behalf of Mozilla would be go
5 matches
Mail list logo
