-
Notifications
You must be signed in to change notification settings - Fork 347
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
History to be separate for each container #1233
Comments
See #537; click the Thumbs Up below the request to vote for it. |
Yes. This looks like a duplicate of #537. Please vote (:+1:) or discuss on that issue to show your interest. I'll close this, but feel free to reopen if you think it's a different issue. |
@kendallcorner I think this (and #1544) are somewhat different from #537: this issue wants the history to be completely isolated from other containers, while my request in #537 was merely to use it as a signal in the ranking, i.e. sites visited in another container would still be suggested, but just less prominently than sites often visited in the current container. |
Agreed. If your browsing history is still shared, using a different browser for specific personas is still a more tidy solution. +1 on this request. |
I would like to request that history be made per-container, so that the history for one container is separate from the history for another container. The omnibar should only show URLs from the history of the current container. This is quite important to my use case. I use per-account containers to keep separate browsing contexts, and I don't want URLs from different contexts showing up in the omnibar.
For some reason I had assumed this was the case with per-account containers already. I just realized it's not, and I think it reduces the usefulness of this feature significantly. Please consider adding this!
The text was updated successfully, but these errors were encountered: