Hi Feike, thanks for the suggestion. It makes the component unauthorable and it can considered as solution to our problem.But as Scott highlighted above, can we still consider this to be a bug? Same piece of code is behaving differently in different UI.Using resourceType='foundation/component/iparsy...

I thought so too. Classic ui works fine as it locks the dialog because of inheritance. Same should happen in touch ui as well.Thanks for the response. I will try logging this as bug.

Yes that is correct.

Our goal is to include the component along with dialog values into another page. Our comoonent 'menu' contains the navigation menus and included in the header section of the page. It is authored in index.html page and we want the same component with same values inside another page that is not a dire...

hi All,we have recently migrated from AEM 6.0 to AEM 6.3 and refactored the code in sightly. There is one scenarion i need help with. we have a page :     /content/myproduct/global/en_US/indexThis has components in it          /content/myproduct/global/en_US/index/jcr:content               - navigat...