W3C home > Mailing lists > Public > www-style@w3.org > May 2010

Re: Box Reordering

From: David Hyatt <hyatt@apple.com>
Date: Mon, 24 May 2010 22:18:00 -0500
Cc: Alex Mogilevsky <alexmog@microsoft.com>, James Robinson <jamesr@chromium.org>, "Tab Atkins Jr." <jackalmage@gmail.com>, www-style list <www-style@w3.org>
Message-id: <2E785FD8-8BA6-45DC-B994-EF9F9F8F3570@apple.com>
To: Boris Zbarsky <bzbarsky@MIT.EDU>
On May 24, 2010, at 8:39 PM, Boris Zbarsky wrote:

> On 5/24/10 9:24 PM, Alex Mogilevsky wrote:
>> I predict that somebody will fill a Flexbox with thousands of items and
>> then use box-ordinal-group for sorting, and expect reasonable
>> performance. Then Flexbox layout not only needs a secondary storage for
>> child order and quicksort. Neither is rocket science, but if it needs to
>> be there it really should have a strong reason.
> 
> Fwiw.... the Gecko implementation is somewhat as you described, and it's not good enough for this use case if the DOM is being mutated and you have to resort.  Quicksort is typically O(N log N) or worse on nearlt-sorted data, so you get overall O(N^2 log N) behavior unless you add yet more complexity and sort lazily, etc.
> 
> The complexity is the real issue.  The non-flexbox box model is already complicated enough that defining how this new feature would interact with all the kitchen sinks already tossed in (and then implementing it) would be a major undertaking.  It doesn't obviously seem worth it.

I agree.  The implementation in WebKit is bad also (O(n^2) just to walk the kids in order).  Let's just cut it.

dave
Received on Tuesday, 25 May 2010 03:18:33 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 17:20:27 GMT