Hi,
For the first time when a touch ui custom component is added onto a page, its outline(blue box) is not visible and hence not editable. Only after page refresh(manually) we are able to see the component. I compared the component implementation for touch dialog with that of the foundation Text&Image component, but could not find any difference related to this.
Any help on this would be highly appreciated.
Thank you.
Solved! Go to Solution.
Views
Replies
Total Likes
Hi
I was reading an article, where i found slimier kind of problem.
//We noticed some bugs when switching between modes. In some cases, the change in mode does not trigger a change in “wcmmode”, so a page refresh is necessary for the components to display properly. For example, we built a tabbed component where each tab is displayed as a vertical list in edit mode so the authors can complete each tab, when switching to preview mode, the tabs are still displayed as a list, so we needed to trigger a page refresh to fix the rendering. Constant refreshing of the page may be irritating for an author.
Link:- http://www.inm.com/en/blog/2015/03/touch-vs-classic.html
You can try one thing, try this community article and see if problem still persist.
Link:- https://helpx.adobe.com/experience-manager/using/creating-touchui-component.html
I hope this will help you.
Thanks and Regards
Kautuk Sahni
Views
Replies
Total Likes
Hi
I was reading an article, where i found slimier kind of problem.
//We noticed some bugs when switching between modes. In some cases, the change in mode does not trigger a change in “wcmmode”, so a page refresh is necessary for the components to display properly. For example, we built a tabbed component where each tab is displayed as a vertical list in edit mode so the authors can complete each tab, when switching to preview mode, the tabs are still displayed as a list, so we needed to trigger a page refresh to fix the rendering. Constant refreshing of the page may be irritating for an author.
Link:- http://www.inm.com/en/blog/2015/03/touch-vs-classic.html
You can try one thing, try this community article and see if problem still persist.
Link:- https://helpx.adobe.com/experience-manager/using/creating-touchui-component.html
I hope this will help you.
Thanks and Regards
Kautuk Sahni
Views
Replies
Total Likes
Thanks for the information Kautuk, but i understand the example you had given is about switching between edit and preview mode.
When OOTB components for example Text & Image(/libs/foundation/components/textimage) is dropped onto a page, without having to refresh the page the component is visible for the author to be able to open the granite/touch dialog. But the same is not happening with my custom component.
Thanks and Regards
Srikanth Pogula.
Views
Replies
Total Likes
Views
Likes
Replies
Views
Likes
Replies