Re: The CSS Problem

(12/11/14 5:47), Tab Atkins Jr. wrote:
>> 2. I was told that IE 10 only implements those that are listed on [1].
>> That is, it doesn't support 'flex-flow' (but there's 'flex-wrap') and
>> 'align-content'. Could it be that IE 10 people spend too much time on
>> other features such as Grid and Region? (Though I think the sensible
>> guess is that the good implemention is not released yet)
> 
> No, it has nothing to do with that.  IE10 entered code freeze a little
> before the CSSWG made its final changes to the spec and froze it for
> CR.  It was just a bad timing mismatch, nothing more.

It can be argued that if CSSWG had accepted fewer drafts then IE folks
might have spent more time on css-flex-1 so that css-flex-1 could have
gone to LC before the code freeze. Or you tell me why that wasn't possible.

> Note that the justify-*/align-* properties *are* supported in IE10,
> just under their earlier names (flex-pack, flex-align, etc.).

Yes, I now this equivalence. The reason I mention 'align-content' is
that the equivalent, 'flex-line-pack', isn't in [1]. I am sorry but I
don't have IE 10 at hand to test if 'flex-line-pack' is really not
supported or not.

> You shouldn't try and guess at why impls do things unless you have
> data, 

*shrug*. In any case, for Flex, I would mostly want to use the shorthand
'flex-flow' but IE 10 only has 'flex-direction' and 'flex-wrap', and I
am unlikely to want to use a Regions that can only flowed from an
<iframe> when WebKit doesn't support it. Can you argue why the status
quo would be the same if CSSWG hadn't accepted these many proposals at once?

> and you shouldn't trust performance assertions from random
> people without good data.  ^_^

That includes you too, yes. ;) (/me is asking for data)


[1] http://msdn.microsoft.com/en-us/library/ie/hh673531(v=vs.85).aspx


Cheers,
Kenny
-- 
Web Specialist, Oupeng Browser, Beijing
Try Oupeng: http://www.oupeng.com/

Received on Tuesday, 13 November 2012 22:14:33 UTC