- From: Nicholas Shanks <nickshanks@nickshanks.com>
- Date: Thu, 21 Feb 2013 21:42:52 +0000
- To: "Tab Atkins Jr." <jackalmage@gmail.com>
- Cc: W3C CSS Mailing List <www-style@w3.org>
Received on Thursday, 21 February 2013 21:43:23 UTC
as long as the sub features have human names (english words) and not DOS 3-char file name extensions, I'm happy. On Thursday, 21 February 2013, Tab Atkins Jr. wrote: > On Thu, Feb 21, 2013 at 9:22 AM, Jake Archibald <jaffathecake@gmail.com<javascript:;>> > 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 > > -- Nicholas.
Received on Thursday, 21 February 2013 21:43:23 UTC