Univention Bugzilla – Full Text Bug Listing |
Summary: | It takes not long enough to open a user | ||
---|---|---|---|
Product: | UCS | Reporter: | Dirk Wiesenthal <wiesenthal> |
Component: | UMC - Domain management (Generic) | Assignee: | UMC maintainers <umc-maintainers> |
Status: | RESOLVED DUPLICATE | QA Contact: | |
Severity: | normal | ||
Priority: | P5 | CC: | best, gohmann, klaeser, troeder, wiesenthal |
Version: | UCS 4.0 | ||
Target Milestone: | UCS 3.2-x | ||
Hardware: | Other | ||
OS: | Linux | ||
See Also: |
https://forge.univention.org/bugzilla/show_bug.cgi?id=37929 https://forge.univention.org/bugzilla/show_bug.cgi?id=45574 |
||
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): | ||
Max CVSS v3 score: | |||
Bug Depends on: | 32978 | ||
Bug Blocks: |
Description
Dirk Wiesenthal
2013-11-06 12:46:27 CET
Probably, each value needs to be set separately according to the widget's "ready" state. The detailpage should not be visible (or at least covered by standby / progressbar) before all values are collected from server and set into the widgets. (In reply to Florian Best from comment #2) > The detailpage should not be visible (or at least covered by standby / > progressbar) before all values are collected from server and set into the > widgets. But this is intentionally not done so strictly due to Bug #32978. We were just too greedy here. Is it only a problem for the printer module? Maybe we could decide in the UDM module whether it should be wait for all values and show an animation / progress. (In reply to Stefan Gohmann from comment #4) > Is it only a problem for the printer module? → No, it applies to every module. From Bug 32978, comment 1: > [...] > * The form is shown as soon as it is rendered. Until all dynamic values > (i.e., combo boxes) have been loaded, the submit button is disabled. This should explain the behaviour. It was a decision taken at Bug 32978... I do not remember to which extent it was discussed, though :) . Would it be possible to disable a widget (hinting "loading...") until it has loaded its value? |