Looking at the scenario cited in the impl issue report, the problem I see is
that the assignment of a "blank" value should not be disabled when
INTERPRET_EMPTY_STRING_SUBMITTED_VALUES_AS_NULL is enabled. But that is likely
happening because prior to this feature, a null value was interpreted as "no
The resolution I see is that if the request parameter is missing or empty, then
a null value needs to overwrite any previous value on the component. After all,
that is what is meant by INTERPRET_EMPTY_STRING_SUBMITTED_VALUES_AS_NULL.