JET.js support of asynchronous loading

Steven McCoy

The JET API does not appear to be designed to handle HTML 5 [asynchronous script loading][1]. For example calls like `JET.onload()` will clearly fail as `JET` will not exist until the API has loaded. What other caveats are there with JET.js? Further references of note: -
https://developer.mozilla.org/en-US/docs/Web/HTML/Element/script -
http://ie.microsoft.com/testdrive/Performance/AsyncScripts/Default.html -
https://support.google.com/adsense/answer/3221666?hl=en [1]:
http://www.w3.org/TR/html5/scripting-1.html#attr-script-async

Steven McCoy

Here's async support, add the following to JET.js (to be improved)

(function(){
var w=window,a=w.jet.q,b;for(b=0;b


hello eikon

Zhenya Kovalyov

What is the use case for this?

Steven McCoy

@Evgeny as per the Google answers: "offers improved web latency and a better user experience for your site’s visitors. The advantage of the asynchronous code is that it's guaranteed never to get in the way of other parts of your web page loading."

Zhenya Kovalyov

Steve, I do understand why people use async script loading. I am using JET for some level of Eikon integration in one of my projects. The script loads seamlessly: my 3000+ lines of JS alongside JET. When you are working with Eikon, don't you want to work in the controlled sync environment anyway?

susana.chang

ported to external portal