- From: Tab Atkins Jr. <jackalmage@gmail.com>
- Date: Thu, 21 Feb 2013 09:15:52 -0800
- To: Yoav Weiss <yoav@yoav.ws>
- Cc: Liam Quin <liam@w3.org>, Jake Archibald <jaffathecake@gmail.com>, Henrik Andersson <henke@henke37.cjb.net>, "Robert O'Callahan" <robert@ocallahan.org>, Brad Kemper <brad.kemper@gmail.com>, W3C CSS Mailing List <www-style@w3.org>
On Thu, Feb 21, 2013 at 1:07 AM, Yoav Weiss <yoav@yoav.ws> wrote:
> While I'm not sure mime-types are necessary (they're more verbose than may
> be required), this actually allows an author to declare that a certain image
> contains several sub-types that may not be supported by the browser.
> Let's say for example that JPEG arithmetic coding was supported by some
> browsers and JPEG hierarchical coding was supported by others, with some
> overlap in their support.
> format("image.jpeg", "hierarchical", "arithmetic") would allow an author to
> define an image that contains both sub-types, without the need to define all
> possible permutations in the spec.
>
> OTOH, I'm not sure such a scenario is a realistic future scenario, and it
> might be easier to extend the syntax in the future, if & when that need
> arises.
The ability to specify multiple subtypes sounds compelling.
~TJ
Received on Thursday, 21 February 2013 17:16:44 UTC