Details
-
Type:
Bug
-
Status:
Closed
-
Priority:
Minor
-
Resolution: Fixed
-
Affects Version/s: 1.0 RC1
-
Fix Version/s: 1.0 RC2
-
Component/s: Paging/Sorting
-
Labels:None
Description
====
imported from sf tracker
id 999622
submitted by spyteam - spyteam
http://sourceforge.net/tracker/index.php?func=detail&group_id=73068&atid=536613&aid=999622
====
Found a bug where a user, who has clicked a column
header twice to get a descending sort, will not be
returned to 'page 1' if the list is again sorted ascending.
Picture a three-column table for this example with
sort="list" attribute set on the table tag.
1. User clicks column 3 header to sort ascending. User
returned to page 1.
2. User clicks column 3 header to sort descending. User
returned to page 1.
3. User navigates to page other than page 1.
4. User clicks column 3 header to sort ascending. User
NOT returned to page 1, rather, user stays on current
page number.
It just feels like the url links being created for the
column headers is not setting page=1 but is instead
using page=x where x is the current user page. But this
only seems to happen going from a descending sort back
to ascending sort on the same column.
Found in 1.0-rc1.
imported from sf tracker
id 999622
submitted by spyteam - spyteam
http://sourceforge.net/tracker/index.php?func=detail&group_id=73068&atid=536613&aid=999622
====
Found a bug where a user, who has clicked a column
header twice to get a descending sort, will not be
returned to 'page 1' if the list is again sorted ascending.
Picture a three-column table for this example with
sort="list" attribute set on the table tag.
1. User clicks column 3 header to sort ascending. User
returned to page 1.
2. User clicks column 3 header to sort descending. User
returned to page 1.
3. User navigates to page other than page 1.
4. User clicks column 3 header to sort ascending. User
NOT returned to page 1, rather, user stays on current
page number.
It just feels like the url links being created for the
column headers is not setting page=1 but is instead
using page=x where x is the current user page. But this
only seems to happen going from a descending sort back
to ascending sort on the same column.
Found in 1.0-rc1.
