Skip to main content
M
michaelc17610552
Participating Frequently
December 2, 2019
Answered

Browser zoom settings not working on published captivate projects.

  • December 2, 2019
  • 1 reply
  • 677 views

After publishing and viewing a project created in Captivate 2019, I've noticed that the broswer's (Chrome) zoom controls (Ctrl +/-) do not work. However, when I maximize the browser or scale the browser from the side, the published Captivate project scales accordingly.  

This project was published in HTML5 only and Scalable HTML content was selected. 

Are the browsers zoom controls not able to work on a published file? Am I missing something?

Thanks.

MC

    This topic has been closed for replies.
    Correct answer RodWard

    Turn off Scalable HTML, republish, and then try it.

    1 reply

    RodWard
    Community Expert
    RodWardCommunity ExpertCorrect answer
    Community Expert
    December 2, 2019

    Turn off Scalable HTML, republish, and then try it.

    M
    michaelc17610552Author
    Participating Frequently
    December 10, 2019

    Rod,

    Thanks for your response. Browswer Zoom does work when scalable HTML is turned off. 

    Any idea why it can't be both ways? 

    Personally, I would rather an interaction be scalable than be able to have Zoom control but why not both?


    Thanks again Rod!

    RodWard
    Community Expert
    RodWardCommunity Expert
    Community Expert
    December 10, 2019

    Scalable HTML runs code that detects the size of the available screen real estate and then recalculates the display size of the Captivate content to match the available area and maximize either height or width (to preserve the aspect ratio).

     

    The code simply isn't written to work what you want.  It's just working the way Adobe wanted. If you change the size of the browser window, the code immediately recalculates the sizing to again fill the screen.

     

    I'm not saying it wouldn't be possible for some talented JavaScript code to modify the code to work the way you want.  There would be some trade offs, and your end users might like your outcome even less than the way it works now.  But feel free to try if you want.

    Terms & ConditionsAccessibility statement
    Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices