Create an interface for tabbed browsing.
#2 Updated by Soren Stoutner over 2 years ago
https://developer.android.com/reference/android/webkit/WebSettings.html#setSupportMultipleWindows(boolean) might be one way to implement.
#4 Updated by Brian Toole over 1 year ago
I've seen tabbed browsing implemented in a few different ways, but I'm not sure which I like better.
Lightning uses a tab drawer that you swipe open from the side or press a numeric button in the upper corner to access.
Peregrine has a horizontal scroll of tabs on the bottom of the screen.
Chrome and CAF browsers have a vertical "tab stack" that you can access by pressing a numeric button at the top of the screen.
All three are pretty nice, but Peregrine's implementation has the easiest method to create and remove new tabs, with the trade-off of taking up screen real-estate that the other methods don't have.
#7 Updated by Soren Stoutner over 1 year ago
There will be controls to create and close tabs, although I haven't yet finalized where they will be in the interface.
I anticipate that it will a significant amount of work to implement a `TabView` and integrate it with the rest of Privacy Browser. For more information on the timeline, see https://www.stoutner.com/category/roadmap/.
#8 Updated by Coenie Wilkinson about 1 year ago
Whats the difference between your proposed implementation and using chrome custom tabs?
Is it imperative to create a hack for finer grained privacy?
I recently encountered accounts.google.com disallowing authentication with useragent WebView. It seems this was not the intended purpose.
#9 Updated by Soren Stoutner about 1 year ago
Chrome custom tabs opens up a tab using Google Chrome but allows the developer some control over how the UI looks so they can integrate it in their apps. As such, it has all of the privacy downsides of using Chrome. For example, from the description in the link:
1. "The browser uses Google's Safe Browsing to protect the user and the device from dangerous sites" - a list of every website you visit is sent to Google so they can spy on what you are doing.
2. "Providing a likely URL in advance to the browser, which may perform speculative work, speeding up page load time" - Google keeps track of everything you type in the URL bar, even if you don't load it.
3. "Shared cookie jar and permissions model so users don't have to log in to sites they are already connected to, or re-grant permissions they have already granted" - Google gets a copy of all your cookies.
4. "Synchronized AutoComplete across devices for better form completion" - Google saves a copy of everything you type on a webpage.
#10 Updated by Soren Stoutner about 1 year ago
"I recently encountered accounts.google.com disallowing authentication with useragent WebView. It seems this was not the intended purpose."
I assume that this is a question about how to log into Google web pages using Privacy Browser. The following steps work for me.
1. Create domain settings for "*.google.com". It is important to use a wildcard subdomain as Google loads accounts.google.com for authentication but then moves back to a different subdomain to display content.
3. Depending on which Google web page is being visited, set the user agent to WebView default. For more information, see https://www.stoutner.com/user-agent-problems/.