No. This is not a limitation of Bromite but of all Chromium-based projects in general, as general public is not allowed to use Google's APIs for free unless when using Chrome.
Additionally, these features would not be privacy-friendly.
No.
Yes, although this has not been verified (and hardly can be) under all situations; if you were to find connections to cloud-based services please report them via the issue tracker.
Bromite uses ungoogled-chromium's python script to disable URLs in the codebase since version 78.0.3904.93.
Projects which follow a strict approach on this are Iridium and Inox patchset.
Yes, in order to play protected/encrypted media content the browser will use Android's DRM media framework to automatically negotiate access (same as Chromium).
This means for example that requests to Android license servers will be performed (www.googleapis.com), see https://w3c.github.io/encrypted-media/#direct-individualization
To disable this functionality you should disable protected content playback from Site settings -> Protected Content.
It is the core component of Android for all web page visualizations. For example when you access a new wifi network and need to activate it, that is using the SystemWebView. If you do not know what it is then you do not need to install it.
See also the wiki page for community-contributed installation instructions.
Ad-blocking was present and always enabled in the SystemWebView from version 72.0.3626.120 till version 77.0.3865.104, when it stopped working due to upstream NetworkService changes.
See this page.
No. We cannot add add-ons to Bromite (merely some features).
No, and this is not going to change. Many limitations apply for submissions there, including which ads are allowed to be blocked.
Bromite favors user freedom in software choice: the device is yours so you get to choose which software to run on it, end of the story.
It is not on the official F-Droid repository and there are no (more) plans to submit it.
You can use F-Droid client to install and receive updates via the official Bromite F-Droid repository.
Partially, see https://github.com/bromite/bromite/wiki/WebRTC
Using Bromite will favour the monopoly of the Chromium/Blink engine, why do you develop and maintain Bromite?
In short, to show what a Chromium-based engine could do for the user if the user experience and needs were the main focus of modern browser design.
For an Android browser using an alternative engine see Fennec F-Droid.
No; Bromite will support extensions only if upstream (Chromium) does, or similarly another project maintains the patch and functionality.
The Chromium Blink engine uses GCM to deliver messages when websites use the Push API; this will not work in Bromite because cloud integrations are disabled (GCM in this case).
ServiceWorker notifications do work instead since they use android.app.Notification.
PWAs are only supported as home shortcuts; WebAPKs will not work because they are generated server-side on googleapis.com (which is not allowed in Bromite).
Yes, since version 94.0.4606.109 the native Android autofill can be used; this does not require accessibility services as a workaround.
No, this would require Play Store binary blobs.
No. Bromite does not make any choice related to default search engines, the Chromium default is used. Various Android browsers get some fee to ship their apps with a specific default search engine, Bromite does not get any fee from anyone. Changing the default search engine would lead to an endless series of requests to change it based on personal preferences, thus no change is made to the default. See also: https://github.com/bromite/bromite/wiki/SearchEngines
You can compare the blocked URLs with a desktop browser and Bromite (using remote debugging) and figure out some new filter rules to be added. If the ads are blocked via cosmetic filtering then blocking them is not possible with Bromite's engine and you might need something like an user script instead. See also: https://github.com/bromite/bromite/wiki/AdBlocking