Re: [css3-flexbox] Fixing the "replaced elements may or may not be inline" issue

Yup -- apologies if my post sounded like "OMG Mozilla will have to
change the code" -- that was not my intention. :) Boris conveyed my
concern much more clearly & generally (thanks for that).

~Daniel

On 06/27/2012 11:40 AM, Boris Zbarsky wrote:
> On 6/27/12 2:14 PM, Alex Mogilevsky wrote:
>> But the kind of arguments you bring here are exactly the kind of
>> arguments we should have when implementation affects design -- what
>> can and cannot be done with a particular design. It is much healthier
>> and more useful than knowing that some code somewhere has a problem...
> 
> Well, sure.  Daniel's problem was just that he's not an expert on the
> exact details involved, so he simply didn't have the relevant
> information.  And he said that in his post...  I'm sorry if you
> perceived him as being handwavy on purpose here.
> 
> I definitely agree that we should try to be specific about the
> structural problems with an approach, if there are any, as opposed to
> implementation difficulties in a particular implementation that don't
> have a structural underpinning.
> 
> -Boris
> 

Received on Wednesday, 27 June 2012 19:02:49 UTC