Permissions
Previously, in Classic UI, special development consideration had to be made to facilitate AEM diffing (such as using cq:text
tag lib, or custom integrating the DiffService
OSGi service into components). This is no longer needed for the new diff feature, since the diff occurs client-side via DOM comparison.
However, there are some limitations that must be considered by the developer.
-
This feature uses CSS classes that are not namespaced to the AEM Product. If other custom CSS classes or third-party CSS classes with the same names are included on the page, the display of the diff may be affected.
html-added
html-removed
cq-component-added
cq-component-removed
cq-component-moved
cq-component-changed
-
Because the diff is client-side and executes on page load, any adjustments to the DOM after the client-side diff service has run will not be accounted for. This may affect
- Components that use AJAX to include content
- Single Page Applications
- JavaScript based components that manipulate the DOM upon user interaction.