- From: Tab Atkins Jr. <jackalmage@gmail.com>
- Date: Mon, 13 Oct 2014 13:52:37 -0700
- To: Florian Rivoal <florian@rivoal.net>
- Cc: Jens Meiert <jens@meiert.com>, www-style list <www-style@w3.org>
On Mon, Oct 13, 2014 at 1:46 PM, Florian Rivoal <florian@rivoal.net> wrote: > On Mon, 13 Oct 2014 18:20:31 +0200, Tab Atkins Jr. <jackalmage@gmail.com> > wrote: >> On Oct 13, 2014 8:16 AM, "Jens O. Meiert" <jens@meiert.com> wrote: >>> By the way, does “aliasing” entail anything other than adding “no-wrap” to >>> the list of property values? >> >> Nope, that's it. > > In this case, yes. > > Aliasing isn't a technical term, and we tend to use the word loosely to mean > "have both, and make them do the same". Sometimes more side effects are > needed to make it work smoothly, sometimes not. In the case of values, like > here, just defining the two values to both exist and to trigger the same > behavior is generally enough. > > But for instance, when we wanted to alias properties break-before and > page-break-before, we ended up doing so by making one a short-hand of the > other: > http://dev.w3.org/csswg/css-break/#page-break-properties Yeah, properties and values have different sorts of economics. We can "alias" properties by treating them as shorthands of each other, which (a) happens at a very early stage (more or less during parsing), and (b) allows you to refer to it with either name in APIs. Values don't have these sort of conveniences, so we have to a much dumber "alias" of just creating an additional value that means the same thing. ~TJ
Received on Monday, 13 October 2014 20:53:25 UTC