934 results found

1. Bug: Consolidating different simulations into a single file swaps FMR videos

   Because Captivate constantly crashes during the recording of simulations, I've decided to record shorter simulations and then consolidate them into a single file. The problem is, especially for FMR slides, the video is getting swapped — i.e., the audio is correct for that slide, but the video shown in the preview (and the SCORM output) is from a different slide. Captivate, however, shows the video as if everything were fine, so there is really no way fix it because for Captivate it's not broken.

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Software Simulation   ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

2. Bug: Recording simulations as a demo, a training, and an assessment at the same time doesn't usually work

   When recording is finished, at least one of them crashes.

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Software Simulation   ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

3. ragesh.c@gds.ey.com

   The new Adobe Captivate version does not support adding custom navigation elements like in the Classic version. Currently, the header and footer only allow limited customization—such as displaying the course name, page number, and TOC. There is no option to globally add essential navigation buttons like Back, Next, Glossary, or Resources across the course design. This limitation significantly impacts the flexibility and user experience of eLearning modules. Please consider reintroducing the ability to create and apply custom navigation players, as available in Adobe Captivate Classic.

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   Feature_In_Backlog  ·  1 comment  ·  Design Options   ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

4. Increase number of items allowed on Timeline widget

   Please allow us to add more than 6 items/nodes to the timeline widget. An upper limit of 10-20 items on the timeline widget would be more reasonable. I understand that space may be limited with some of the current design options, but changes could be made to accommodate more items on the timeline.

   For example, the design for the horizontal timeline could have a scroll arrow added to the screen, to allow users to scroll left and right and see further down the timeline. Alternatively, the design could be modified (or a new design added) to use a dedicated location or an overlay for all timeline callouts. This would allow for more items on the timeline without compromising on the space available for each callout.

   Finally, the requested change could be made on vertical timelines (currently, the third design option) without affecting the layout at all. Since users would simply need to scroll further down to see additional nodes/callouts, this change would likely be easiest to implement.

   --

   This feature request is based on version 12.6 of the All-New Adobe Captivate, which currently has a limit of 6 items for the timeline widget, regardless of the design option selected.

   Please allow us to add more than 6 items/nodes to the timeline widget. An upper limit of 10-20 items on the timeline widget would be more reasonable. I understand that space may be limited with some of the current design options, but changes could be made to accommodate more items on the timeline.

   For example, the design for the horizontal timeline could have a scroll arrow added to the screen, to allow users to scroll left and right and see further down the timeline. Alternatively, the design could be modified (or a new design added) to use a dedicated location… more

   3 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   Feature_In_Backlog  ·  0 comments  ·  Timeline Widget  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

5. Accessibility Bug: The scrolling text area does not have a tab index

   The click to reveal widget forces a scrolling text box. This text box cannot be scrolled by a keyboard user, because there is no tab index on the box itself. It is also not clear that the text box is scrollable, because the thumb for the scrollbar is hidden until scrolling with the mouse. This box should be responsive on browser zoom and expand vertically to show the text, rather than cut the text off in a scrolling area. If it must do a scrolling area, that scrolling area needs the scroll bar thumb as an indicator, and also needs to be focusable with tab.

   The click to reveal widget forces a scrolling text box. This text box cannot be scrolled by a keyboard user, because there is no tab index on the box itself. It is also not clear that the text box is scrollable, because the thumb for the scrollbar is hidden until scrolling with the mouse. This box should be responsive on browser zoom and expand vertically to show the text, rather than cut the text off in a scrolling area. If it must do a scrolling area, that scrolling area needs the scroll bar thumb as an indicator, and also needs… more

   3 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   Feature_In_Backlog  ·  2 comments  ·  Click to Reveal Widget  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

