Web Viewer overlays

Similar Questions

• Is any web viewer control?

  Is it possible to have a control on screen web viewer with the "done" button that appears on all content when linking to the Internet in a DPS application? My client wants an app that mimics the behavior of kiosk and wishes to include the option for a visitor to link to various company websites. So far, the app works beautifully by referring to a sequence of attractive images to attract people after 5 minutes.

  However, when the visitor opens the web viewer that the image sequence is below the web viewer window, it is so possible booth would be left sitting on the web page for as long as it takes someone to walk by and press the Finish"" button.

  Unfortunately, integrating Web sites in an overlay on a web page to prevent this as various Web sites open new windows and lead to the web viewer jerky window open again.

  I raised the possibility with the customer that he can be a behavior that we cannot control. But I would be sure.

  Is there any way to have the web viewer overlay be on some sort of timer?

  Thanks in advance for any advice. This forum is great!

  No, there is not. Sorry

  Neil

• URL of Web viewer links

  We have implemented a web viewer integrated by following the instructions on this page:

  http://www.Adobe.com/devnet/digitalpublishingsuite/articles/embedded-Web-Viewer.html

  Here is a link to the results:

  http://www.forconstructionpros.com/Viewer?WV=s%2FSustainable%2520Construction%2F049ab0e6b2 f34f82813b4b7b3f57067a%2FSust%2520Fall%25202014%2520v29%2FCover.html

  There is unexpected behavior when clicking on URL links (try on the second page).

  The linked URL opens in the same browser instead of opening a new window.

  Because of this, when you click the back button in the browser, it takes back you to the coverage because there is only a single URL for the spectator to all the embedded web.

  On the other hand, here's an example of a web viewer embedded.

  By clicking on a link on this page, opens a new browser window, so when the viewer closes this window, they can continue to read the magazine where they had left him.

  How to change that? Is this something that can be done with the way the integrated web viewer is built?

  Is there a workaround in how the URL links have been built in InDesign?

  Please advise,

  Dave

  In the hyperlink overlay Panel, be sure to set the link to open it in the browser of the device and not the browser in app, and then update the folio of the DPS dashboard

• Can't see an excerpt from the article on iPhone with web viewer enabled. How to solve?

  I try to activate the preview of the article for the web viewer for iPhone. On iPhone, I see just a banner with the cover of my problem...

  

  How can I configure so that viewers can just to see complete with overlays "Get App" section as it is configured for iPad?

  Here is a link to test...

  Citygram Austin July 2014: makes - Kumbh Mela

  It is a Folio v30, all items are marked as 'free', folios have the same name and product ID and web viewer is enabled.

  I thought I had this feature before.

  We do not support the viewer of the web article on iPhone, right on iPad.

  Neil

• The external web site links do not work in Web view

  Hello

  " I folio with overlay of web content and inside I have a link to external site: < a href =" http://external_site "target ="_blank"> "

  Everything works as expected when viewing folio on the iPad Adobe Viewer,

  but does not work in Web mode. I found, that contentviewer.adobe.com puts "web content overlay" in the iframe and add after the html header line

  http://CDN-ContentViewer.Adobe.com/public/pepper/lib/interwindow-messaging-lib.js

  It seems that this script blocking external links.

  Someone has experienced this problem?

  Any ideas how to make the web content from overlay to external site link working in Web mode?

  Thank you

  Piotr

  
  

  
  

  Thank you. The viewer web team has studied this issue and found a bug. The fix should be in place in a few weeks.

• Can web viewer external links open in a new browser window?

  We have as a default behavior for all links off the title would open in a new browser window when clicked. Now by clicking on a link reuses the window current and required the user to the publication.

  I was hoping that maybe change the value in Folio overlays Hyperlink "Open in Folio ' to 'Open in device browser' would work, but it doesn't seem to change anything on the web viewer.

  He will be supported in publication v29 of tomorrow.

• Rendering limits Web viewer

  I'm trying to discover the limits of the "renditions" of the web viewer. I realized a Folio that has an overlay on ever page content drop down, hot spots, galleries etc but it will not create a shared web when rendering via a social link in the application of development, what it produces is the message "this article is not currently available for this device." (under Google Chrome Mac desktop). However, I produced a folio of test that have complicated overlays and just copy and images which creates a shared Viewer web when rendering via a social link by e-mail.

  I guess there are limits to what the web viewer can show, that's why the simple folio displays and complicated folio is not.

  Just for reference bot folios have been implemented (I checked double) in the same way and they are all free, no dose two or protected.

  Make sure that you reports not protected articles. See the help article through Social sharing for more details on this and the limits of web viewer.

  http://helpx.Adobe.com/Digital-Publishing-Suite/help/using-social-sharing.html

