web client: grid columns aren't displaying in order specified in tt2 files
Bug #1731278 reported by
Kathy Lussier
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Evergreen |
Won't Fix
|
Low
|
Unassigned |
Bug Description
When manually adding specific columns to display in a web client grid, the columns should display in the order in which they were entered. However, this isn't happening. As an example, in t_checkin_
Alert Msg
Balance Owed
Barcode
Bill #
Checkin Date
Family Name
Finish
Location
Route To
Start
Title
Circulation Modifier
Circulation Library
However, when retrieving the checkin interface, these fields display in the following order:
Alert Msg
Start
Route To
Title
Location
Checkin Date
Bill #
Family Name
Finish
Circulation Modifier
Barcode
Balance Owed
Circulation Library
Changed in evergreen: | |
importance: | Undecided → Low |
Changed in evergreen: | |
milestone: | 3.1-rc → 3.1.1 |
Changed in evergreen: | |
milestone: | 3.1.1 → 3.1.2 |
Changed in evergreen: | |
milestone: | 3.1.2 → 3.1.3 |
Changed in evergreen: | |
milestone: | 3.1.3 → 3.1.4 |
Changed in evergreen: | |
milestone: | 3.1.4 → 3.1.5 |
Changed in evergreen: | |
milestone: | 3.1.5 → 3.1.6 |
Changed in evergreen: | |
milestone: | 3.1.6 → 3.2.1 |
Changed in evergreen: | |
milestone: | 3.2.1 → 3.2.2 |
Changed in evergreen: | |
milestone: | 3.2.2 → 3.2.3 |
Changed in evergreen: | |
milestone: | 3.2.3 → 3.3-beta1 |
status: | Confirmed → New |
Changed in evergreen: | |
milestone: | 3.3-beta1 → 3.3-rc |
Changed in evergreen: | |
milestone: | 3.3-rc → 3.3.1 |
Changed in evergreen: | |
milestone: | 3.3.1 → 3.3.2 |
Changed in evergreen: | |
milestone: | 3.3.2 → 3.3.3 |
Changed in evergreen: | |
milestone: | 3.3.3 → 3.3.4 |
no longer affects: | evergreen/3.0 |
Changed in evergreen: | |
milestone: | 3.3.4 → 3.3.5 |
Changed in evergreen: | |
milestone: | 3.3.5 → 3.4.2 |
Changed in evergreen: | |
milestone: | 3.4.2 → 3.4.3 |
Changed in evergreen: | |
milestone: | 3.4.3 → 3.4.4 |
Changed in evergreen: | |
milestone: | 3.4.4 → 3.5.1 |
Changed in evergreen: | |
milestone: | 3.5.1 → 3.5.2 |
Changed in evergreen: | |
milestone: | 3.5.2 → 3.6.1 |
Changed in evergreen: | |
milestone: | 3.6.1 → 3.6.2 |
Changed in evergreen: | |
milestone: | 3.6.2 → 3.6.3 |
tags: | removed: webstaffclient |
Changed in evergreen: | |
milestone: | 3.6.3 → 3.6.4 |
Changed in evergreen: | |
milestone: | 3.6.4 → 3.7.2 |
Changed in evergreen: | |
milestone: | 3.7.2 → 3.7.3 |
no longer affects: | evergreen/3.6 |
Changed in evergreen: | |
milestone: | 3.7.3 → none |
Changed in evergreen: | |
milestone: | none → 3.9.1 |
status: | New → Confirmed |
no longer affects: | evergreen/3.1 |
no longer affects: | evergreen/3.2 |
no longer affects: | evergreen/3.3 |
no longer affects: | evergreen/3.4 |
no longer affects: | evergreen/3.5 |
Changed in evergreen: | |
milestone: | 3.9.1 → 3.9.2 |
Changed in evergreen: | |
milestone: | 3.9.2 → none |
To post a comment you must log in.
After deleting my browser grid settings (via eg/staff/ admin/workstati on/stored_ prefs), on a 3.1-beta server, I'm seeing something similar to this bug on Chrome (though not the same order of columns that Kathy described). But in Firefox I see exactly the expected columns in expected order. Some research revealed that JavaScript sort in Firefox is stable, while it is unstable in Chrome. This means our current column-sorting code relies on browsers to maintain sort order of "equal" columns during the sort process, but some browsers don't play along. The solution is for us to explicitly track and maintain the column order that we want. Dan Wells has a branch for this, coming soon.