Preview mode will allow a client to see what will be displayed on a Publish instance.  Depending on how the HTLs were written, there might be differences between what is displayed on Author Instance's edit mode and Publish Instance's publish mode.    Changing the mode will refresh the page, it shoul...

AEM supports the use of both Sling APIs and JCR APIs.  Docs on best practiceshttps://experienceleague.adobe.com/docs/experience-manager-learn/foundation/development/understand-java-api-best-practices.html?lang=enDocs on Sling APIhttps://sling.apache.org/old-stuff/sling-api.html Docs on JCR APIhttps:...

General Java For basic Java tutorials and documentation : https://docs.oracle.com/en/java/https://docs.oracle.com/javase/tutorial/    For Apache Sling API https://sling.apache.org/old-stuff/sling-api.html   General AEM Java https://developer.adobe.com/experience-manager/reference-materials/ https://...

I found a working solution to load JSON data into a mock JCR.   @ExtendWith(AemContextExtension.class) @ExtendWith(MockitoExtension.class) class MyTest { private final AemContext jcrContext = new AemContext(ResourceResolverType.JCR_MOCK); private final Session jcrSession = jcrContext.resou...

This still results in testNode being null. Does it not for you?   I believe the mock JCR is different from the mock AEM context.    Only adding nodes into the MockJcr works. 

I can. But the road less travled is more interesting.  Also, I needed this approach to be able to test a workflow.

How could you load a json with test data into a MockJcr inside a Java Unit test?    I know it is possible to load a mock json into an AemContext, e,g,      @ExtendWith(AemContextExtension.class) @ExtendWith(MockitoExtension.class) class MyTest { final AemContext context = new AemContext(); ...

Request for Feature Enhancement (RFE) Summary:AEM can determine (either exactly or by degree of likelihood) which HTML elements are above the fold and which elements are below or outside of the initial viewport. And AEM allows to automatically put a loading="eager" or loading="lazy" attribute, respe...

Any progress or plans on this item?