07-27-2021, 11:59 PM
Ciao DG112,
thank you so much for your detailed post. Really appreciated.
So, let's go per point.
About Defer/Async execution of Widget JS code. It is already Defer/Async. It's just a matter of formality.
By declaring it async, your automatic detection will state that everything will be ok. But nothing will change.
The execution of the code is triggered on a $(doc).ready() event. So it's blocking nothing.
And internal, asycn calls are already async.
About the automatic detection of "javasctipt cleaning" with the goal to save bandwidth, it's probably
a (at least partially) fake detection. The Zak widget is very flexible. Several if not many parts of code
are executed only if certain settings or properties have certain values.
About Woff and Woff2: we are on it. Maybe we can improve things here.
And also about utf-8 declaration, let us explicitely include the charset on the response.
But notice that afaik every browser, today, when charset is missing, tries with utf-8 as
first attempt. So we will make such intervetion, but probably nothing will change.
Thanks again for your contribution!
thank you so much for your detailed post. Really appreciated.
So, let's go per point.
About Defer/Async execution of Widget JS code. It is already Defer/Async. It's just a matter of formality.
By declaring it async, your automatic detection will state that everything will be ok. But nothing will change.
The execution of the code is triggered on a $(doc).ready() event. So it's blocking nothing.
And internal, asycn calls are already async.
About the automatic detection of "javasctipt cleaning" with the goal to save bandwidth, it's probably
a (at least partially) fake detection. The Zak widget is very flexible. Several if not many parts of code
are executed only if certain settings or properties have certain values.
About Woff and Woff2: we are on it. Maybe we can improve things here.
And also about utf-8 declaration, let us explicitely include the charset on the response.
But notice that afaik every browser, today, when charset is missing, tries with utf-8 as
first attempt. So we will make such intervetion, but probably nothing will change.
Thanks again for your contribution!