Skip to main content
Participant
February 25, 2017
Question

Captivate 9 Text Entry Box and Windows Keyboard Shortcuts Problem

  • February 25, 2017
  • 1 reply
  • 262 views

I have several projects developed in Captivate 9 that use text entry box fields. These are set to retain the text as a variable and uses the standard Submit button to proceed to the next page (where the variable displays the text).

For some learners, when they click on the text entry box and begin typing, it is almost treating what they type like Windows Keyboard shortcuts. For example, it may open a new tab to a search window, try to bookmark the page, or even take a screenshot. It is very much a hit and miss issue.

These are on Windows 7 machines running IE 11.

    This topic has been closed for replies.

    1 reply

    Paul Wilson CTDP
    Community Expert
    Community Expert
    February 26, 2017

    How many instances like this have occurred? I ask because it is not entirely uncommon that a user might mean to type one thing or another but accidentally press the [Ctrl] key instead of the [Shift] key as an example. The result could be to open up a search within a browser instead of simply typing an uppercase F. 

    Paul Wilson, CTDP
    Participant
    February 27, 2017

    Right now we have two courses this is happening now on in testing, 2-3 testers experienced this problem a couple of times. All the testers are developers and the first time it happened, we did ask them to verify what they were clicking and being careful what they hit, making sure they clicked in the text field before typing, etc, to try to eliminate user error as a possibility.

    Paul Wilson CTDP
    Community Expert
    Community Expert
    February 27, 2017

    That is unusual. Is it happening on just one slide in each course? I know that sometimes Captivate slides can become corrupt and cause unusual things to happen. Perhaps you could try recreating that slide just by itself from scratch and testing it out to see if it happens on a new version of the project. You may wish to reach out to Adobe. This could be a software bug.

    Paul Wilson, CTDP