W3C home > Mailing lists > Public > www-style@w3.org > October 2011

RE: [css3-*] Defining support for the inherit keyword

From: Sylvain Galineau <sylvaing@microsoft.com>
Date: Fri, 28 Oct 2011 17:18:46 +0000
To: Boris Zbarsky <bzbarsky@MIT.EDU>
CC: "www-style@w3.org" <www-style@w3.org>
Message-ID: <3C4041FF83E1E04A986B6DC50F0178290334214C@TK5EX14MBXC296.redmond.corp.microsoft.com>

[Boris Zbarsky:]
> I don't see why the core syntax being defined in one place as opposed to
> every spec copy/pasting it and getting out of sync is getting labeled as
> "confusion" here.

You're right; faulty inference on my part here. I think we're in violent 
agreement: of all the ways to be consistent, I prefer those that are 
explicit but consistency really is the proper goal.

> I see the inherit/initial/whatever issue as similar: having it defined in
> one place that all other specs simply reference is the thing that will
> minimize confusion going forward.
> The only reason it's being a problem right now, as far as I can see, is
> that CSS3 modules are not consistent about the way they handle it.  I
> absolutely agree they should be consistent; I just think they should
> converge on referencing a single central location for this instead of
> duplicating things.
> > Sure. I have no issue with that, as long as the dependency from
> > values/types to their central definition is explicit, visible and
> > unambiguous. And whatever the solution, I would  like us to be
> consistent.
> Yes, absolutely.  Consistency is key here.  The current state of things is
> broken.
> -Boris
Received on Friday, 28 October 2011 17:19:17 UTC

This archive was generated by hypermail 2.4.0 : Friday, 25 March 2022 10:08:06 UTC