If we double click on the classic dialog icon in the component node structure in crxde, a page opens up in a new tab where we can see the dialog layout.
url : localhost:4502:<<path-to-component>>/dialog.html
Issue : For some dialogs , a blank page opens up even though the dialog is properly constructed and is already used in components. Some AEM folks have suggested that this happens because of the custom listeners in the component and AEM is unable to evaluate custom listeners output while rendering the dialog. However , this issue is observed in some /libs components as well.
For ex : /libs/foundation/components/video
/libs/foundation/components/title
Is it an expected scenario/known product behaviour ?
There is a common console error for all these components. Please find attached the screenshot
Solved! Go to Solution.
Views
Replies
Total Likes
I just tested on AEM 6.2 this use case. i cannot replicate this issue
/libs/foundation/components/title/dialog
http://localhost:4533/libs/foundation/components/title/dialog.html
/libs/foundation/components/video/dialog
http://localhost:4533/libs/foundation/components/video/dialog.html
May be this is your environment and your custom listeners specific.
Views
Replies
Total Likes
I just tested on AEM 6.2 this use case. i cannot replicate this issue
/libs/foundation/components/title/dialog
http://localhost:4533/libs/foundation/components/title/dialog.html
/libs/foundation/components/video/dialog
http://localhost:4533/libs/foundation/components/video/dialog.html
May be this is your environment and your custom listeners specific.
Views
Replies
Total Likes
I think it is an issue in this specific environment. I will look into this.
Views
Replies
Total Likes
Views
Likes
Replies
Views
Likes
Replies
Views
Likes
Replies