W3C home > Mailing lists > Public > www-style@w3.org > April 2013

Re: [css-font-load-events] Using Futures

From: Anne van Kesteren <annevk@annevk.nl>
Date: Mon, 8 Apr 2013 15:37:05 +0100
Message-ID: <CADnb78jneaibv4kR2ZWwJierdq8aBi=2gb+6-+rdyMXv34-wGQ@mail.gmail.com>
To: "Tab Atkins Jr." <jackalmage@gmail.com>
Cc: www-style list <www-style@w3.org>, Alex Russell <slightlyoff@google.com>
On Mon, Apr 8, 2013 at 3:26 PM, Tab Atkins Jr. <jackalmage@gmail.com> wrote:
> On Fri, Apr 5, 2013 at 3:02 AM, Anne van Kesteren <annevk@annevk.nl> wrote:
>> I think we should remove the EventTarget dependency for now and
>> address this use case at a later point when futures gain a way to get
>> insight into the progress of the operation they represent the result
>> for.
> This doesn't make sense.  We do want ProgressFuture for Font.ready()
> (so you can indicate when a font *starts* loading, which is currently
> hidden), but the events I've left are on FontList, and can't be
> replaced by a ProgressFuture.

How does ready() not provide the same functionality provided it will
gain progress notifications going forward?

Received on Monday, 8 April 2013 14:37:41 UTC

This archive was generated by hypermail 2.4.0 : Friday, 25 March 2022 10:08:28 UTC