Brett Birschbach

The approach of checking the parent edit context for whether the interface is in Edit mode is a result of the HTML in the `embed.html` file of the `embed` component...

Note that the cause of this issue is similar to https://github.com/adobe/aem-core-wcm-components/issues/2785 - both could probably be solved with a solution that captures the original WCM Mode in a request attribute.

A similar update should likely be made to `com.adobe.cq.wcm.core.components.internal.form.FormHandlerImpl#activate`

Also if the Redirect target is an internal path that is invalid, the same thing happens. Though that's maybe acceptable, it might make more sense to show the invalid path...

And if not support rendition selection, at the very least use a URL that gets a web rendition rather than referencing the DAM asset directly. Right now the background src...

If the Container component were able to leverage the `imageDelegate` pattern, it could create an Image model and render a URL that can be addressed by the AdaptiveImageServlet (or other...

This is effectively the same as the long-standing https://github.com/adobe/aem-core-wcm-components/issues/741 - ultimately to fix the Container component needs to be refactored to enable the `imageDelegate` pattern and reuse the image dialog...

This is effectively the same as the long-standing https://github.com/adobe/aem-core-wcm-components/issues/741 - ultimately to fix the Container component needs to be refactored to enable the `imageDelegate` pattern and reuse the image dialog...

In practice making all PNGs as `png-alpha` greatly increases file sizes served from Dynamic Media, which can incur a very large performance hit for larger images. So maybe setting that...

nice, love the approach assuming it works!