Bug 37929 - no standby animation during object loading
no standby animation during object loading
Status: RESOLVED WONTFIX
Product: UCS
Classification: Unclassified
Component: UMC (Generic)
UCS 4.0
Other Linux
: P5 normal (vote)
: UCS 4.0-x
Assigned To: UMC maintainers
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2015-03-03 17:08 CET by Florian Best
Modified: 2019-01-03 07:17 CET (History)
1 user (show)

See Also:
What kind of report is it?: ---
What type of bug is this?: ---
Who will be affected by this bug?: ---
How will those affected feel about the bug?: ---
User Pain:
Enterprise Customer affected?:
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:
Bug group (optional): Large environments
Max CVSS v3 score:
best: Patch_Available+


Attachments
example fix (798 bytes, patch)
2015-03-03 17:08 CET, Florian Best
Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Florian Best univentionstaff 2015-03-03 17:08:39 CET
Created attachment 6735 [details]
example fix

There is no standby animation during the udm/get call (loading of object) so the form is released before the original values are entered. In case of a large environment where the udm/get takes longer than 2 seconds this is disturbing. In my example it takes 40 seconds.

The problem is that in DetailPage.js this.standby(false) is called without concerning that some standbyDuring() calls are active.

I am not sure if this should be fixed directly in StandyMixin (could be done on purpose). Otherwise we have to fix DetailPage.js in udm.
Comment 1 Stefan Gohmann univentionstaff 2019-01-03 07:17:14 CET
This issue has been filled against UCS 4.0. The maintenance with bug and security fixes for UCS 4.0 has ended on 31st of May 2016.

Customers still on UCS 4.0 are encouraged to update to UCS 4.3. Please contact
your partner or Univention for any questions.

If this issue still occurs in newer UCS versions, please use "Clone this bug" or simply reopen the issue. In this case please provide detailed information on how this issue is affecting you.