Ilya Grigorik

You're right, the timer business is complicated. My primary goal is to ensure that we enable developers to deliver the _fastest possible_ experience in their application. In the case of...

Depends on the specified strategy. If "block" is set to `infinite` (https://github.com/KenjiBaheux/css-font-rendering/issues/11#issuecomment-63159022), then we shouldn't fallback.. otherwise, treat timer as expired and apply the fallback.

@jakearchibald I don't follow what you're proposing here.. You're introducing new concepts like immediate, wait, race?

Ahhh, OK, now I'm with you. This is an interesting pattern... I like it. Couple of thoughts and questions: - s/wait/block.. i.e. font-rendering-block-timeout. - I believe this covers all the...

> It doesn't support "render nothing on fail"... I think we can make that work. How about... ``` css @font-face { /* ... */ font-rendering-wait-timeout: [duration]; font-rendering-block-timeout: [duration]; /* or...

@jakearchibald I think `infinite/0s+` is OK. I _was_ missing some cases, updated: https://github.com/KenjiBaheux/css-font-rendering/issues/11#issuecomment-63112270 @tabatkins that sounds about right. Re, block and swap: I would really like to use the desired...

> Again, the assumption of the current proposal is that if the font is important enough for you to want to blank the text while you wait, then it's probably...

@tabatkins to turn the question around, why should we disallow "block for X, swap for Y"? It doesn't seem unreasonable: I'm willing to suffer some pain (no text) and wait...

@tabatkins I think we can leave `3s infinite` out in favor of `auto`? Instead, I'd use `mandatory` as shortcut for `infinite/infinite` - I think the name actually fits! Other than...

Fair enough. I'm just hesitant of standardizing block=3s behind "swap".. It's an arbitrary value, and arbitrary values have a tendency to be (ab)used a lot once they make it into...