For your DEV and Test environment you can use and see if you are still getting this problem.To disable clientlib mechanism, navigate to felix console yourhost:port/system/console/configMgrSearch for "HTML Library Manager" Check "Debug" and save.anyways for production you will not be changing the client libs so i think it's not a problem

So how many segments do you have to resolve ? and what are the conditions that each segments has ?Mostly, campaigns always will take a little time as it is resolved from the browser (JS) after the page has been rendered.

You can use the HtmlLibraryManager API to get the path of the JS from the client lib name. First get the ClientLibrary by passing the category name in the below API method-https://docs.adobe.com/docs/en/cq/5-6-1/javadoc/com/day/cq/widget/HtmlLibraryManager.html#getLibraries(java.lang.String[], com.day.cq.widget.LibraryType, boolean, boolean)And then get the include path of the JS by calling the following API method-https://docs.adobe.com/docs/en/cq/5-6-1/javadoc/com/day/cq/widget/ClientLibrary.h...

This is to do with XSS protection that that text editor runs through. You can find the configuration file here: /libs/cq/xssprotection/config.xmlYou can overlay the file under /apps/cq/xssprotection/config.xml and modify the configuration to allow what you're putting in there. At first glance, it looks like it validates the ID attribute with the following regex: . You may need to configure that further, or change the ID for your element (which would likely be a better option)

Approach should be close to #2.You need to have the template level or site level clientlibs at /etc/designs and include that in your template.For components, create clientlibs under that component folder itself which get included only when the component is used in the page while authoring. This is the normal approach to be followed in AEM. Regards,Lokesh

I guess this is a simpler way, you do have an option to set replicate permission for users, another way can we with package deployment.I hope you are creating your own site specific dictionaries.