- From: L. David Baron <dbaron@dbaron.org>
- Date: Thu, 8 Oct 2015 16:20:51 -0700
- To: Boris Zbarsky <bzbarsky@mit.edu>
- Cc: www-style@w3.org
Received on Thursday, 8 October 2015 23:21:19 UTC
On Thursday 2015-10-08 19:07 -0400, Boris Zbarsky wrote:
> On 10/8/15 6:55 PM, Tab Atkins Jr. wrote:
> >I just want to make sure that I actually understand the issue here,
> >and that it's not something new and unique to the Alignment spec that
> >I'm not seeing.
>
> It's not unique, but it's an antipattern if you want this stuff to be able
> to be optimized well, and just because we made a mistake once doesn't mean
> we should make it again.
I think it may be unique to properties currently in css-align,
although one of the six problematic properties was problematic back
when it was in flexbox.
(When 'currentColor' was not a computed value, it was also present
for 'border-color' and 'outline-color', though.)
-David
--
𝄞 L. David Baron http://dbaron.org/ 𝄂
𝄢 Mozilla https://www.mozilla.org/ 𝄂
Before I built a wall I'd ask to know
What I was walling in or walling out,
And to whom I was like to give offense.
- Robert Frost, Mending Wall (1914)
Received on Thursday, 8 October 2015 23:21:19 UTC