ExtensionInfo.isLoaded is inconsistent about adobe-runtime-support HOT 2 OPEN

Hi

It seems like we may have caused some issues when trying to ensure that the extensions' swf definitions were available from worker threads.. the mechanism we added there involved tracking the 'toplevel' object that was used when creating the initial reference to the extension (i.e. when we parse the XML descriptor file at start-up). So a worker that's then coming later with its own toplevel shouldn't be able to load extensions, but should be able to get at the swf definitions.

The issue though is caused by the fact that during start-up, it's an "internal" toplevel object that's being used when the extensions are first registered, but when you access things from your SWF code it's then a "content" toplevel object... so the loading of the SWF data did probably work, but the state was not being set to "loaded".

The thing I can't quite work out is how come some of them ended up with a loaded state of "true"..! if they are mentioned in the app descriptor with 'delayLoad' set, then the loaded state should be incorrect the whole time...

We have a fix for this though - just need to ensure it doesn't then break the Worker scenarios..!

thanks

from adobe-runtime-support.

Great to hear, let me know if you want me to test anything

from adobe-runtime-support.