On second thought, I guess if we assume that the user *did* intend to load some web fonts by making a call to webfontloader, and we're not loading any fonts, then the most sensical thing to do would probably be to set inactive as a "the fonts that you probably expected to be here aren't here" kind of message.

So yeah, maybe firing inactive in these cases makes the most sense from a developer perspective after all.