Hey all, During our migration from Classic UI to Touch UI, we're creating Touch UI dialogs and interfaces for all our components. Many of our Classic UI components made use of the "html5smartimage" ExtJS xtype to accept image input from the DAM and give authors the ability to set and change cropping...

Success.   This seems contrary to the proposed nature of how overlays are supposed to function? But I agree, this seems to have fixed the issue.   Thank you for spending the time to reply!

Going to give this a try today. You may be right on the mark, as this was something we JUST implemented a change for (hiding unwanted OOTB navigational components).   Will check back in a bit. Thanks!

Following up here - Having no success tracking things down using your method here. The new instance will randomly fail for reasons unrelated to our current setup... Makes it difficult to actually get to test the current failure points.   I appreciate the suggestion, but I don't think I can dedicate ...

Will give this a go and update here when I see some results. Thanks.

We're working through a lot of code changes right now, so yes, there have been many code changes. It started happening after a seemingly harmless adjustment to some component HTL. When I noticed, I reverted back to a code commit before the issue was occurring. This didn't fix the problem though.   I...

From my original post: "There are no obvious errors in the granite logs or the web browser console."   Gave it another go on startup, regardless.   Granite logs:   Browser console: In my development environment I'm still missing the ability to delete existing components or add new components to a ...

Components appear in all sidebar lists and pre-baked template areas as they're supposed to, yes.

Seeing this issue across both development and stage on our AEM 6.5.12.0 instances, while working in Touch UI over this last week: "The issue is that periodically ALL components will have their edit options removed, just leaving the Insert and Group options." (Same issues as this thread and this thre...

Tested and confirmed I'm seeing the same issue in my instance. Were you able to resolve this?