In this scenario, the workaround you mentioned will be effective for resizing cases; however, it will not work for edits. This is because the HTML is injected before the observer is initialized, so any subsequent changes are not detected by the observer. As a result, the callback will not be trigger...

Does anyone have insight into whether this is an architectural oversight or an intended behavior? If it is intended, could someone provide the reasoning behind it? If it is a mistake, will it be addressed in a future release, or are there any open tickets related to this issue ?

The callback I’m attaching to the afteredit listener is quite resource-intensive, as it reinitializes parts of the DOM. For this process, I require the latest DOM structure. Using MutationObserver would trigger updates for every change, which defeats the purpose of the AEM event listeners like after...

I'm using event listeners to track changes like afteredit, aftercopy, and aftermove. I've noticed that when I apply layout changes, the afteredit listener is triggered. However, when I listen for afteredit after a resize, I'm not getting the updated DOM HTML. It seems like the event handler might be...