6. [Feature] Extended styling options for buttons in designOption.json

   Problem:
   Currently, not all styles available in the Captivate GUI can be set via the button’s designOption.json.
   Examples: gradient in shapeData, inner/outer shadows including position, and certain icon settings do not apply.

   Suggestion:
   Extend the button’s designOption.json, so that all styles available in the GUI can be applied.
   Additionally, as with content_blocks and smart_widgets, the JSON for buttons should be extended with customStyles.

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   1 comment  ·  Button    ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

7. [Feature] Filter for custom Design Options

   Problem:
   The GUI currently displays all stored Design Options.

   Suggestion:
   Add a filter in the Design Options menu to show only custom Design Options, for example.

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   Feature_In_Backlog  ·  1 comment  ·  Design Options   ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

8. [Feature] Control visibility of Design Options in the GUI

   Problem:
   All Design Options currently appear automatically in the menu, including those that are only used within other Design Options.

   Suggestion:
   Add a property in designOption.json (e.g., visible: false) to control the visibility of a Design Option, so internal options are not shown in the menu.

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   1 comment  ·  Design Options   ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

9. Being able to copy and paste images

   It would be helpful if images can be uploaded via copy/paste. Similar to how PowerPoint works, when an image is pasted onto a slide an image block is used. Also being able to copy images to reuse them without having to go through the file pathways to find the image source would help simplify and speed the process.

   8 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   Feature_In_Backlog  ·  1 comment  ·  Image   ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

10. Add Ability to Lower Slide/Thumbnail Resolution to Improve Editing Time

    Currently the program is super slow, and it's frustrating sitting there waiting for thumbnails of slides to process before I can even click them. I wish there was a way we could lower the resolution of our slides/thumbnails (like how Adobe After Effects allows you to lower the resolution to 1/4 or 1/2 to enable faster editing).

    I don't need my slides and thumbnails to look perfectly crisp while editing and if they were lower resolution in the editor it might help me speed up my process.

    I use some animated GIFs as images, and in the thumbnails Captivate is actually running the animation which is insane and probably uses up so much of my computer's processing on something that doesn't even matter.

    Also, when you are making interactions and you want to select a certain slide to go to - you have to sit there and wait while all the full resolution thumbnails populate before you can click anything. I have projects with a LOT of slides, and I name them all to ensure organization. If I could change this to be a text-only view rather than sifting through thumbnails it could save me a lot of time. Thank you Captivate Team I appreciate your time.

    Currently the program is super slow, and it's frustrating sitting there waiting for thumbnails of slides to process before I can even click them. I wish there was a way we could lower the resolution of our slides/thumbnails (like how Adobe After Effects allows you to lower the resolution to 1/4 or 1/2 to enable faster editing).

    I don't need my slides and thumbnails to look perfectly crisp while editing and if they were lower resolution in the editor it might help me speed up my process.

    I use some animated GIFs as images, and in the thumbnails Captivate is… more

    3 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    NeedMoreInfo  ·  1 comment  ·  Application   ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

11. Playhead Not Accurate In Timeline

    This is especially noticeable when I've just added a new audio to the slide. I add the audio, press play on the timeline, and the playhead is frozen in place while the audio plays uncontrollably in the background. Eventually the playhead starts moving, but it's inaccurate. When the screen is frozen and the audio is playing, I have to just sit there and wait for the playhead to start moving. If I click anything before the playhead starts moving again, the program can crash or freeze.

    I've noticed the timeline is pretty inaccurate in general, and I have to time my bookmarks based on LOOKING at the audio wave file instead of relying on the timeline itself. The playhead/timeline is also incredibly SLOW and I have to be super careful not to click too many times, or the play button will literally disappear while the audio plays with the playhead not even moving. Or, the first time trying to play a slide with a new audio will cause all the elements on the slide to disapear and I have to click to another slide to refresh it and start editing it again.

    This is especially noticeable when I've just added a new audio to the slide. I add the audio, press play on the timeline, and the playhead is frozen in place while the audio plays uncontrollably in the background. Eventually the playhead starts moving, but it's inaccurate. When the screen is frozen and the audio is playing, I have to just sit there and wait for the playhead to start moving. If I click anything before the playhead starts moving again, the program can crash or freeze.

    I've noticed the timeline is pretty inaccurate in general, and I have to time… more

    3 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    NeedMoreInfo  ·  1 comment  ·  Timeline  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

