From 2389b2fa057bc99f33306c7acd063fa8e22b522a Mon Sep 17 00:00:00 2001
From: Dominik Csapak <d.csapak@proxmox.com>
Date: Tue, 15 Nov 2022 14:23:12 +0100
Subject: [PATCH] ui: backup job edit: fix form reset tracking

When the mode changes, we set the pool selector visible/hidden, but
we never disabled/enabled it. This tripped up the dirty state of the
form always showing the reset button as enabled.

Properly enabling and disabling the pool field fixes the dirty state
tracking.

Signed-off-by: Dominik Csapak <d.csapak@proxmox.com>
---
 www/manager6/dc/Backup.js | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/www/manager6/dc/Backup.js b/www/manager6/dc/Backup.js
index c81a76ce..4638cbb6 100644
--- a/www/manager6/dc/Backup.js
+++ b/www/manager6/dc/Backup.js
@@ -322,10 +322,12 @@ Ext.define('PVE.dc.BackupEdit', {
 		vmgrid.setDisabled(true);
 		vmidField.setValue('');
 		selPool.setVisible(true);
+		selPool.setDisabled(false);
 		selPool.allowBlank = false;
 		selectPoolMembers(selPool.value);
 	    } else {
 		selPool.setVisible(false);
+		selPool.setDisabled(true);
 		selPool.allowBlank = true;
 	    }
 	    let list = vmidField.getValue();