- From: Tim Panton via GitHub <sysbot+gh@w3.org>
- Date: Fri, 08 Feb 2019 09:13:24 +0000
- To: public-webrtc-logs@w3.org
So here is a practical example I'm hitting: We allow a user to 'lend' access to a resource. This is done by the 'lender' establishing Data Channels with the device and the borrower. The borrower then sends credentials to the resource _via_ the lender - the resource accepts them because of their provenance. We initiate (and validate) this transaction with a QR code shown on the lender's browser. The borrower scans it and uses the info to open a Data Channel to the lender. What we are seeing is that the Data Channel path is different if the borrower uses the native camera app as a QR code reader vs when they use a javascript one built into the web page which uses GUM and asks for permissions. This means we have to encourage users to avoid the much better native QR code reader - which makes me sad. -- GitHub Notification of comment by steely-glint Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/2012#issuecomment-461737721 using your GitHub account
Received on Friday, 8 February 2019 09:13:26 UTC