![]() Definitely not a solution for the less savvy. I can get by on this as a temporary solution, though it breaks auto-update for the 1Password app if I do that. I was able to get 1Password to treat Bromite like a browser just by making a patched 1Password APK with an extra line in the .KnownBrowser enum. Moreover 1Password autofill already works in Bromite, so it seems weird that getting URL-based entry filtering is only available if the browser is on a hardcoded list. From my understanding Bromite's been decently popular in the Android privacy space and is a commonly used alternative browser with GrapheneOS. The only other Android browser that offers Chromium with a decent ad blocker and useful UI tweaks is Brave, and Brave is becoming less appealing as it turns more and more into adware. ![]() My interest in Bromite is it being a Chromium fork that adds back good expired flags (like bottom navigation) without adding much cruft. This was suggested back in 2020 but the topic was closed without much discussion. If that's the case it should be trivial to support Bromite as a browser instead of just a generic app. I'm not super familiar with 1Password for Android's internals, but it seems to me like browser support is hardcoded and not actual compatibility checks. It's getting pretty annoying to have to tap "Open 1Password", find the corresponding login, and tap to fill once when 1Password should be able to treat it like any other Chrome fork and filter by URL. The problem is 1Password doesn't recognize it as a browser, so instead of offering/saving logins to the corresponding URL it scopes everything to the browser app itself. Could 1Password please add Bromite () as a supported browser for autofill? Since it's a patched version of Chromium for Android (just with some privacy/usability tweaks), it's already compatible with Android system autofill.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |