01fd96240cf3dce30ffb09383547a0559c4edd2c
We used to call renderRevisionInfo(...) first on page load to have the revision action related UI properly initialized, and then again when the callback determined which revision action buttons should be displayed. However by calling that method twice, the history and comments each showed up twice as well. The first initialization of the revision action related parts of the UI on page load do not need a call to the full grown renderRevisionInfo(...), but only hiding UI elements, such that the user doesn't see the UI elements popping up for a split second. Change-Id: I649af53ea56e63febbb9144a6eae306e2db4269e
Description
RETIRED, Gerrit as used by OpenStack