Details
-
Bug
-
Status: Open
-
Minor
-
Resolution: Unresolved
-
1.15.1
-
None
-
None
Description
Currently, when a new parameter value is set to an empty string and marked as sensitive, and if the Parameter Context has not been saved yet, if you edit the same parameter and check the "Set empty string" box again, the "Apply" button will become disabled, since technically the value hasn't changed. See attached gif.
We never want to indicate what a sensitive value may be. The check behavior should be updated by comparing whether a change has been made in the value keydown, not by comparing whether the values match or not.