update sandboxed Google Play documentation
This commit is contained in:
parent
717f5e5b8b
commit
782969a9d1
@ -1110,14 +1110,10 @@
|
||||
cases, the functionality it offers fundamentally requires privileged
|
||||
access and cannot be supported. For example, it's unlikely Android Auto will be
|
||||
supported. The same applies to other highly invasive OS integration / control
|
||||
or privileged access to hardware. There are also a lot of features such as the
|
||||
FIDO2 security key support which could be made to fully work despite reliance
|
||||
on a lot of privileged APIs (their FIDO2 service is partially working
|
||||
already). In the case of FIDO2, we could also eventually support redirecting
|
||||
to our own implementation similarly to how we do that by default for
|
||||
geolocation. Our compatibility layer is a very actively developed work in
|
||||
progress and most of the remaining unavailable functionality is quickly
|
||||
becoming supported.</p>
|
||||
or privileged access to hardware. Our compatibility layer is a very actively
|
||||
developed work in progress and most of the remaining unavailable functionality
|
||||
is quickly becoming supported. In the future, we can also support redirection
|
||||
for more APIs such as FIDO2 rather than only the geolocation service.</p>
|
||||
|
||||
<p>Functionality depending on the OS integrating Play services and using it as
|
||||
a backend is unavailable. An OS integrating Play uses it as the backend for OS
|
||||
|
Loading…
x
Reference in New Issue
Block a user