View Full Version : Incorrect handling of configs: autoCapitalize, autoComplete, autoCorrect, (etc.?)

17 Feb 2012, 7:00 AM
These tri-state (true/false/null) boolean-type configurations are displaying as checkboxes in the component configs.

Checking them means true, but unchecking them seems to mean use component default, not false. In these cases, the defaults of these is null.

There seems to be no way to make these configuration options get saved with a false value, and this might extend out to other true/false/null configuration options. Without the ability to set these config options to false, some of my textfields are resulting in some pretty poor usability.

I would perhaps suggest a typical tri-state checkbox for these configuration types, with the grayed state representing the default/inherited value.

17 Feb 2012, 8:34 AM
Handling the tri-state nature of boolean configurations is already scheduled to be addressed in our next sprint. Thanks for the suggestions.

29 May 2013, 8:06 AM
Any progress on this. I just got bit by the same problem.