The Merge prompt's Review Changes slideout can take a long time to load for complex installs, but there is no indication that anything is happening during the gathering of data before a single thing appears in the panel. Good UX principles dictate a loading indicator should display during this time. Can be gated by a minimum delay (e.g. 2s).
When are you measuring the two seconds from?
Doesn't matter. The important part is to display something, anything, while the data is loading in. E.g. my install's flows file is ~450k, and the Changes panel takes about ~7 seconds to load, during which the panel is totally blank. That's poor UX.
Adding a delay before it loads is standard so as not to delay a quick load with the image load-in. 2 seconds could start counting from the time the panel loads up or some other init function.
Sorry, I don't understand where this delay is. Can you tell me what to do in order to see the problem please?
- Create a very large, highly complex install (flows file), e.g. with lots of nested subflow instances, on a moderate/slow server. As mentioned, my json exceeds 400kb.
- Get the Merge changes dialog to appear. This can be done by rushing deployments one after another, or e.g. making a change to the flows json outside the Editor (in a text editor).
- Open the Review Changes panel from that Merge Changes dialog button.
On a very complex install, the Review Changes panel takes a while to load anything in.
OK, now I understand what you are referring to. If the flow file is modified in another browser window or by another user then a notification appears 'The flows on the server have been updated' with a button 'Review Changes'. Your issue is that after clicking the button there is no indication that anything is happening until the merge dialog appears, which can take some time in the case of large flows.
Well the Merge dialog appears quickly; it just doesn't populate with the sub/flow rows for a while and remains blank during that time.