1. Why isn’t preview mode working with Chrome?
2. Why does the Pyramid Information widget work with IE and Edge, but not Chrome?
Before we get started, I have: Captivate 2019, 11.0.1.266 and this is the latest version.
Second thing: Chrome and Preview worked 100% correctly 2 weeks ago, it’s only been in the last week or so that the problem described below has started.
The Problem: I can no longer preview my project in Google Chrome (or any other browser), unless I fully publish and launch the index file. Chrome is my default browser, so I don’t even get the option to use IE or Edge. I know all the ‘haters’ swear Chrome is the best anyway, but secondary problem is that when I do get the published version to launch the Pyramid Information widget does not work at all in Chrome. The Pyramid Information Widget works 100% fine in IE and Edge. (Don”t ask about Mozilla or Safari, they are not allowed by my company so whether the work or not is irrelevant.)
Further information to ponder: we pushed the finished module to our LMS with the same results regarding the Pyramid Information widget… worked in IE and Edge but did not work in Chrome.
So I have the opposite issue. My preview works fine in both Chrome and Edge but when I publish it does not work.
When I launch the course it appears as though it is opening and even gives me the screen with the start arrow. When I click the start arrow I get a half title screen with a dark screen over top of the title screen and gives me nothing else to move further in the course.
It does work in IE, but IE is on the way out.
Hello,
I had the same problem and managed to fix it. My default browser was Chrome. Here is what worked for me.
- Set default browser to Edge.
- Previewed my project as HTML5 in browser/F11.
- Changed default browser back to Chrome.
- Now I can preview project as HTML5 in browser/F11 again in Chrome as it should be.
Good luck.
Must have missed this question.
Which type of project are you previewing? If it is a non-responsive (blank) project, you have to know that the only Preview method using a temporary HTML5 output is F11 (Preview HTML in Browser). The other Preview methods (not Play slide which is NOT preview) do use temporary SWF output. Chrome doesn’t install the Flash Player by default, so you’ll not be able to see the course with those Preview methods.
Hi,
Can you please confirm the exact OS version along with build number and the Chrome version that you are using at your end.
If possible, please attach a sample project with the pyramid widget so that we can test the behavior at our end.
Regards,
Shaleen
Hey Adobe… anyone think it’s time to address this issue? I canNOT work with responsive design design if I have to ‘publish’ anytime I want to review/preview my project.
PLEASEEEEE don’t tell me to just copy/paste the link in to another browser. THERE is NO link… Preview Project… there is NO link… nothing happens.
Try this one, uploaded to my domain:
Hi am currently facing the same problem. I SWF the preview works fine. But when I try to go to html5 preview i just get a “publish failed” message. I have cleaned the preferences so far, and try it on different browsers (Chrome, Edge, Safari, firefox) and it just doesn’t work.
Janen, when you are working on a Responsive project (like I am) the menu is even different. I don’t even get those options or a failure message. It will display the ‘processing’ dialog box like it’s doing something, then poof… nothing happens.
When I publish the file works 100% correct in IE and Edge. However, the published file will NOT display the widget in Chrome… it runs the file but not correctly.
Try using a responsive project, that’s the file type I am working with… something changed recently… In Feb at the Training 2019 Conf. in Orlanda all was fine. In March, everything was fine…. sometime in April Preview mode stopped working, and published files don’t work properly either in Chrome.
I did double-check and don’t have any issues, not when previewing Project, nor when publishing. I used this small test file, will post a link in another comment for you to check if it is working in your case?
Why separate comment: since it has a link, will have to wait for moderation. Have no idea how long that will take.
You must be logged in to post a comment.