bvandersloot-mozilla
bvandersloot-mozilla
We identified a potential need for a more sustainable no-cors mode in discussion surrounding FedCM. The purpose is to create a browser-process priveleged mode that will not fail the Access-Control-Allow-Origin...
Consider the domains from the spec as an example: - Set primary: `exampleA.com` - Service: `exampleA-usercontent.com` - Associated: `exampleB.com` From the spec it is clear that as a top-level context...
There are several details of the set validation process that are left out at this point. Since the spec recently converted away from leaving this to a trusted-third party (the...
The privacy property in the principles is "Prevent website from silently querying for the availability of digital credentials and communicating with wallet providers without explicit user consent" which, while good,...
When building a privacy model, selective disclosure is a key feature of the lower protocols and formats being used by this API. However, the properties of that selective disclosure are...
This is a consequence of a few related issues: #35, #32, and #30. Put simply, this API enables gating web content behind holding a government issued credential with particular properties....
This is an addition that tries to create a point for further communication about deprecation and removal of web features, as we determined may be useful at TPAC in the...
### What is the issue with the Compatibility Standard? We identified this may be a good venue to talk about the problem of deprecation on the Web and addressing compat...