Experiment gpf.require.define to leverage script tags instead of ajax loading

[ArnaudBuchholz]

No description provided.

[ArnaudBuchholz]

Found the following pattern:

var link = document.createElement("link");
link.rel = "import";
link.href = "https://cdnjs.cloudflare.com/ajax/libs/reveal.js/3.6.0/lib/js/head.min.js";
link.addEventListener("load", function () {
    alert(link.import.body.innerHTML);
});
document.body.appendChild(link);

Obviously, it does not work on IE but it allows to use CORS-enabled component (where AJAX can't)

[ArnaudBuchholz]

I need to do additional tests to assess compatibility

[ArnaudBuchholz]

Since I am not clear how this must be integrated in the lib, it can be:

• either specific to the gpf.require API (through gpf.typedef.requireOptions)
• or generic to the gpf.load API's browser implementation. In that case, a compatibility grid must be setup to determine when the mechanism is used or the dev may decide through an option that would be set through a global variable or on the script tag that includes the gpf lib.

In any case, the main benefit is to bypass today's limitations with AJAX requests (even if it is not a blocking limitation)

Putting back in the backlog until the need becomes obvious.