Numeric input editors should allow blank input as long as they are in focus.

GoogleCodeExporter commented 9 years ago

What steps will reproduce the problem?
1. Create an exploration whose first state has a numeric input widget.
2. Preview this exploration.

What is the expected output? What do you see instead?

When the numeric input widget appears, it contains a 0. When this zero is 
deleted, an error message appears.

A similar (but worse) problem arises if you select the music notes editor and 
choose a rule which has a number in it. If you delete the 0, a rather intrusive 
butterbar warning appears.

A proposed solution is to allow the box to be empty while the user’s mouse 
focus is inside the box. If the focus moves away from that box and the box is 
empty, its value should be reset to 0, otherwise an inline error message should 
be displayed.

Note: filed based on release testing for v1.2.10

Original issue reported on code.google.com by s...@seanlip.org on 1 Dec 2014 at 3:04

GoogleCodeExporter commented 9 years ago

Original comment by s...@seanlip.org on 7 Dec 2014 at 12:48

GoogleCodeExporter commented 9 years ago

This is partly fixed in

    https://code.google.com/p/oppia/source/detail?r=da64e48bf52004e5afc5650d9e1698f7576b8579&name=issue-488

A further fix is needed for the rule editor: the old 'int-editor' must be 
changed to use the new schema-based forms framework instead. I'll try to work 
on that next week.

Original comment by s...@seanlip.org on 15 Feb 2015 at 9:23

Changed state: Started

paulproteus / oppia

Numeric input editors should allow blank input as long as they are in focus. #488