Skip to main content
Inspiring
June 1, 2017
Answered

iOS friendly//Issues with canvas conversion

  • June 1, 2017
  • 1 reply
  • 664 views

I have a created an animation with 50 buttons that react to the hover of a cursor.

However, it has come to my attention that Flash is not ideal nor iOS friendly.

So I have converted it to HTML Canvas, in hopes that this would work better.

I adjusted stop actions to

this.stop();

Now, the animation works perfectly when it is tested on Animate CC.

However when I click on the HTML after it is published, the animation works for the first button that is hovered over but then freezes on that frame and does not allow me to hover over other buttons.

What am I not understanding here? Any suggestion appreciated, thanks.

Sarah

This topic has been closed for replies.
Correct answer ClayUUID

Okayyyyy.... when you publish, do you see this in your Output window?

WARNINGS:

Content with both Bitmaps and Buttons may generate local security errors in some browsers if run from the local file system.

If yes, then that's what's happening. Your browser (I'm guessing Chrome) doesn't like certain things when pages are run locally, and throws a JavaScript error which halts the entire page. If you were to open the dev console in your browser (usually F12), you'd see the error message.

You don't get these errors when testing directly from Animate because it runs the page through a local web server. You won't get them when the files are posted on a proper web host either.

1 reply

Legend
June 1, 2017

Your buttons have bitmaps in them, don't they.

Inspiring
June 1, 2017

It's a US map vector.  Each button is a US state.  Each button gradually changes from grey to green, while a photo of a person pops up to the right of the map.

I wasn't sure how to answer your question, sorry.

ClayUUIDCorrect answer
Legend
June 1, 2017

Okayyyyy.... when you publish, do you see this in your Output window?

WARNINGS:

Content with both Bitmaps and Buttons may generate local security errors in some browsers if run from the local file system.

If yes, then that's what's happening. Your browser (I'm guessing Chrome) doesn't like certain things when pages are run locally, and throws a JavaScript error which halts the entire page. If you were to open the dev console in your browser (usually F12), you'd see the error message.

You don't get these errors when testing directly from Animate because it runs the page through a local web server. You won't get them when the files are posted on a proper web host either.