March 27, 2019
Keyboard keys like Tab, Page Up, Pause/Break, do not function when Posted to a web server,only when in Project test mode.
Comments
(11)
March 27, 2019
Keyboard keys like Tab, Page Up, Pause/Break, do not function when Posted to a web server,only when in Project test mode.
Newbie 1 posts
Followers: 0 people
(11)

I am creating projects for testing users on a main frame product. I have no choice on the keyboard commands they have to use. It requires Tabs, Page Up, Page Down and Pause/Breaks. I am able to program them just fine. They work perfectly when I use Captivate 2017 and Preview them with the Project option . I have published them in both swf and html. Does something need to be on the web server that I might be missing?  Is there code that needs to be updated or fixed? Please help.

Perplexed,

Dona Conn

Play
11 Comments
2019-06-25 21:40:44
2019-06-25 21:40:44

I have found a solution to my tabs not working problem. It is Java Script Code. It works.

 

Copy this code to the slide frame:  Actions/On Enter/Executer JavaScript/Script Window

$(‘Text_Entry_Box_1‘).focus();

$(document).keydown(function (e) {

var keycode1 = (e.keyCode ? e.keyCode : e.which);

if (keycode1 == 0 || keycode1 == 9) {

e.preventDefault();

e.stopPropagation();

} });

or if using a Click Box

$(‘Click_Box_3‘).focus();

$(document).keydown(function (e) {

var keycode1 = (e.keyCode ? e.keyCode : e.which);

if (keycode1 == 0 || keycode1 == 9) {

e.preventDefault();

e.stopPropagation();

} });

On the actual Text Box or Click box do the following:

Select the Text Box – Choose Actions/On Success/Go to the next slide/ Shortcut is Tab(or what ever does not work) and On Focus Lost/ Go to next slide.

Hope this helps others that have to use this for now.

Like
(2)
2019-05-23 16:33:05
2019-05-23 16:33:05

see this post

https://forums.adobe.com/message/10241266#10241266

this may be a solution to all of us – adobe needs to publish this into the code as an update IMHO

Like
(2)
2019-05-04 22:06:54
2019-05-04 22:06:54

here is an Adobe 2019 sample does the same problem with html5 only. 1st screen works but rest do  not.

Like
(2)
2019-05-04 19:13:42
2019-05-04 19:13:42

The web server must support JSON because we have zero image problems. I have tried it both with validation and without. the success action is set to the tab key. I am uploading a sample file if you would look at slide 2, it is now in captivate 2019. I turned off the navigation skin and also accessability settings. Thank you for your help.

Attachment  sample.cptx

Like
(2)
(1)
>
Dona Conn
's comment
2019-05-05 07:51:43
2019-05-05 07:51:43
>
Dona Conn
's comment

I apologize, but I don’t download files for security reasons. Still no answer to my questions, give up.

Like
(2)
2019-05-04 18:16:41
2019-05-04 18:16:41

I need it to work in HTML, I am not using SWF any longer and can not figure out why the Text entry box will not work on the Tab function. When the user presses tab, the tab key goes to the url then several other browser buttons and finally comes back to my training where i want them to only tab to the next field which is a new slide. Is there a advanced action I could record to force tab to work to go to another tab field on the same slide or to advance to the next slide?  I even updated to 2019 captivate and it still does the same thing in that version.

What is JSON?

 

Like
(2)
(1)
>
Dona Conn
's comment
2019-05-04 18:40:16
2019-05-04 18:40:16
>
Dona Conn
's comment

JSON is needed because it is used for the images. You need to check if the webserver supports it.

You didn’t answer the questions I asked about the validation nor the Success action.

Like
(2)
2019-03-31 20:22:35
2019-03-31 20:22:35

Are you on 10.0.1.286? I see that the Tab key is not working on the third slide. How did you set up the TEB? Is it validated? What is the Success action?

Like
(2)
2019-03-31 20:20:47
2019-03-31 20:20:47

No I did it only to swf.

 

Like
(2)
2019-03-31 19:58:58
2019-03-31 19:58:58

If I publish to SWF only it worked, HTML5 did not.

Like
(2)
2019-03-28 09:11:24
2019-03-28 09:11:24

Did you publish at the same time to HTML and SWF? If yes, please don’t do that anymore. Since EOL of Flash player is in the near future, keep only to HTML5 output.  Is it working in that case? Only requirement for the webserver is to support JSON.

Like
(2)
Add Comment