12. Make 'Auto Fit Height' include manual Padding Inputs

    In previous updates, I was able to add my custom padding and then select 'Auto Fit Height' to ensure that the content would stretch all the way across the screen, but it still maintained my padding settings.

    Currently, when I check 'Auto Fit Height' and preview, it will remove any padding and press the elements super close together - making it a useless function because there's no breathing room on the page anymore. So what I'm doing as a workaround is manually adding tons of padding so the images/text look centered vertically on the slide. Please bring back the original functionality or add vertical centering!!

    In previous updates, I was able to add my custom padding and then select 'Auto Fit Height' to ensure that the content would stretch all the way across the screen, but it still maintained my padding settings.

    Currently, when I check 'Auto Fit Height' and preview, it will remove any padding and press the elements super close together - making it a useless function because there's no breathing room on the page anymore. So what I'm doing as a workaround is manually adding tons of padding so the images/text look centered vertically on the slide. Please bring back the original… more

    2 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    NeedMoreInfo  ·  2 comments  ·  Layout slides    ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

13. [Feature] Custom placeholder text and images in `designOption.json`

    Problem:
    Currently, placeholder text and images in Design Options are fixed. When placing a design option, a default image and Lorem Ipsum text appear.

    Suggestion:
    Allow defining custom placeholder text and images directly in the designOption.json for each widget or slide element.

    {
        "tag": "slide-item-image",
        "placeholder": "placeholder.png",
        "customStyles": {
            "all": {
                "imageContainerStyles": {}
            }
        }
    }
    

    Benefit:
    - Designers immediately see the expected image size and proportions.
    - Placeholder text can indicate the function of the text (“Headline”, “Subtext”, etc.).
    - Increases consistency and standardization across slides and projects.

    •  

    1 vote

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    1 comment  ·  Design Options   ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

14. [Bug] Margin in Tabs widget prevents styling via `designOption.json`

    In the Tabs widget, Captivate applies the following CSS rule to an inner container:

    .cp-tabs-widget .cp-tabs-container .cp-widget-content-container > div {
        width: 100%;
        height: 100%;
        margin: 10px 0px;
    }
    

    The margin: 10px 0px cannot be controlled via designOptions.json. Visual styling such as margin or padding should be configurable.

    1 vote

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    1 comment  ·  Tabs Widget  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

15. [Bug] Inline margin in Tabs widget (cp-content-image)

    In the Tabs widget, Captivate injects an inline margin (margin: 0px 2% 0px 0px) into the cp-content-image element at page generation:

    <div class="cp-content-image" style="box-sizing: border-box; margin: 0px 2% 0px 0px; padding: 0px; flex: 0 1 40%;">...</div>
    

    This behavior overrides any margin settings defined in designOption.json.

    1 vote

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    1 comment  ·  Tabs Widget  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

16. Improve documentation for design options

    The design options concept is the most powerful feature in Captivate 12 and the key to building custom layouts. However, documentation is very limited. It is often unclear which JSON properties are actually supported for each widget, and many entries defined in the JSON are not transformed by Captivate.

    Suggested improvement:
    - Provide an example.json file for every widget, showing all possible properties (“grammar”) of the design options.
    - Especially for more complex widgets (accordion, tabs, carousel, etc.), this would help developers understand what can be customized.
    - Include notes for properties that are not yet transformed but are planned for future updates.

    The design options concept is the most powerful feature in Captivate 12 and the key to building custom layouts. However, documentation is very limited. It is often unclear which JSON properties are actually supported for each widget, and many entries defined in the JSON are not transformed by Captivate.

    Suggested improvement:
    - Provide an example.json file for every widget, showing all possible properties (“grammar”) of the design options.
    - Especially for more complex widgets (accordion, tabs, carousel, etc.), this would help developers understand what can be customized.
    - Include notes for properties that are not yet transformed but are planned… more

    1 vote

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    Feature_In_Backlog  ·  1 comment  ·  Design Options   ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

