Issue with clientlib load order

[#1]

Hi All, 

We have an issue where clientlibs included directly included in the page (using data-sly-call overriden in customheader and customfooter fragments) is loading after the clientlib included through page policy. This is for XF page. Is there a way We can include the page policy after the statically included base clientlibs. 

[kautuk_sahni · Accepted solution]

Xfpage points to a different page rendering component. I adjusted head.Html to reorder inclusion of header css and it worked

[kautuk_sahni · Accepted solution]

Thank you for sharing the solution with AEM community

[Adilmo]

Hi, Use defer to load policy clientlibs after the DOM load.

https://javascript.info/script-async-defer#defer

[Adilmo]

Can enforce the order of clientlib loading .... from page component ??