[UI] UI takes to long to provide feedback when changing fabrics and other entries in network/storage

[David Britton]

My observations:

1) changing the settings rapidly enough, can lead to weird UI behavior (things flipping back a couple times -- see video)

2) changing 4 or 5 things will lead to a UI update which closes the box I was just getting ready to change, before I changed it.

3) if I close the browser window after I complete the two changes in my video and come back, changes are sometimes lost.

Suggestions relating to my observations:

1) Some kind of spinner greying out the row from further operations until the update is done

2) make sure async updates don't mess with my current input

3) Set that browser flag that makes window close operations warn while that async update is happening.

Of course, I'm running this against a real MAAS that is not located in my house. I wonder if I were local in the datacenter where MAAS is running, if things would be quick and I wouldn't notice.

MAAS version: 1.9.0+bzr4533-0ubuntu1~trusty1 (stable PPA)
Angular: 1.2.11-1

[David Britton (dpb)]

BTW, along with this, it was very difficult for me to see that what I had done had just been saved to the database. I liked the automatic application of it, but I think a bit of visual feedback that what I did was just saved would be nice, even for an experienced user.

- spinner with grey-out/un-grey on table, or on row
- 'saved all changes' at the top of the table
- etc.

[Blake Rouse (blake-rouse)]

Since you were not in the data center that is why you are seeing that delay. I agree this could be improved.

[Dean Henrichsmeyer (dean)]

It also happens if you're local. If you know what you're doing (say editing multiple nodes consecutively for instance), it's unclear what is saved and what isn't.

[Lilyana Videnova (lilyanavidenova)]

This was fixed with the work we did on improving the Bonds and Bridges UI.