It'd be pretty simple to enforce sandbox/parental controls for the integrated webview browser.
1. Just limit the webview browser location to the same list as allowed by the parental control.
2. By default limit the webview browser location to the domain first opened by the app i.e locked to a single domain by default.
3. Allow webview browser to be expanded via a regex/pattern list of domains.
4. Limit the number of webview browser location changes so even if you can access a search engine with a global domain allowlist, it would just return to the first page after N window.location changes.
There's plenty of introspection you can do via JS (which is already being used to set/inject that `mm` object), it could even check for certain DOM elements, HTTPS fingerprint, etc. to determine if the page is an "intended" destination for the particular integrated webview browser.
1. Just limit the webview browser location to the same list as allowed by the parental control.
2. By default limit the webview browser location to the domain first opened by the app i.e locked to a single domain by default.
3. Allow webview browser to be expanded via a regex/pattern list of domains.
4. Limit the number of webview browser location changes so even if you can access a search engine with a global domain allowlist, it would just return to the first page after N window.location changes.
There's plenty of introspection you can do via JS (which is already being used to set/inject that `mm` object), it could even check for certain DOM elements, HTTPS fingerprint, etc. to determine if the page is an "intended" destination for the particular integrated webview browser.