Adobe Animate preloader is not responsive in HTML export

Forum|Forum|8 years ago
September 20, 2017
4 replies
2046 views

Hi,

I'm exporting responsive content in JavaScript/HTML. However, when I 'Include preloader' in the Publish Settings, I have found that the preloader itself is not responsive. The result is that it does not sit centrally to the responsive content.

Any help to resolve this would be much appreciated!

Thanks,

Derrin

This topic has been closed for replies.

Correct answer UDESCO

Hi Derrin,

We have fixed this issue internally and it should be available with the next release.

Just to be sure, can you share a screenshot of your Publish settings and also, if possible, a test file to confirm it works fine on our internal builds. Thanks!

S

scottmadore

Inspiring

Is this fixed?

I am having the same problem. It never gets past the preloader.

trail11_sm201

I

islamm82371387

Participant

Unfortunately not yet.

P

Petrol.Eng

Participant

I think that you may try change the height and width to 50% of the "_preload_div_" in the HTML file:-

Change:-

To be:-

I hope that help you.

C

ClayUUID

Legend

Just to forestall any potential confusion for anyone reading this thread:

1) The Animate "preloader" isn't a preloader, it's a throbber. All Animate Canvas documents are preloaded by default. You can't not preload them.

2) What Animate calls "responsive" is just scaling and centering, not true responsive layout.

So Derrin's complaint actually has nothing to do with preloaders or responsive layout, It's just Animate not centering a throbber correctly.

I don't understand how Adobe, one of the most high-profile multimedia companies in the world, ended up using such incorrect multimedia terminology in one of their products, but I hold out the hope that they'll eventually fix it.

UDESCOCorrect answer

Participating Frequently

Hi Derrin,

We have fixed this issue internally and it should be available with the next release.

Just to be sure, can you share a screenshot of your Publish settings and also, if possible, a test file to confirm it works fine on our internal builds. Thanks!