17. [Feature] Additional content wrapper for all design objects

    Problem:
    Currently, div.cp-widget-container directly contains the widget elements.

    Suggestion:
    It is recommended to introduce an additional content wrapper element below div.cp-widget-container for all widgets (videos, text, images, quizzes, etc.). This new wrapper should hold the actual content and control its maximum width, while the outer container can still be used for full-width background styling.

    Benefits:
    1. The existing div.cp-widget-container can continue to provide full-width background styling (color, image, etc.), stretching across the entire slide.
    2. The new inner wrapper (e.g., div.cp-widget-container__inner) should hold the actual content and define a maximum content width to center and structure the layout consistently. This is especially useful for long pages.

    Problem:
    Currently, div.cp-widget-container directly contains the widget elements.

    Suggestion:
    It is recommended to introduce an additional content wrapper element below div.cp-widget-container for all widgets (videos, text, images, quizzes, etc.). This new wrapper should hold the actual content and control its maximum width, while the outer container can still be used for full-width background styling.

    Benefits:
    1. The existing div.cp-widget-container can continue to provide full-width background styling (color, image, etc.), stretching across the entire slide.
    2. The new inner wrapper (e.g., div.cp-widget-container__inner) should hold the actual content and define a maximum content width to center and structure the layout consistently.… more

    1 vote

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    1 comment  ·  Design Options   ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

18. [Feature] Wrap VideoCaption and VideoBody in their own container

    Caption and Body should be nested in their own parent element for flexible layout, e.g.:

    <container-video-grid>
      <container-video-grid-card>
          <video></video>
          <videoText>
              <videoCaption></videoCaption>
              <videoBody></videoBody>
          </videoText>
      </container-video-grid-card>
    </container-video-grid>
    

    Benefit: Easier layout control, consistent spacing, flexible arrangement of video and text.

    1 vote

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    1 comment  ·  Video  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

19. [Bug] Remove inline height on page generation

    Captivate currently injects a fixed inline height (220px) into Video Grid containers at page generation:

    <div id="videoContainer_si78699" class="videoContainer" data-desktop-height="220" automation-id="slidevideo:::container_aspectratio" style="height: 220px; width: 100%;">
    

    This prevents proper responsive behavior and overrides custom CSS.

    Expected behavior: No fixed inline height should be injected. Instead, the container should default to height: 100%, so that its size can be fully controlled by parent elements defined in the designOption.json.

    1 vote

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    1 comment  ·  Video  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

20. Cards and LMS Reporting

    I want to be able to give the user points for clicking on each of the cards l so I can see that they viewed each one. Currently it seems I can tag the image on the card as reportable if it's clicked, and I can tag the Title of the card as reportable, but if you just click within the card and not on the icon or a label direclty, seems I can't report the fact that the card was flipped as a score to the LMS. For example, if there are 4 cards, and the user clicked 3, I want to report back 1 point for each card flip so I know they did look at them. Also, there is no variables or click actions to use to code interactions with the card.

    I want to be able to give the user points for clicking on each of the cards l so I can see that they viewed each one. Currently it seems I can tag the image on the card as reportable if it's clicked, and I can tag the Title of the card as reportable, but if you just click within the card and not on the icon or a label direclty, seems I can't report the fact that the card was flipped as a score to the LMS. For example, if there are 4 cards, and the user clicked 3,… more

    1 vote

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    NeedMoreInfo  ·  2 comments  ·  Cards Widget  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating