Our short term solution to this problem was to take the AEM 6.3 version of /libs/cq/gui/components/authoring/editors/clientlibs/core/js/model/Inspectable.js and install it as an overlay at /apps/cq/gui/components/authoring/editors/clientlibs/core/js/model/Inspectable.js in 6.4. Its hasPlaceholder me...
This appears to be a dropzone bug in touch ui. My component has cq:dropTargets in its editConfig and I can fix the problem by removing cq:dropTargets but I need cq:dropTargets because it is needed for in-place editing of the component's background image. I may need to create an Adobe support ticket.
I have a container-like component that has a parsys and it is often nested several deep on my 6.3 site that is migrating to 6.4.8. However, when I have a page that has four of these nested components, the 6.4 touch ui doesn't let me add any components to the parsys of the inner-most component. I can...
The developer mode does give some high level info about the livecopy's components, but it doesn't allow one to open the touch dialog for any of the components. My authors want to open the livecopie's touch dialogs in read-only mode so they can understand how its components are configured.What I thin...
In AEM 6.3 Touch mode, where a blueprint has been rolled out to a livecopy page, a component on the livecopy cannot be edited unless one cancels inheritance for that component. I understand this is by design, but is there a way in the livecopy to open the component's dialog to see how it is configur...
The AEM Image component supports linking to other sites. Open the dialog for the Image component and then paste in the URL of the external website into the "Link to" field.