916 results found

1. 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

2. [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

3. [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

4. [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

5. Bug: "Apply appearance" is only partial

   When copying the appearance between instruction boxes, only certain aspects of the boxes are copied (such as border and background colour) while others are not (font face and box corner radius).

   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

6. 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

7. 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

8. 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

9. [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

10. Bug: Layer blur area under instructions

    I have instructions and a blur area in my simulation, and if I move them to the same place the blur area covers the instructions. What would be the point of having instructions if I wanted them blurred? I can't think of a case where one wouldn't want the instructions to be on top of the blur area.

    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

11. [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

12. [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

13. 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

14. [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

15. [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

16. [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

17. 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

18. Carousel Widget and LMS Reporting

    I want to be able to give the user points for clicking on the items of the carousel so I can see that they viewed each one. Currently it seems I can only report if they click on the arrow. If I have 4 items, and they keep clicking the arrow (say 6 times), do they keep getting points? Seems I should be able to report on the card states instead. If they only click on 2 of 4 cards, I want the LMS to report 2 as a reportable score.

    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  ·  1 comment  ·  Carousel 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

19. Cache - should ask you to change your default locations instead of being duplicated

    There should be a contradiction in the place in the preferences, where it says 'clear cache' -- the two file save locations -- one is the file location of the .cpt file, and the other is the cache file location. these should NOT be the same, nor should it be an option to be saved in the same place.

    Why you ask?
    Because I had my HUGE module saved to the same location in both of these locations. I cleared my cache. Then... POOF, my entire module - GONE!. Up in smoke. Disappeared.

    Nothing told me I was deleting my entire module. Nothing warned me. Just 1 click, and its gone.

    Recommendation:
    -make it a contradiction so that people cannot save their .cpt file in the same file location as the cache folder
    -make it not possible to delete the project while clearing the cache.
    -implying that 'clear cache' is doing much more than just clearing cache, which is a normal every day thing we do to make things run smoother.

    There should be a contradiction in the place in the preferences, where it says 'clear cache' -- the two file save locations -- one is the file location of the .cpt file, and the other is the cache file location. these should NOT be the same, nor should it be an option to be saved in the same place.

    Why you ask?
    Because I had my HUGE module saved to the same location in both of these locations. I cleared my cache. Then... POOF, my entire module - GONE!. Up in smoke. Disappeared.

    Nothing told me I was deleting my… 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  ·  Preferences  ·  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. This program is unusable in its current state.

    This program is unusable. Assets do not load, especially if you already have a system image loaded. Click to reveal does not work if you change image, or any settings (Something went wrong), Accordion crashes, you can't change image size so even if you have a small image it shows up huge in the slide. Hot spots, image is small and you can only size if horizontally. Slides and pictures resize from the editor to the preview. Its just ongoing. Unless you have a very simple course and you dont want to use widgets this program is basically useless. Going to go back to Classic until it is fixed (I dont hold hope).

    there are some good features but the program is so buggy and broken it ruins the experience.

    This program is unusable. Assets do not load, especially if you already have a system image loaded. Click to reveal does not work if you change image, or any settings (Something went wrong), Accordion crashes, you can't change image size so even if you have a small image it shows up huge in the slide. Hot spots, image is small and you can only size if horizontally. Slides and pictures resize from the editor to the preview. Its just ongoing. Unless you have a very simple course and you dont want to use widgets this program is basically useless. Going… 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  ·  1 comment  ·  Accessibility  ·  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