• Web Viewer: Best practices and Limitations

  The opportunity to share our publication online via a web viewer is an asset to have. However, I noticed some blockages in two folios, we have made available online: videos suddenly stop playing; slow scrolling pages are not completely accessible to see; interactivity does not work in different browsers. I wonder if there is any documentation or advice to ensure a smoother experience across all display options.

  Hello

  Thanks for the additional details. We look at the issues you reported and have a few comments.

  Here are a few quick notes for each of the elements.

  -Video suddenly stop playing.

  We had a new web viewer updated today, and this seems to have solved the problem with the video stopping on this article.

  http://ContentViewer.Adobe.com/s/Airman%20Magazine/c31b3f6bf51348f280a8bf8e57d33ee4/2013-0 6/7%20SUMMITS%20SIDEBAR.html

  In this article, there is a play button placed inside the OSM. ASM has been put to play as a slide show and the loop. It was originally an interaction with the video that caused it close. We have made some changes to the way video MSOs interact in this latest version, and that avoids this problem.

  Yet, in this case, apparently not necessary to use the DSO or even a button. For videos full screen like this, you can simply create the video overlay on the image of the button. With videos full screen, the area of overlay that you define behaves like a button "play" without you having to add explicitly one.

  -Scroll effect slow pages are not completely accessible for display

  We have also looked at this article and are able to reproduce the problem. As we develop a solution, we will work to get to a workaround to help you avoid this problem. We'll post here when we have some suggestions for you.

  -Interactivity does not work properly in different browsers

  We have experienced some problems with certain types of content in Internet Explorer. We are working on some improvements to help reduce these.

  I will address the two items that you referenced separately.

  -Multi-state objects does not properly

  There are some limitations with IE when it comes to the way it handles the interaction events. In this case, the layout of the content can be slightly adjusted to avoid this problem. I noticed that the positioning of several ESM is a little bit off.

  For example, the "VISUALS4" MSO is supposed to appear on the fourth page (index of the #3 page). However, if you look carefully at the InDesign file, you will see at the top of the OSM superimposed on the previous page of two pixels. As layering begins on the previous page, this is how it is rendered. Most modern browsers can handle this correctly, but it affects the stacking order in a way that causes a problem with IE.

  If you move all WHO the problem a few pixels to make sure that the upper part of the WHO is aligned with the top of the page, it should work properly in Internet Explorer.

  -Overlay of the play button has somehow to only changed the blue outline

  In reviewing the file folio for the article, it shows that the two States for the MSO play button use the same image.

  http://CDN-ContentViewer.Adobe.com/v/88e59469-94d0-4D3B-95cb-595c7d3a7944/7%20SUMMITS%20SI DEBAR/1/OverlayResources/InDesign_BNDLR_RSRC29936-633919858/Multi-state%2010_State%202_205 11_Content_L.png

  I don't know what the behavior planned for this MSO. It is configured as a slide-show mode that loops between the two States, once it is clicked. Because the OSM will be covered by the video full screen, which is the desired effect? Please explain what you want to achieve and we can provide suggestions.

  -No support for overlays

  On some browsers, including some versions of Internet Explorer, we support all interactive overlays. The screenshot you posted seems to be an overlay of imageSequence. This special overlay is not supported on some versions of Internet Explorer.

  Please let us know if you have any other questions or encounter other problems. We will do our utmost to help.

  Thank you

  JC Camargo

  Computer scientist, Adobe Digital Publishing Suite

• Future plans for the App Web View

  I'd like say the new view of web get you sharing a folio is exciting. Question: What are the future hope or that he plans for this feature. SE Navto: / / buttons and overlays be fully supported?

  Thank you.

  The Web Viewer supports all overlays in the latest browsers (Chrome, Firefox, Safari, IE9, IE10) with the exception of the Panorama. There is also a limited overlay support in IE8 (hyperlink, 360 view, button, image)

  Kristy

• Link Hypertext &amp; Web view

  In the new InDesign 5.5, the link Hypertext & Web view only seem to be able to work in the Overlay of the Creator window Preview / Panel.

  But when I saw it by Folio Builder and the iPad, both of this interactive overlay does not work.

  The rest of the features like Pan, Video etc all works well.

  Can someone please?

  Thank you!

  OK, I was able to recreate the problem with hyperlinks and I went ahead and submitted a bug report to Adobe.  The key question, however, I wasn't able to recreate.  Check a few things and let me know if it fixes the problem.

  With your button, make sure that you have "navto://articlename" make sure that the name of the article is the same way, it appears in the Panel (which must match the name of acrobat.com) so not 'articlename_h' or 'articlename_folio' or something like that.  Update section of the folio builder Panel... and preview the FOLIO group level.  If she does not have article you made navto it will not work.

  Let me know if it helps

• Ad Mob in a Web view?

  Hello

  I want some ads on my AIR apps playbook, the only way I could think to do was to have a web site discovers with a banner of admob in it. Has anyone tried this or something similar?

  Some people have trouble using AdMob ads in anything other than the native implementations provided by Google.  They prohibit accounts with sites that seem to be the mobile web because they no longer allow that.

  Another option would be to use the HTML-based banners, where the network does not care where they are shown.  I used LeadBolt with good success, given their advertising banners are pure HTML/Javascript.

  I just did a quick video tutorial on creating a HTML upward in a Web view using LeadBolt.  Should be portable anywhere, you can load html...

• How to add the Web view in the screen.

  I want to add the text at the top of the screen and the Web view that open site in the lower part. Please help me that how can I do this.

  Thanks in advance.

  "I want to make the request and build BB JRE 4.7.

  No you don't really have.

  And you shouldn't, because:

  (a) as much as I know there is no performer 4.7 devices that cannot be upgraded to 5.0

  (b) the proportion of 4.7 devices autour is very small, so it is a small market

  (c) there is a lot of work

  (d) the results are not as good

  (e) a person on this forum will be able to help you.

  RIM do not support the OS 4.7 for WebView, so if nothing else has convinced you, it must give the impression that you should not try to develop for OS 4.7.

  Edit:

  Really should have said that it is just my opinion...

• Scalability and cross-platform Web Viewer features

  If I understand door MEA Mobile apps, our company is interested in using AEMM provided the web viewer is cross-platform capable.

  On the phone, the web viewer support a sensible overview; However, seems to want to launch the application.

  On Tablet (iPad, at least), the web viewer displays the message: "this content is no longer available.  "Download the application to enjoy similar content."

  On the desktop, the experience is good; However, what scalability is possible; as the sensitive available refining?

  This ability would be major for our society - both in the launch of new projects, as well as our full range of editions of the migration.

  The web viewer only works on desktops and laptops. It is not supported on phones and tablets.

  Extensibility for web office viewer is similar to iOS and Android apps. Creating workflow API and most APIs Cordova associated with the application, user, device and content work similarly in web viewer as they do in iOS/Android, but Cordova APIs that are specific to mobile devices (such as the camera and geolocation) do not work in Office web viewer.

• Item is not available in web viewer

  Although my content, collections and page layouts are published, when I connect to my web Viewer URL and browse in an article, the page displays an error message:

  We're sorry

  This article is not available

  

  Any recommendations as to the action, I'm missing?

  It looks like the content is being measured in your application. The collection in which appear the articles has a product associated with ID. When you change the product ID in the table of edge products & subscriptions, it occupies to the object or restricted? If you set the ID of the collection in fr., all items within the collection will be available. If you do not want this collection to be free - if you want to require a purchase or log - then you need to change the properties of the article and change the access to the Article of 'Aerosol' or 'Protected' to 'free '. Publish and check again.

  If this does not work, let us know.

• Why are they the Web viewer and device sign in different boxes?

  We create an AEM application that uses right V2. I just noticed that the sign in the dialog box for the Web Viewer looks like this:

  

  But the sign in for iOS devices dialog box looks like this:

  

  Ask yourself why they are different? Differences that matter to us:

  1. the screen of the Tablet says "Username" but Viewer says Web 'Email address' (we prefer email address)

  2. the screen of the Tablet is not a link "create an account", but the Web viewer don't. This is important. We need this.

  Is it possible to make these screens match? Why are they different?

  Thank you.

  Keith, the 'create an account' link on iOS is in the 'Account' dialog box, under the button "connect". iOS is the only application that has a dialog account, because iOS has a few other configuration options to manage the different store not present scenarios on other platforms. Do you not observe it at this place?

  About the chain, the difference is involuntary. User name is the more generic term and one we use throughout all the viewers of the mobile device. We chose the username because some authentication providers do not require an email address, so he labelling 'e-mail address' may be incorrect.