Muse PreRelease to DPS 2015 | Community
Skip to main content
Level 4
November 10, 2015
Solved

Muse PreRelease to DPS 2015

  • November 10, 2015
  • 16 replies
  • 10977 views

Muse PreRelease to DPS 2015

I'm producing a muse page that is responsive so that it can be used in DPS 2015.

When I have an HTML article from muse placed in DPS it loads on iPad and phone great. But when I tap on the article the top menu does not show-up.

Is this a known issue?

I should add that other Muse 2015 html articles I have place in DPS 215 that are not responsive don't have this problem.

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by Neil_Enns_-_Ado

When this happens it is because your page is trapping the touch events so the viewer can't get them and react. You'll need to change your HTML so the javascript isn't capturing all the touch events. If you need to use touch events in your page you should integrate the DPS touch APIs.

Neil

16 replies

Anthony_Cumia
Level 2
July 7, 2016

I guess having a session at Max titled "No Code Required: Using Designer-Focused HTML Tools with Adobe DPS" would be a little misleading then.

SFS-DPSAuthor
Level 4
July 7, 2016

"BINGO" that's where some of the distress is coming from. Its marketed as one thing, and then once you have its another.

BobLevine
Level 6
July 7, 2016

Yup. But they’re not alone. Everyone does it and I hate it.

SFS-DPSAuthor
Level 4
July 7, 2016

So next best thing is to have a fantastic Tut on how to inject AEM API in to Muse page!

Peter_Villevoye
Level 2
July 8, 2016

@BobLevine: That kind of generalization is not helping.

For every "skilled coder" there are probably hundreds - if not thousands - of other human beings who don't, won't, and can't get a grip on coding. And they have very legitimate needs for digital publishing tools. You're right: many of them will happily use some kind of template or framework solution. But a fair amount of designers will never touch a tag.

But let's go back to the problem at hand: AEM not playing nice with Muse.

A friendly Adobe staff member discovered that older Muse output (before the responsive hoopla) worked fine, so something must have crept in with a recent Muse and/or AEM update.

Would a straight-forward "dummy" tutorial on how to apply that Gesture API solution help ?

If copying/pasting/editing some necessary code into an HTML file is the solution, then why not let Muse, AEM, or even the Packager handle it ? As a temporary work-around, we consider developing a script and a hot folder to process the code into the files.

Peter_Villevoye
Level 2
July 10, 2016

There's a temporary but very helpful solution now:

Re: Easy Way to Add the Gestures API to Muse