- From: =JeffH via GitHub <sysbot+gh@w3.org>
- Date: Wed, 06 Jun 2018 17:30:42 +0000
- To: public-webauthn@w3.org
@agl notes on webauthn call today: two parts of the issue: 1. icon can be data url 2. should brws client get the the data and pass to authnr, or give authnr the data: url and let the authnr do it... @emlun -- concerned that icon-holding data: url will be large, leave it to the client to display... @agl: limited authnrs will want the client to handle this, more capable authnrs cound deal with it themselves... perhaps we need two fields, one for URL and one for data folks note that the message gets large when the URL is data url. @emlun - **ought to point out this "can be a data: URL" and leave it at that...** @selfissued agrees @akshayku agrees, thinks incomplete soln, but good enuff for now @apowers313 notes CTAP says it can be either data: or other (http) url but does not address it further. @selfissued notes that what is actionable now is to just state this can be a data: url as @emlun suggests... and point to the RFC -- GitHub Notification of comment by equalsJeffH Please view or discuss this issue at https://github.com/w3c/webauthn/issues/930#issuecomment-395150445 using your GitHub account
Received on Wednesday, 6 June 2018 17:30:49 UTC