Feature #322
open
Consider using the Bromite SystemWebView instead of creating Privacy WebView
Added by Soren Stoutner over 5 years ago.
Updated over 1 year ago.
Description
It is always easier to use an existing project instead of creating your own. I just need to spend some time to see if Bromite SystemWebView is moving in the same direction of what I have planned with Privacy Browser and if they are amenable to have me involved as a contributor and open to any additional changes I need to make.
Android already has ability to change webview from developer options. And yes. Bromite Webview's working asusual with pb. Not an issue at all.
Privacy Browser indeed does work just fine with Bromite SystemWebView. However, SystemWebView doesn't contain most of the changes that are needed to support the desired features in the 4.x series. It is premature to say if it would be less effort to work with Bromite to integrate the changes I need into SystemWebView or to develop Privacy WebView myself. I expect to spend some time investigating that issue when the close of the 3.x series draws near.
Oh. I thought priority ranges completely wrong. I though 4.x > 1.x, caz 4 is larger ¯\(°_o)/¯
Yes, for historical reasons I am using the Priority field as a target version number field.
Currently Privacy Browser is version 3.11. Every but report and feature request in the 3.x series will be implemented before Privacy Browser releases version 4.0.
Also available in: Atom
PDF