- From: Jonathan Kingston via GitHub <sysbot+gh@w3.org>
- Date: Mon, 19 Sep 2016 21:51:31 +0000
- To: public-css-archive@w3.org
I noticed this when trying to draft up how this would attach to the
Fetch specification, ideally knowing the content type ahead of the
request would be better here.
The issue with supporting sounds surely would require some clearer
form of content negotation than just URL's right?
For example using URL modifiers as per the spec to be something like
this:
```
content: url('myimg.png' content-type('image/png')),
url('mysound.ogg', content-type('audio/ogg')) / "fall back text";
```
Where anything else is assumed images.
For brevity the request types of fetch could be used instead:
```
content: url('myimg.png' type('image')), url('mysound.ogg',
type('media')) / "fall back text";
```
Also the `<uri>` is still present in `<content-list>` this should
probably be changed to `<image>` right?
--
GitHub Notification of comment by jonathanKingston
Please view or discuss this issue at
https://github.com/w3c/csswg-drafts/issues/216#issuecomment-248138520
using your GitHub account
Received on Monday, 19 September 2016 21:51:37 UTC