156a224fcd1f553e30dfd174922c6be15303b4f3
When browsing changes it is very common for a user to be on their own dashboard, click on a change, jump back, then jump to another change. We want to make the "jump back" part really fast. Its unlikely that the data in the dashboard has really changed since the last time the user looked at it, so recycling the entire widget graph saves us time in constructing the DOM elements over again for the table. If rows did get removed or were inserted the table will update itself once the RPC call is complete. Signed-off-by: Shawn O. Pearce <sop@google.com>
Description
RETIRED, Gerrit as used by OpenStack