Comment 8 for bug 1812900

I note that the patch for bug 1793196 that moved one of the calls to $scope.fetchDefaults() seemed to caused (or revealed) the issue between 3.1.10 and 3.1.11, but that doesn't account for why folks also saw the problem in 3.2.2.