Univention Bugzilla – Bug 34181
During app installation: Transition of progressbar between software tests and installation routine looks buggy
Last modified: 2014-02-27 12:58:38 CET
Fix does not work in a special situation: When the progressbar is set to "indeterminate" by some progress info sent from the backend, Infinity has to be sent as string "Infinity" because json does not support Infinity (python side does, but js side does not). Thus, the check var comesFromOrGoesToInfinity = oldValue === Infinity || newValue === Infinity; has to be adjusted: var comesFromOrGoesToInfinity = parseFloat(oldValue) === Infinity || parseFloat(newValue) === Infinity; +++ This bug was initially created as a clone of Bug #32649 +++ Reason is the "indeterminate" value of the progressbar during software tests and the "0" value when the installation begins. There is a transition effect that goes from 100 to 0 and lasts just long enough for users to wonder why the progress goes in the wrong direction. The transition is a CSS effect. Remove this effect by watch(progressbar, 'indeterminate') and (un)set a class: .noTransition { -webkit-transition-property: none; -moz-transition-property: none transition-property: none; -webkit-transition-duration: 0; -moz-transition-duration: 0; transition-duration: 0; } This problem is App Center specific (because indeterminate is used only there) but should be fixed generically in umc/widgets/ProgressBar.
Fixed in univention-management-console-frontend 3.0.152-22.820.201402251020 Found a better (shorter) way of doing it instead of parseFloat(). The way dojo does it: Instead of using value === Infinity, I now use value == Infinity
looks good YAML OK
http://errata.univention.de/ucs/3.2/64.html