Bug #11689
closed
Hidden value checkbox on global parameter form doesn't replace editor
Added by Dominic Cleal over 9 years ago.
Updated over 6 years ago.
Description
When editing a global parameter, the "Hidden value" checkbox doesn't replace the full editor (added in #11625) when checked, and the new textbox stays there when unchecked.
1. Edit a non-hidden parameter, check the "Hidden value" box and a new textbox appears between the editor toolbar and textarea. The old non-hidden value is still shown in the textarea.
2. Untick the "Hidden value" box and the new textbox remains.
3. Create a hidden parameter, untick the "Hidden value" box and the password field is replaced by a textbox and not the editor.
Files
- Status changed from New to Assigned
- Assignee set to Walden Raines
What's the expected behavior when the hidden value checkbox is checked?
It looks like it used to turn the text field into a password input which is grotesquely unsemantic and could even automatically be populated by a password via the browser or some plugin.
Does it really make sense to mask the input on the edit page? I understand not showing it on the list page but if you are going to edit a value, aren't you likely to want to see it?
Yes, the previous behaviour is the expected behaviour - to swap the text box for a password/hidden field and back.
Dominic Cleal wrote:
Yes, the previous behaviour is the expected behaviour - to swap the text box for a password/hidden field and back.
Okay, but I will mask the value using something other than a password field.
- Status changed from Assigned to Ready For Testing
- Pull request https://github.com/theforeman/foreman/pull/2706 added
- Pull request deleted (
)
- Status changed from Ready For Testing to Closed
- % Done changed from 0 to 100
- Related to Bug #11845: Hiding and then unhiding a parameter value breaks on host[group] parameters added
Also available in: Atom
PDF