I forgot to ask about this earlier. I just wanted to make sure I understood this change. We used to fail quickly if the webfontloader library detected that it thought the user agent didn't support web fonts at all. Now, we try to load and leave it up to each individual module to tell webfontloader if it thinks it can load web fonts? This would allow a module to provide support for something that webfontloader itself didn't detect as supported.

That seems logical and like a good way to make modules more independent. Is there a potential downside to this change? (Like a slower time to inactive event or something?)