active-event not being triggered when two calls made back to back

[onassar]

The following JS Fiddle showcases the issue (running 1.6.21.min.js):
https://jsfiddle.net/hp307g3w/1/

You'll see that while the second font's fontactive event is fired, the active is not.

[bramstein]

This looks like a bug. Is there any particular reason why you would call load like that?

[onassar]

I tried to simplify my application-logic, which itself will make multiple calls to load depending on how a user interacts with the app. Any timeline on a possible fix? Would be happy to test / confirm.

[onassar]

Any estimate on timeline?

[grabks]

@bramstein This appears to be impacting release 44 of Google Charts. I believe it's causing issue #2179 for us, where users are unable to draw multiple charts that use the WebFontLoader, since each chart makes its own load call.

Do you have any estimates for when this issue might be addressed?

[bramstein]

It looks like this was introduced when we made the modules load asynchronously. I think I know how to fix it, I'll try to find some time for it this week.

[onassar]

Great thanks @bramstein
Looking forward to a fix

[grabks]

@bramstein Awesome! Thanks for the update!

[onassar]

Any movement here?

[dlaliberte]

The problem grabks reported above was not a problem in 1.6.8, but became a problem starting with 1.6.15. That might provide an additional clue to narrow this down.

[codemanki]

+1 here. Experiencing the same behaviour: making multiple calls to load and only first fires active event. All others just freeze

[onassar]

I'm using a bunk work-around for this. Good luck to you all :|