Example: Currently, when a collection is renamed, the page scrolls to the top: this can be inconvenient for large numbers of collections.

Generally, refreshing an entire tab causes a loss of UI state. Until a framework is in place for updating content without losing UI state, websocket→reload behavior should be confined to content that is important to keep up-to-date and does not have UI state (e.g., pipeline status).

Many cases can probably be covered systematically by adding a check to the tab-refresh handler: If a tab's content includes elements whose attributes indicate infinite-scroll behavior, do not refresh it.