Bug 1568753 Comment 0 Edit History

Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.

Original comment by
on 
I may have found a bug with the new password masking APIs but I'm not sure if an empty fields is supposed to behave in a special way:
STR:
1) Have an **empty** type=password field
2) `field.editor.autoMaskingEnabled` => `true`
3) `field.editor.unmask(0)`
4) `field.editor.autoMaskingEnabled` => `false`
5) `field.editor.mask()`

Expected result:
* Field should be masked again for future input
* `field.editor.autoMaskingEnabled` should be `true`

Actual result:
* Field is masked for future input
* `NS_ERROR_ILLEGAL_VALUE` thrown from nsIEditor.mask
* `field.editor.autoMaskingEnabled` is `true`  (changed from false to true despite the error)
Revision 1 by
on 
I may have found a bug with the new password masking APIs but I'm not sure if an empty field is supposed to behave in a special way:
STR:
1) Have an **empty** type=password field
2) `field.editor.autoMaskingEnabled` => `true`
3) `field.editor.unmask(0)`
4) `field.editor.autoMaskingEnabled` => `false`
5) `field.editor.mask()`

Expected result:
* Field should be masked again for future input
* `field.editor.autoMaskingEnabled` should be `true`

Actual result:
* Field is masked for future input
* `NS_ERROR_ILLEGAL_VALUE` thrown from nsIEditor.mask
* `field.editor.autoMaskingEnabled` is `true`  (changed from false to true despite the error)

Back to Bug 1568753 Comment 0