And again, here also painstakingly repeating various layout grid settings, copying scribbled numbers and all on notebooks, making mistakes (of course) and spending hours to do the most simple trick in the history of mankind and computerkind: COPY...

And it works – again another step forward ! I'm very carefully conducting the project at hand to stay clear of any non-standard widgets or nested interactions. But a slideshow should be the least of features to work correctly. So now we're both waiting to discover what's the next culprit to tackle ?

I understand very well that Muse's code can be quite a hindrance in addressing all possible 'hot spots'. As it turns out, the Slideshow's thumbnail is already a different type of tag than the trigger area of a Composition. The latter is playing nice with your script, while the former is not responding to the link tag.

We've been implementing the MuCow into a few 'real' pagesand noticed one drawback so far:Touching the thumbnails of a Slideshow toggles the navbar;touching trigger areas of a Composition doesn't toggle it.(The obvious behavior would be to not let it toggle.)

I noticed your MuCow now made it into an official Adobe AEM Help page !So it might be considered as the officially advised and endorsed procedure.I hope updates will follow swiftly, if new versions require certain adaptations.

Houston, we lost the problem... The navigation appears and reappears nicely when the screen is ticked anywhere.We'll be testing more complex pages the next days, so I hope this version holds up.Thanks for your very swift and adequate help, again !I'm going to push some corporate Adobe buttons, to implement it into the packageror offer some other structural solution "at the source". After all, it's their software.And I'll be crediting you all the way !!

Sounds like a plausible cause and fix.I'll give it a try, when I get my hands on my Mac...Thanks in advance - I'll keep you posted.

I tested it with a fairly simple existing page and a brand new page (Muse 2015.2), with just two colored rectangles as a header and footer and a few paragraphs of plain text in between. Note: both pages have been set up to be "fluid" ! Both pages refuse to display the app navigation. To be sure, I also tested a non-fluid version of another freshly build simple page, but again, in vain.I checked to see if the custom script was still present in all pages, and it was. It wasn't commented with <-- A...

After a holiday and some other jobs, I finally had the chance of testing this solution in the project at hand. But I'm sorry to say that it doesn't seem to work - yet.I placed the MuCow (1.2) file in the Master page, moved the little [ < > ] element somewhere at the top of the canvas, saved the Muse file and exported the HTML folder, processes the folder through the AEM Mobile Packager, and added it to an AEM project. But when viewed in the Previewer app on my iPad, the screen still won't reveal...

Woww, even support, updates, and bug fixes !