W3C

– DRAFT –
Web Fonts Working Group Teleconference

28 June 2022

Attendees

Present
Bianca, chris, Garret, jhudson, jpamental, sergeym, siterum, skef, Vlad
Regrets
Chris Lilley
Chair
Vlad
Scribe
garret, jpamental

Meeting minutes

jpamental present+

Pull request review

Garret: PR 98 - intention to provide guidance to browsers around how this should work with HTTP cache

<Vlad> #98 (https://github.com/w3c/IFT/pull/98)

Garret: changed the way the algorithm works so there are inputs to tune it's behavior and leverage cache

Garret: PR 100 - following discussions from last call about font collections - they are added in this PR. Added fields to identify fragment ID

<Vlad> https://github.com/w3c/IFT/pull/100

Garret: PR 102 - cleanup PR, nothing too big here. Instead of linking to the top level RFC it links to the relevant section and updating other references to the most recent RFC

Open issues (https://github.com/w3c/IFT/issues)

Skef: new issue. Updates related to 2 bugs

Garret: Haven't had a chance to review yet

Vlad: Skef, are these related to the issues you previously reported?

Skef: They are related, but new

Garret: If I understand it, you're looking to make the two approaches more independent. This seems reasonable

Skef: Yes - it should allow more independent development of different aspects of the spec

Skef: From our perspective, if we're going to do work on this we'd want to have access to the document scan

Garret: For now the spec doesn't deal with that, and not sure if we need to. It could be left to the browser (or JS developer) to handle as an implementation detail

Garret: I'll review and comment further with a little more time

Skef: I updated Issue 93 with more information

<Garret> https://fonts.gstatic.com/experimental/patch_subset/demo.html

Garret: Skef, have you seen the web assembly demo? If not I'll send a link

Garret: We built the client and server in C++, and I built up the client in web assembly as well so I could run it in the browser

Vlad: Seems like all 3 issues we have now might benefit from a new section in the spec. Not sure if we can address it right now, but the discussion is ongoing

Vlad: Pretty confident we can do that before TPAC. My goal is to have it pretty well complete so we can share it there

Garret: That seems reasonable

Vlad: I reached out to Myles to find out status from him. He is now managing the group, and so has less time to devote to this. He confirmed he is still interested and indicated there may be someone else who might be able to help as well

Jason: Won't be able to get to TPAC in September, but can join remotely

scribe nick: garret

Vlad: in person attendance?

Skef: tuesday, wednesday

John: yes

Garret: yes

Sergey: yes

Bianca: no, but will join remotely if possible.

Vlad: re: planning.

Vlad: want spec to point where it can be shared with everyone.

Vlad: garret you mentioned making a video.

Garret: I will respond to the email asking for Demo's.

Vlad: I was contacted if we had something to talk about during atypi

Vlad: the video demo would be good for that.

Garret: agreed.

Vlad: will need to check if there's collision between the two events in sept.

Vlad: it will be the week before TPAC (sep. 1st - 3rd)

Garret: I should be able to do the demo.

Vlad: I'll respond accordingly

Vlad: not sure about Myle's attendance, will check in.

Vlad: FYI requirements for being tested before returning to the US have been lifted for 90 days, which covers to the end of TPAC.

Vlad: for the next call looks like the next available date would be the 26th.

Vlad: let's plan to keep working on the spec, addressing issues until then.

Vlad: so next call will be the 26th

Minutes manually created (not a transcript), formatted by scribe.perl version 185 (Thu Dec 2 18:51:55 2021 UTC).

Diagnostics

Maybe present: Jason, John, Sergey