Opened 13 years ago

Closed 13 years ago

Last modified 13 years ago

#2593 closed defect (invalid)

FilteringTable sort fails in 0.4.2rc1 & 2

Reported by: dojo@… Owned by: bill
Priority: blocker Milestone:
Component: Widgets Version: 0.4.2rc1
Keywords: Cc:
Blocked By: Blocking:

Description

The attached example illustrates a problem where the "value" attribute associated with a row is apparently never set or is silently removed elsewhere. When the sorter routine goes to do a getDataByRow() for the row, the dojo.html.getAttribute(row, "value") call returns null.

This worked fine in 0.4.1

Attachments (2)

test.html.gz (643 bytes) - added by dojo@… 13 years ago.
Error test case for #2593
test.html (1.3 KB) - added by dojo@… 13 years ago.
Uncompressed version

Download all attachments as: .zip

Change History (6)

Changed 13 years ago by dojo@…

Attachment: test.html.gz added

Error test case for #2593

comment:1 Changed 13 years ago by James Burke

dojo@…, can you reattach the test case, but not as a gzip file? I cannot seem to pull down the gzip file.

Changed 13 years ago by dojo@…

Attachment: test.html added

Uncompressed version

comment:2 Changed 13 years ago by dojo@…

Add uncompressed version of attachment.

comment:3 Changed 13 years ago by Tom Trenka

Resolution: invalid
Status: newclosed

This is not a regression or a bug; your example never designated one of the fields in your data as the value or key field (default is "Id"), nor did you point that key field to one of your existing properties.

Each object in your data should have a unique key, something that can be used as a hashtable key. The default for the table is "Id".

This also should not have worked in 0.4.1.

comment:4 Changed 13 years ago by dojo@…

D'oh! Thanks.

Though the failure mode seems less than graceful or informative.

Note: See TracTickets for help on using tickets.