Thanks for picking up the error of the lower-case 'i'. Fixed now.
I've changed the "Thanks for Markus Gafner" paragraph to
As an example application of this capability, see this CodeRunner author's forum thread where Markus Gafner (who contributed this workaround) shows a TextUI question with an embedded GraphUI question, plus other embedded questions.
I do always use grunt to rebuild the 'build' versions of amd modules before committing. But when I merged your pull request into master I made the mistake of assuming you had included any changed code in the pull request. However, I don't think it breaks anything - your textareaId feature isn't documented in the master branch yet and the fact that it doesn't work in the 'build' version shouldn't be a problem.
I'm sorry to hear about the failures in the test last week. Indeed if you depend entirely on "Open attempts are submitted automatically" it seems there's a problem, which I wasn't aware of.
The contents of the various CodeRunner UI elements are sync'd back to the underlying textarea answerbox only when a question is saved or submitted, which includes:
- when the student clicks Check or Precheck,
- when the user navigates to a different quiz page
- when the user explicitly submits their quiz.
I would have expected the "Open attempts are submitted automatically" feature, which is implemented in JavaScript, would initiate a submit operation on the form which should have in turn called my own sync code. But that seems not to be happening. I'll look into it. But I fear that the data is lost - all that is getting sent to the server on a quiz timeout is the unsync'd raw text area contents.