- From: Tab Atkins Jr. <jackalmage@gmail.com>
- Date: Thu, 21 Feb 2013 09:36:54 -0800
- To: Jake Archibald <jaffathecake@gmail.com>
- Cc: Henrik Andersson <henke@henke37.cjb.net>, Rik Cabanier <cabanier@gmail.com>, Brad Kemper <brad.kemper@gmail.com>, "robert@ocallahan.org" <robert@ocallahan.org>, "liam@w3.org" <liam@w3.org>, W3C CSS Mailing List <www-style@w3.org>
On Thu, Feb 21, 2013 at 9:22 AM, Jake Archibald <jaffathecake@gmail.com> wrote:
> +1
>
> I'd prefer type('image/whatever', 'subfeature', 'another-feature') to
> keep it distinct from @font-face's format(), which doesn't use mime
> types.
>
> The spec would define the sub-features as and when needed.
Yes, I'm fine with this. I'll give it a slightly more CSS-y syntax:
type("image/foo" subfeature1 subfeature2)
This follows the tradition of "things imported from outside CSS are
strings, things inside CSS are idents", and omits unnecessary commas.
This does mean we're still gated on the spec defining subfeatures, but
perhaps I can fob that off to a wiki or a registry somewhere.
~TJ
Received on Thursday, 21 February 2013 17:37:46 UTC