Issue with clientlib load order | Community

New Participant

Solved

Issue with clientlib load order

Forum|Forum|5 years ago
March 9, 2021
2 replies
1590 views

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.

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.

Best answer by Adilmo

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

AdilmoAuthorAccepted solution

New Participant

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

Employee

Thank you for sharing the solution with AEM community

Kautuk Sahni

New Participant

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

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

Arun Patidar

AdilmoAuthor

New Participant

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