- From: BigBlueHat via GitHub <sysbot+gh@w3.org>
- Date: Wed, 25 Aug 2021 20:22:56 +0000
- To: public-css-archive@w3.org
> If we went that way, we already have `data:` urls for that purpose; you'd just need to mint a qr code MIME type, where the resource data is intended to be interpreted as a qr code. Like `data:image/qrcode,https://example.com` Not sure a media type is necessary (or wise) in this case. Media types shouldn't generally describe what's inside the package--just the packaging. 😃 And qrcode's themselves are "shipped" in all kinds of `image/*` packages currently (and it should stay that way). The point of this proposal (as I understand it) is to have the browser turn strings into QR codes with minimal effort. Using the `data:` URL wouldn't provide for that; just an alternate means of shipping an existing image, and extending it to be more than a means of conveyance would be concerning. -- GitHub Notification of comment by BigBlueHat Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/6544#issuecomment-905847450 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 25 August 2021 20:22:58 UTC