Skip to main content
jamesqg8994329
Participating Frequently
April 30, 2017
Answered

Missing Edge Inspect - preview alternative?

  • April 30, 2017
  • 1 reply
  • 1060 views

Hi there,

I have upgraded to the Captivate 2017 release and I am missing the edge inspect preview option.

I am designing responsive html projects and it is important to preview and test the look at various screen sizes (prior to each breakpoint taking effect). Any ideas how to complete this actions with the 2017 release (short of publishing the content)?

 

Thanks in advance,

James

This topic has been closed for replies.
Correct answer Lilybiri

There is no alternative except publishing, uploading to a web server or Scorm Cloud and test on devices. Too bad that Adobe discontinued development of the Edge family.

Contrary to Steve, I am not as optimistic about the Preview being totally WYSWYG. Preview (in Browser) works pretty well for SWF output (Flash player was standard) but not for HTML5 output. HMTL5 is  necessary for responsive projects. The difference between Preview and published output can be

considerable (just to mention effects, especially motion paths, and tet containers). Output depends both on device and the used browser.

1 reply

Inspiring
April 30, 2017

Hi James,

The short answer would be to preview normally and just adjust the sizing slider to your preferred device dimensions, You can dynamically change it to any size and then back again, in preview.

Cheers,

Steve 

Lilybiri
LilybiriCorrect answer
Legend
April 30, 2017

There is no alternative except publishing, uploading to a web server or Scorm Cloud and test on devices. Too bad that Adobe discontinued development of the Edge family.

Contrary to Steve, I am not as optimistic about the Preview being totally WYSWYG. Preview (in Browser) works pretty well for SWF output (Flash player was standard) but not for HTML5 output. HMTL5 is  necessary for responsive projects. The difference between Preview and published output can be

considerable (just to mention effects, especially motion paths, and tet containers). Output depends both on device and the used browser.