- From: Garret Rieger <grieger@google.com>
- Date: Fri, 8 Jul 2022 11:49:00 -0600
- To: Yoav Weiss <yoavweiss@google.com>
- Cc: Chris Lilley <chris@w3.org>, "Myles C. Maxfield" <mmaxfield@apple.com>, Nic Jansma <nic@nicj.net>, public-web-perf <public-web-perf@w3.org>
- Message-ID: <CAM=OCWaPtTRyMZUDoqptKUKHOKpdFvXptyp7+-kMps9XuJ2+kg@mail.gmail.com>
Here's a link to the evaluation report I mentioned during the call: https://lists.w3.org/Archives/Public/public-web-perf/ Among other things it contains data from the simulations we ran to compare incremental font transfer performance to other font loading methods. Lastly, here's a link to the demo that I showed: https://fonts.gstatic.com/experimental/patch_subset/demo.html On Fri, Jul 8, 2022 at 11:43 AM Yoav Weiss <yoavweiss@google.com> wrote: > +Garret Rieger <grieger@google.com> +Myles C. Maxfield > <mmaxfield@apple.com> > > Thanks Garret and Myles for hopping over to the call yesterday. > Rough minutes from the discussion are in this doc > <https://docs.google.com/document/d/1B4SXlxQwJLwoQRkl5RQeBJ8GMjOB9qNxX4n3Vt9Js1o/edit#heading=h.ysuruy6slns6>. > I'll publish them to Github shortly. > I also opened a few issues > <https://github.com/w3c/IFT/issues/created_by/yoavweiss> and commented on > existing ones. Happy to discuss more! :) > > Cheers, > Yoav > > On Fri, Jul 1, 2022 at 3:30 PM Chris Lilley <chris@w3.org> wrote: > >> Hi Nic, >> >> Excellent, thanks for the swift response. We look forward to your >> comments! >> On 2022-07-01 15:27, Nic Jansma wrote: >> >> Hi Chris, >> >> Thank you for bringing this to our attention. We have put it on the >> agenda[1] for our next WebPerf WG call (July 7th) >> >> [1] >> https://docs.google.com/document/d/10dz_7QM5XCNsGeI63R864lF9gFqlqQD37B4q8Q46LMM/edit# >> >> - Nichttps://nicj.net/ >> @NicJ >> >> On 6/28/2022 8:23 AM, Chris Lilley wrote: >> >> The Web Fonts WG requests review of the Incremental Font Transfer (IFT) >> specification by the Web Performance WG. A new WD of IFT was published >> today [1] >> >> This specification defines two methods to incrementally transfer fonts >> from server to client. Incremental transfer allows clients to load only the >> portions of the font they actually need which speeds up font loads and >> reduces data transfer needed to load the fonts. A font can be loaded over >> multiple requests where each request incrementally adds additional data. >> >> Earlier work [2] demonstrated the performance improvements n terms of >> bytes transferred and reduced network delay, for various network types. >> >> The current work proposes a specific networking mechanism by which the >> client and server can negotiate which IFT method to use [3], and to >> transfer requested subsets of the entire font [4][5]. We would particularly >> value the review of the Web Performance WG on those aspects, although >> review of the entire specification would of course be most welcome. >> >> [1] https://www.w3.org/TR/2022/WD-IFT-20220628/ >> [2] https://www.w3.org/TR/PFE-evaluation/ >> [3] https://www.w3.org/TR/2022/WD-IFT-20220628/#method-selection >> [4] https://www.w3.org/TR/2022/WD-IFT-20220628/#extend-subset >> [5] >> https://www.w3.org/TR/2022/WD-IFT-20220628/#browser-behaviors-subsequent-requests >> >> >> -- >> Chris Lilley >> @svgeesus >> Technical Director @ W3C >> W3C Strategy Team, Core Web Design >> W3C Architecture & Technology Team, Core Web & Media >> >>
Received on Friday, 8 July 2022 17:50:07 UTC