Re: [whatwg] [csswg][css-display] Updated WD of CSS Display L3

2017-01-25 Thread Boris Zbarsky
On 1/25/17 10:48 PM, Florian Rivoal wrote: Is it a general argument that adding more things to the platform always makes it harder down the road to add more things due to having to figure out more interactions It's not a general argument in this case. It's a specific argument. For example,

Re: [whatwg] [csswg][css-display] Updated WD of CSS Display L3

2017-01-25 Thread Florian Rivoal
> On Jan 26, 2017, at 12:23, Boris Zbarsky wrote: > > It will complicate attempts to add other, much higher value, features to > CSS, again both in terms of specification and implementation. Could you elaborate on that? Is it a general argument that adding more things to

[whatwg] [csswg][css-display] Updated WD of CSS Display L3

2017-01-25 Thread fantasai
at: https://www.w3.org/TR/2017/WD-css-display-3-20170125/#changes We anticipate this being the last draft before the transition to CR, therefore this is the "last call" for comments. Please review the draft, and send any comments to the CSSWG mailing list, <www-st...@w3.org>, prefixed w

Re: [whatwg] [csswg][css-display] Updated WD of CSS Display L3

2017-01-25 Thread Boris Zbarsky
On 1/25/17 8:14 PM, fantasai wrote: * a 'run-in' layout model slightly less insane than the one proposed in CSS2.0 I like the truth in advertising there. ;) I'd just like to reiterate my (longstanding, so unlikely to sway anyone) opinion that run-in, even in this "less insane"