Re: CSS issue about incremental font loading opt-in mechanism

Looks good to me.

I don't see anyone objecting to "new tech needs new keyword" so the only 
pushback that is likely would be "we tested `supports` and don't see a 
need" to which the answer would be, how will you support this new 
incremental stuff then.

I see its tagged css-fonts-5, which I think is reasonable given the 
timescales for our stuff, and that css-fonts-4 might make it to CR in a 
year or less with a following wind.

On 2021-03-02 13:32, Myles C. Maxfield wrote:
> I’ve created it here: 
> https://github.com/w3c/csswg-drafts/issues/6063 
> <https://github.com/w3c/csswg-drafts/issues/6063>. Please tell me if 
> anything should be changed/updated.
>
> Thanks,
> Myles

-- 
Chris Lilley
@svgeesus
Technical Director @ W3C
W3C Strategy Team, Core Web Design
W3C Architecture & Technology Team, Core Web & Media

Received on Tuesday, 2 March 2021 21:55:27 UTC