[Registries configuration page] "Start scan" button is not grayed out immediately after clicking "Start scan" button

[williamshen9999]

Please refer to #321

However, I would want to double confirm again if there will be chance to fix (or even improve) before v1.0.0?
For 321:
I won't know if I really click the "Start scan" button successfully or not?... (coz the button is not grayed out immediately after I click it...)

[fabriziosestito]

If something goes wrong when starting a scan (which basically means creating a ScanJob in the background), an error will show up in the UI.

Not totally sure about the “greyed out” behavior, maybe @xingzhang-suse can clarify.

[xingzhang-suse]

Hi @fabriziosestito, I think the corner case is wethere we should gray out the button, if the scan is pending/scheduled/in progress for a long time, or the scan is stuck.
I know the backend has a handling for triggering a in process scan, it will return error while user click the start scan button.
So we need to discussion whether we need to gray out it in this case.

[fabriziosestito]

If the backend returns an error from the webhook, the scan job will not be created. In this scenario, the button should not be greyed out.