W3C home > Mailing lists > Public > whatwg@whatwg.org > November 2012

Re: [whatwg] Sortable Tables

From: Tab Atkins Jr. <jackalmage@gmail.com>
Date: Thu, 8 Nov 2012 09:29:06 -0800
Message-ID: <CAAWBYDCZv7wu_jBGc97q_xpQ5RCbC3Z0_u1nehY14UgYMt5tbQ@mail.gmail.com>
To: Ojan Vafai <ojan@chromium.org>
Cc: WHATWG List <whatwg@whatwg.org>, Alex Russell <slightlyoff@google.com>, Ian Hickson <ian@hixie.ch>, Rafael Weinstein <rafaelw@google.com>, Adam Klein <adamk@chromium.org>
On Thu, Nov 8, 2012 at 8:59 AM, Ojan Vafai <ojan@chromium.org> wrote:
> On Thu, Nov 8, 2012 at 4:17 AM, Alex Russell <slightlyoff@google.com> wrote:
>> I'm much more inclined to solve this from the data axis. Asking the table
>> itself to do the sorting is weird. Instead, you most often want to have
>> some data source return you rows in sorted order (or indicate row order).
>> If you do something like MDV, sorting the table is applying a sort to the
>> template that stamped out the view. That works with DOM-table backed tables
>> as well as server or JS-backed tables.
>
> I like this approach. One thing this loses is having default styling for
> sortable headers. It would be awesome if sortable tables looked the same
> across pages instead of each page needing to invent their own up/down arrow
> UI.

Agreed, I favor a DOM-based solution because of this.

> Also, is MDV intelligent enough to know that you just moved items around or
> will it clobber and recreate the entire DOM?

It *should* be intelligent enough to recognize moves, as opposed to
just add/deletes.  Ask Raf or Adam about their progress on getting
this done.

~TJ
Received on Thursday, 8 November 2012 17:44:50 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 30 January 2013 18:48:11 GMT