Not evident how to change on-change submit behavior in Tasty

[reiniervandijk]

It is often undesirable to have automatic on-change -> submit behavior for settable slot forms in Tasty. Especially with large amounts of object on the canvas, a user would like to set a batch of inputs before triggering any updates. By default, an HTML event that changes a single form element, will lead to an AJAX request. It is not evident to the user how to change this behavior. I see that as an significant shortcoming of the documentation leading to unnecessary frustration and time spent on waiting for re-visualization.

Moreover, consider that fact that the "working..." status at the bottom of the screen often goes unnoticed to newbies, in which case they happily change many settable form elements sequentially, unaware of triggering many sequential updates and eventually the risk of having a "hanging" Tasty. In the current KBE exams, easily 5-10 minutes of an hour-long session are now spent on struggling with Tasty.

[genworks]

Open for submissions: $100