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

Neil_Enns_-_Ado
Adobe Employee
Neil_Enns_-_AdoAdobe EmployeeAccepted solution
Adobe Employee
November 10, 2015

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

SFS-DPSAuthor
Level 4
November 10, 2015

"If you need to use touch events in your page you should integrate the DPS touch APIs"


Does this mean that these DPS API's need to be re-added in a program like Dreamweaver? This is not something I can do in muse?

Neil_Enns_-_Ado
Adobe Employee
Adobe Employee
November 10, 2015

It means you have to write your Javascript code in a way that uses the APIs if you are attempting to use touch in your HTML. If you’re in Dreamweaver or Muse you’d need to include the APIs and then use them.

Neil

SFS-DPSAuthor
Level 4
November 10, 2015

Ok. I will have to find out how a non-coder like myself can do this in muse. I have asked on the Muse Forum also.

SFS-DPSAuthor
Level 4
November 10, 2015
Neil_Enns_-_Ado
Adobe Employee
Adobe Employee
November 10, 2015

Yup!

Neil

Anthony_Cumia
Level 2
March 31, 2016

I'm having this same problem. So how do non-coders solve this? I've looked at the DPSGesture API material as well, but being a non-coder, I really don't understand what goes where.

Peter_Villevoye
Level 2
July 7, 2016

As I said in this other thread: same problem here.

I'm guiding a former DPS client into the realms of publishing with AEM and Muse for HTML content, but they have absolutely no experience or ambitions in coding. Let's wait for Adobe's official stance on their earlier "non-coding" approach and promise...

BobLevine
Level 6
July 7, 2016

My $0.02 is that there is no such thing as an HTML solution with no coding required. Yeah, you might get away with something highly templated but to not have any HTML skills today is to put yourself at a very big disadvantage.

SFS-DPSAuthor
Level 4
July 7, 2016

It would then be nice if adobe would put together an explicit (in the sense even dummies can follow along) tutorial on how to add AEM UI to a Muse Published page.

Since this would be a repetitive workflow for every artical created in muse.

Possible?