Comments (3)
Interesting point, but the imperative API doesn't necessarily mean the SMS arrived on this device (for example, it could be received on another device and sync'ed across devices, as discussed for support on desktop when Chrome has the same user signed-in). So I'm not sure if this particular difference is substantive?
from web-otp.
I suppose implementing that sort of sync (if it's both implemented and reasonably widely used) would mitigate this.
from web-otp.
That's a very interesting observation, but like @sso-google said, there isn't any guarantee in the API design that the retrieval is happening at the specific device.
Here is an example of early implementation in that direction:
https://chromium-review.googlesource.com/c/chromium/src/+/1868049
and more over here if you want to get a sense of how far ahead we are at:
https://chromium-review.googlesource.com/q/owner:goto%2540chromium.org
I suppose implementing that sort of sync (if it's both implemented and reasonably widely used) would mitigate this.
If you are feeling adventurous, you can even try it yourself :)
chrome://flags#sms-receiver-cross-device
Given this, I'm going to resolve. Feel free to re-open if the answer isn't satisfying.
from web-otp.
Related Issues (20)
- Ordering of transports in OTPCredentialRequestOptions not clear
- Editorial: [[DiscoverFromExternalSource]] uses same |options| name for two different variables
- Requirements for OTPCredentialRequestOptions.transport are incompatible with WebIDL HOT 2
- security checks in [[DiscoverFromExternalSource]] don't match those described in the security section
- Explanation for not using "trustworthy urls" is confusing
- Inaccuracies in framing of "comparable APIs" in explainer
- The specification draft link in the README is a dead link
- Repo got renamed HOT 2
- Repo is fork
- Why stop working if I add sender to my contacts? HOT 1
- Email OTP HOT 2
- Support WebOTP in cross-origin iframe
- Supported browser for WebOTP
- Support for web push notification as a transport mechanism
- web opt API not working in react.js HOT 1
- Software-based OTP Applications
- Add AbortSignal's abort reason to WebOTP
- Message access pop-up appears even after aborting. HOT 2
- Broken references in WebOTP API
- Register the `otp-credentials` in the Permissions Policy Registry
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from web-otp.