-
-
Notifications
You must be signed in to change notification settings - Fork 14
Description
Hey there. Love quite a bit about this browser so far, happy to see such active development on it!
There is a behavior I'm noticing which I'm not sure is purposeful or an oversight, but I feel that it defeats the purpose of enforcing authentication on tabs within a container.
In list and grid mode in the tab view, tabs behave as I'd expect when using a container with authentication. Not visible until a passcode is entered and separated from the main tabs. However, in tree view mode, it seems to display all tabs, regardless of if they are private tabs or whether they are tabs with isolated cookies/authentication in a separate container. Here are some screenshots of the behavior:
I feel as though tree view can be a very useful tool, but that it should be a tree view that shows all tabs within either the same container or the same cookie session. Perhaps a setting to toggle which preferred behavior the user would like? I may not be the best voice for implementation of that decision lol.
Anyway, hopefully the screenshots demonstrating the issue make it clearer. Here's one also showing the settings used to create the container:
Thanks again for the hard work on this browser, I'm glad to see a new, promising open source android browser on the block!



