– DRAFT –
Web Fonts Working Group Teleconference

WOFF2

<chris> https://github.com/w3c/woff/issues/15

https://github.com/w3c/woff/issues/15#issuecomment-1015409619

RESOLUTION: the four editorial changes are agreed as editorial

RESOLUTION: publish an updated WOFF2 Recommendation with two proposed corrections

@chris: once we have 2 months of review we can make propose it as a specification. Is there interest in proposing woff2 as an ISO standard?

<chris> dvb references woff 1, should update to woff 2

vlad: yes, this should

vlad: yes we should (fixing typo)

Vlad: when we introduce these changes we should ensure that the test suite is up to date

@Garret it shouldn't be too bad once I get time to work on it

@Vlad: Chris - do we need to have a second implementation?

@Garret: we could add it to FontTools pretty easily

@Chris - that would be useful to have

RangeRequest FPWD

<chris> https://w3c.github.io/IFT/RangeRequest.html

@Vlad - back to the original agenda. If you recall we decided it would be easier if we had the first public working draft before we included Range Request

@Vlad we need to do that now with Range Request to publish that as a working draft before we can merge them

@Chris - it's normal to have open issues. No reason to have that block publishing the first public working draft

RESOLUTION: approved publishing of First Public Working Draft of Range Request

Merging

@myles: can we start merging?

@chris: yes we can, but there is overlap that has to be resolved when we do

@chris: top down approach makes sense - I like the structure of Range Request so follow that when bringing it together with Patch Subset

@myles: since it was my idea to split them, it seems like I should be on the hook to merge them

@myles: I'd prefer to do one big PR to mush them together and then start to reorganize

@Garret: no objection

@Vlad: we can postpone next week's call so you have time

myles: I have one topic I'd like to add

myles: I think our spec is coming along well but the biggest unknown for me is the integration with CSS font loading API and how the font display descriptor is going to work

myles: what does it mean/how does it work if you try 'font-display: block' when it's a dynamically loaded font

myles: where should those questions be posed/resolved?

Garret: I think we should create the issue and then take it to the CSSWG with suggested solutions

chris: this avoids open-ended issues in CSSWG which tend to go on forever

myles: ok then I'll open some issues with specific technical questions

<Vlad> https://github.com/w3c/csswg-drafts/issues/6892

Vlad: anyone have anything else to add to the agenda?

Vlad: chris do we have all the resolutions we need to proceed?

chris: yes we do

Vlad: I will update the invitation to reflect canceling next week's call

Vlad: thank you all!