AEM ClientLib Loading Issue: clientlib Not Loading During New Page Creation

Hi @ben_hu,

When you create a new page, AEM opens a Create Page Wizard inside the Sites Console, not in the page editor.
This dialog runs in the SiteAdmin (or Page Wizard) context, not in the page context - so the extraClientlibs defined in the page component (like image.editor) are not yet loaded.

Only after the page is created and opened for editing does AEM load:

cq.common.wcm
core.wcm.components.page.v3.editor
core.wcm.components.image.v3.editor
image.editor

from the page’s component definition.

Move your script to a console clientlib

Instead of attaching via extraClientlibs to a page component, include your clientlib under the console clientlibs used by the page creation wizard.

Example:

/etc.clientlibs/image.editor

Then, in your js.txt, add your logic to listen for dialog events globally:

$(document).on("dialog-loaded", function (e) {
  // logic for alt text population
});

Attach your clientlib via category:

<clientlibCategory>cq.siteadmin.admin.properties</clientlibCategory>

or in your own category that you overlay into the Site Admin console.

OR
Dynamically detect context

If you must keep image.editor under the page component, you can lazy-load it when the dialog opens:

if (Granite.author && !window.imageEditorLoaded) {
    $.getScript("/etc.clientlibs/image.editor.js").done(function() {
        window.imageEditorLoaded = true;
        console.log("image.editor loaded dynamically");
    });
}

This ensures it still executes even if not included by extraClientlibs.

OR

Hook into the page creation wizard

If your logic specifically targets new pages, consider overlaying:

/libs/wcm/core/content/sites/createpagewizard.html

and including your clientlib category there (using a custom clientlib loader in the console).