Re: Proposed agenda for this week telcon, March 28th

FYI I don't expect to make the call tomorrow (it's a bit of an awkward time
for me)

On Wed, Mar 27, 2019, 4:04 PM Myles C. Maxfield <mmaxfield@apple.com> wrote:

> I don’t know if we’ll have time, but I’d like to have a discussion about
> flashiness.
>
> I think we’ve all settled on a design where, during initial page load,
> some subset of a font is downloaded from a server. Then, as the page
> content changes, there would be subsequent downloads from the server, and
> somehow a way of joining the new response with the old response. What
> should browsers show during the second download?
>
>
>    - One option is the way unicode-range behaves, where a random half of
>    the characters scattered throughout the newly-added text are rendered, and
>    the remaining ones are invisible. I have accidentally caused behavior like
>    this in WebKit before (in English content), and we heard howls from users
>    about it.
>    - Another option is for the browser to somehow separate the “new text”
>    from the “old text” and render none of the “new text” but keep rendering
>    all of the “old text”. Keeping these two sets distinct is perhaps
>    unimplementable, especially in the presence of things like React that have
>    “virtual DOMs” and automatic diffing
>    - Guarantee that, for every alphabetic language/script, the entire
>    alphabet always be transferred together. This wouldn’t help the scripts
>    that need progressive enhancement the most, may not work with combining
>    marks even in alphabetic scripts.
>    - Maybe someone smarter than me can come up with something better?
>
>
> Thanks,
> Myles
>
> On Mar 26, 2019, at 9:07 AM, Levantovsky, Vladimir <
> Vladimir.Levantovsky@monotype.com> wrote:
>
> Folks,
>
> Here is what I have on my list of tentative topics for this week’s telcon:
>
>    1. Review the results of the F2F survey
>    <https://www.w3.org/2002/09/wbs/44556/WebFontsWG-Sep2019F2F/results> and
>    firm up our meeting plans (venue, prep work, etc.)
>    2. WOFF2 bug fixes/maintenance <https://github.com/w3c/woff/issues>
>    3. Enriching Variable Fonts (see list archive for details
>    <https://lists.w3.org/Archives/Public/public-webfonts-wg/2019Mar/thread.html>
>    )
>    4. Progressive Font Enrichment strategy and legacy support
>    <https://lists.w3.org/Archives/Public/public-webfonts-wg/2019Mar/0004.html>
>    5. Housekeeping – review and updates on action items
>    <https://www.w3.org/Fonts/WG/track/actions/open>
>    6. AOB
>
>
> See call connection notes for details
> <https://lists.w3.org/Archives/Public/public-webfonts-wg/2019Jan/0026.html>
> .
> Thanks,
> Vlad
>
>
>