Process question causes next page button to stop working when using browser
January 1, 2013 12:00 AM
I have a page with a multiple choice question with 10 answers, of which a certain number are correct - in this case 3 of the 10 are correct. The user is only told that there may be more than one correct answer.
We use feedback - show message, but we can't use immediate feedback because it triggers the message when the user has checked an equivalent number of correct answers (i.e. in this case when 3 or more check boxes are selected)
So we added a button with process question action, for the user to check their result.
This all works fine in preview but when published to HTML and viewed in browser, and the "process question" button is clicked, the "next page" button then becomes inoperable, in fact it appears that the entire navigation freezes.
I have isolated the issue in a new title with only the question, process button and next page button (with a corresponding page 2) and exported it as a zip. This is attached. It is best tested by publishing it to html, then opening one of the two pages and testing the next/previous nav buttons. These work and when the next page button is selected it process the question, as expected. BUT if you click the "process question" button once, it then freezes the nav buttons completely.
I am using Firefox 17.0.1
Any help appreciated.
Discussion (4)
Hi. We're having the same issue! Have you found a work around or solution to this?
I published that title to HTML in Lectora 11 and tested it. It works perfectly in Chrome, FF, IE10. Next button works perfectly before processing and after processing. Am I missing anything? Is the problem really there?
@MegLosee 50329 wrote:
Hi. We're having the same issue! Have you found a work around or solution to this?
Hi and thanks for replying.
I was told this:
"If it is a bug, you would need to deal directly with Trivantis support, again as you have no support with ITC Learning.
Have you been keeping your licence up to date with all new features/bug fixes? If it is a bug it may already have been fixed in a release."
As yet I haven't tried either as the project is on hold, but when the time comes I will do. Maybe you can ? I think that my simple title in which the issue is isolated, should be accessible to you from this thread. Maybe you can compare yours and mine.
thanks
DL
I tested it in Chrome and IE10 and while it worked fine in IE, and the navigation worked fine in Chrome, I didn't get any feedback in Chrome. Anyone what setting would cause that problem for me?
Discussions have been disabled for this post