Add to browser's history instead of replacing for the first navigation to content

First navigation to content perspective causes parent.updateNavLocation() invocation which leads to replacing the current entry in the browser's history. This behavior suppresses the proper history stacking and in a case of a navigation sequence "home -> content search (click on a document) => (internal navigation to) content" prevent's normal back navigation so back button click navigates to home instead of content search.

Supposedly the problem can be fixed either by preventing parent.updateNavLocation() when content perspective is being opened or adding addHistory option for updateNavLocation().