Comment 2 for bug 1828840

Thanks, Jane! I don't have a strong preference either way, but I have a mild preference for hiding it. My reasoning is that disabling a control is useful in cases where there's a way for a user or Evergreen admin to enable it through normal configuration action (like adding a permission or setting a library setting or the like). A control should be hidden (or *ngIf'ed away) if the only way to make it active is a code change.