Novelist delays can cause Staff Client issues
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Evergreen |
Fix Released
|
Medium
|
Unassigned | ||
2.10 |
Fix Released
|
Medium
|
Unassigned | ||
2.9 |
Fix Released
|
Medium
|
Unassigned |
Bug Description
When Novelist is set to load in the staff client and gets stuck on something (in our case, loading On the Shelf information) it can prevent the staff client from loading/updating things like the record information screens. Eventually the information will load or time out and the staff client will catch up, but this can take several minutes of waiting.
My proposed solution is to wrap the Novelist call in a setTimeout with a delay of 100ms. The staff client should hopefully be done initialization by then but patrons are probably still reacting to the page having loaded and thus won't have scrolled down to where Novelist will then be populating.
Here is my branch:
While I personally see this as fixing a bug I am not sure if others will.
Changed in evergreen: | |
status: | Fix Committed → Fix Released |
FWIW, I lean towards classifying this as a bug, or at least suitable for backporting to maintenance branches.