scrollable frames do not work.

Neil, thanks for the quick response. I'm a WYSIWYG kind of guy, so I wouldn't know how to build a preview app. I'll continue with 2014 until it becomes available in 2015.

You need to build your own preview app right now, we don’t have an ACV equivalent available for 2015. When you build your own preview app in the Apps tab of the portal you’ll then have to sign it with your iOS developer certificate so you can install it on your device.

Neil

I'm not even at the point where I'm viewing this on a Kindle or iPad. I'm trying to get the previewer to work. I have an EPUB previewer with InDesign 2015, but it doesn't even recognize scrollable frames. I have to go back to the 2014 version of InDesign which has the Adobe Viewer application. I don't have a clue how to access the Adobe Viewer with InDesign 2015, and I think that's the problem. Does it even exist?

Hi Ivan. Yes I have indeed and all my scrolling related issues were solved a couple days ago. I think Jim (original post) may need some tips though!

Thanks!

Jeff

Jeff - re: the HTML scroll frames issue, have you looked at the DPS HTML Gestures API? Adobe DPS 2015 HTML Gesture API - Examples.zip

That could fix the issue you describe

Hi. A couple of us on the board have had some issues related to this topic though all my scrolling frames are working fine with IOS and Android Viewers. They always have worked for me (those created in indesign). I was having issues with HTML scrolling focus before the latest update. I had to tap before it would focus on the HTML frame and allow scrolling. Now it functions as normal. Jim, Are you creating indesign scrolling frames or HTML frames that scroll? Have you recreated your app since the update went out this week? We all have to recreate the apps for each new Adobe update. Also, I have had some cacheing issues and have rebooted my devices periodically.

Jeff

Hi Jim,

Have you tried activating them by tapping on them first? There's another thread floating around the forum where someone has that issue, and while I thought it was fixed in the last release apparently the fix didn't quite make it in.

Neil