ui: storage: use null as empty value for scanned-node selector

otherwise it can happen that there as additional change event from
null to '', even though the value did not change

Signed-off-by: Dominik Csapak <d.csapak@proxmox.com>
Signed-off-by: Thomas Lamprecht <t.lamprecht@proxmox.com>

diff --git a/www/manager6/form/StorageScanNodeSelector.js b/www/manager6/form/StorageScanNodeSelector.js
index d6c9508a1413105cdc5854ce6ef08b4ccb8be6b4..b2e013e9cb5674bcd95296050deab00ed354f6c1 100644 (file)
--- a/www/manager6/form/StorageScanNodeSelector.js
+++ b/www/manager6/form/StorageScanNodeSelector.js
@@ -9,7 +9,7 @@ Ext.define('PVE.form.StorageScanNodeSelector', {
     disallowedNodes: undefined,
     autoSelect: false,
     submitValue: false,
-    value: "",
+    value: null,
     autoEl: {
        tag: 'div',
        'data-qtip': gettext('Scan for available storages on the selected node'),
@@ -18,14 +18,16 @@ Ext.define('PVE.form.StorageScanNodeSelector', {
        clear: {
            handler: function() {
                let me = this;
-               me.setValue("");
+               me.setValue(null);
            },
        },
     },
 
+    emptyText: Proxmox.NodeName,
+
     setValue: function(value) {
        let me = this;
        me.callParent([value]);
-       me.triggers.clear.setVisible(value !== "");
+       me.triggers.clear.setVisible(!!value);
     },
 });