CP 9.0.2 Responsive Preview sometimes http:// sometimes file:// ???

[ingofkc]

I have a few responsive projects, When I select Preview > Project: =>

* Some of my responsive projects start on localhost and show this frameset - preview with integrated breakpoint-selectors.

* Some other responsive projects start from filesystem without this. breakpoint testing environment.

Question:

I can't figure out whats the difference in the settings. I would prefer to preview all my projects from localhost, but I can't find any setting /preferencies to do so.

[RodWard]

For Responsive projects use Preview > HTML5 in Browser, or else Preview in Edge Inspect (if you have set it up).

[ingofkc]

There is no Option "HTML 5 in Browser"

even in the docu the screenshot does not correspond with the text:

How to preview and publish responsive projects in Adobe Captivate

[ingofkc]

even if i choose "Preview in Edge Inspect" this one project starts on "file:///C:/Users/...."

[RodWard]

Sorry.  Forget I mentioned HTML5 in Browser.  That's for normal HTML5 projects.

You might as well forget I mentioned Edge Inspect as well because it's not being actively developed by Adobe since November 2015.

Your best testing option then remains to upload your Responsive output to Localhost, a proper HTTP web server, or an LMS, and test it from there.

I'll do some more testing and see if I can determine why there are differences when you preview.

[ingofkc]

Thanks for your answers!

The strange thing is, that some other projects do start on localhost, but this one important project does not.

[RodWard · Accepted solution]

Does this project happen to reference a document somewhere in the content, perhaps a link to a PDF or anything like that?

[ingofkc]

yes, indeed. but all links are relative, this way: "./external/abc.pdf"

just made a quick test:

added a link to a project with initial localhost-preview : after that it startet with file://

removed the link and it startet from localhost.

good to know, but not really helpful 🙂

thanks again!

[RodWard]

That's why I asked about it.  It looks like Captivate is trying to ensure that the link still works.  If it uses HTTP that particular link would be broken.

This is the first time I've been able to account for why Captivate behaved differently this way.

[ingofkc]

well, but the links to your own files are broken anyway...

[RodWard]

If including the files in with the published content, you really need to test the links AFTER uploading to a web server.  You may find that they work then, even if they don't work when testing the same content locally from your file system.

[ingofkc]

yes, i know that. but its not a good reason to switch the "preview-mode" from localhost to file system. because in preview the links are broken either.

[RodWard]

If you feel strongly about it, by all means log a bug or enhancement request.  I doubt that Adobe will do anything about it unless there is some volume of complaint.  The bug report is how you put things up for the development team to look at.