Adobe Edge files fails in validator - setTimeout

[kekaiser]

Hi!
We have been in dialogue with Adobe Nordic to try to figure out the problem why Adobe Edge files fail in validator. One of the main reasons why Adobe Edge files fail validator is using setTimeout.

Adobe is working with this and trying to find a solution where setTimeout is not used in Edge files, but as described further down in the email Edge, test files run through validator still get an setTimeout error, although the test file does not contain any use of setTimeout.
Are there other events / actions which validator defines as setTimeout or how should we deal with this.

Here is the email from Adobe:

Hi Johan,
We are Evaluating the removal of setTimeout from animate JS runtime.
As an experiment, I have a created a hacked runtime whichemail does not use any window.setTimeout / setTimeout call. But the validator is still complaining excess usage of setTimeout.

It is strange. Am I missing something?

Please try it yourself.

Open page: http://validator.gardr.org/
Choose: City Desktop / Tablet
Choose: 980x300

Copy / paste the pages with hacked runtime
http://edge-settimeout.businesscatalyst.com/assets/edge_test/edge_test.html

Choose: RUN and wait for the report. (See 160+ calls of setTimeout)

Now open the same page in a browser
Inspect and view the source.

Search for setTimeout. You will not find any Occurrences of that.
It would be helpful if you can workwith the validator devs and let us know how it arrives at this report.

Thanks
-Siva

[sveisvei]

Will look into this and see if I can give you a direction.

The requestAnimationFrame warning will be removed, as the IOS versions who had issues with this has such a low marketshare.

[konsulenten]

That would be great!

The Adobe team for Edge Animate is awaiting feedback on this case. They are eager to contribute to solving this.

Numerous ad-agencies in Norway wants to use Edge Animate to produce ads, so the sooner these issues are resolved, the better :)