2.0: New UI via Endless Browser (was: tabbed browsing / firefox-ios UI?) about onionbrowser HOT 11 CLOSED

A few folks and I actually thought about that. Looks like they were implementing their own network stack (which is how they had their Data Saver compression proxy and other neat things) in Chrome iOS, but at some point they updated to use WKWebView and stopped doing this.

https://support.google.com/chrome/answer/6323113

Features not available on iPhone and iPad
Some of your Chrome features and settings will not be available at this time because of iOS constraints. Downloads that require authentication might not work, and the following features and settings had to be removed:

Data Saver
Cookie settings
Auto-Detect Encoding
Do Not Track setting
Enterprise support and multi-profiles
If Apple makes changes to WKWebView to allow these features, we will add them back in.

We interpret this this to mean that they ran into the same limitation with the new API and actually had to stop using their own network stack. So, super interesting.

from onionbrowser.

this would be HUGE! yes please.

from onionbrowser.

Will look into getting this to work this month. Hopefully. (Working on #14 first — bookmarking/customizable home page.)

from onionbrowser.

+1 for this! Thanks for the awesome app, the world needs more people like you in it. Keep up the good work.

from onionbrowser.

https://www.cocoacontrols.com/controls/qmbtabs is easy to use and works. Needs reordering, but that's the top of the list.

from onionbrowser.

Would like this feature too, thanks! Are you still working on it @mtigas?

from onionbrowser.

Would it be a good idea to re-implement the current Tor functionality into a fork of mozilla/firefox-ios or brave/browser-ios (which itself builds upon firefox-ios)? That would free you from caring about building a browser and just focus on the Tor functionality (so rather similar to what the TorBrowser project does).

from onionbrowser.

@fbender Both Firefox and Brave appear to use the newer WKWebView API, which in #47 we realized completely disallows us from using NSURLProtocol to intercept HTTP requests and route them through our Tor process.

That said, I'm actually working on a totally-rewritten Onion Browser 2.0 that is essentially a fork of https://github.com/jcs/endless for the exact reasons you mention. Lemme update this ticket to reflect that.

from onionbrowser.

Good to know. But how does Google do it with their Chrome Browser? They are using their own network stack and should be using WKWebView as well. Maybe they reimplemented everything on top of raw TCP streams? That should be somewhere in the Chromium source code I presume …

from onionbrowser.

I've had a radar open for this since April 15, 2015: http://www.openradar.me/radar?id=5547938658910208

No response from Apple.

from onionbrowser.

Since Onion Browser 2 is now released, I close this issue. Feel free to reopen, if I missed something.

from onionbrowser.