- From: Greg Whitworth <gwhit@microsoft.com>
- Date: Sun, 22 Jun 2014 02:39:43 +0000
- To: Tab Atkins Jr. <jackalmage@gmail.com>
- CC: www-style list <www-style@w3.org>, Jon Rimmer <jon.rimmer@gmail.com>
> Absolutely, the IE/FF behaviour is preferable, and I'd prefer every browser to > match it. The problem seems to be the that definition of a "definite" size > within the spec leaves scope for different implementations to disagree about > what is and isn't definite, based on how they go about resolving constraints. > By the letter of the law, as laid out in the spec algorithm, it would seem that > Chrome is correct in treating these flex items as indefinite, even if we can > see they effectively *are* definite. > > I don't know what the answer is to that. Maybe the algorithm in the spec > needs to be changed to reflect whatever FF/IE are doing with respect to > determining that certain flex items don't need to have their content > measured. > > Jon What do you think Tab? I am more than willing to open a Chrome bug for this, I've had three flex interop bugs in the past week from live sites and this seems like one we'll hit sooner rather than later and I would prefer to avoid it. Greg
Received on Sunday, 22 June 2014 02:40:13 UTC