F4 (Search for Patrons) Results in Multiple Popup Errors if Interrupted

Bug #1300789 reported by Robert J Jackson on 2014-04-01
16
This bug affects 3 people
Affects Status Importance Assigned to Milestone
Evergreen
Undecided
Unassigned

Bug Description

Evergreen 2.5.2
OpenSRF 2.2.X
PostgreSQL 9.1.11
Ubuntu 12.04

Within 2.5.2 staff client pressing F4 followed by another function key short cut will result in a series of 4 popups that must be cleared before the most recently requested function is displayed. This is repeatable. When circ desks are using short cuts and accidentally hit the wrong short cut they will use the desired shortcut prior to the painting of the Patron Search screen. This results in a series of 4 pop ups that must be individually cleared before the desired screen is displayed and circ activities can continue.

[JavaScript Application]

TypeError: $("commonStrings") is null

TypeError: $("patronStrings").getString is not a function

TypeError: $("commonStrings").getFormattedString is not a function

TypeError: $("commonStrings") is null

Erica Rohlfs (erohlfs) wrote :

As Michele Morgan pointed out in IRC (http://irc.evergreen-ils.org/evergreen/2014-04-04), this error occurs if you hold the Function key too long.

Changed in evergreen:
status: New → Confirmed
Erica Rohlfs (erohlfs) wrote :

As a follow up, I can produce single instances of these pop up errors when holding function keys too long. However, to reproduce the four error windows described above, I had to hold down the F4 key while attempting to select another F key. I also reproduced this error by holding down the F4 key.

Michael Peters (mrpeters) wrote :

These errors appear because the javascript file(s) the patron search form references likely aren't fully loaded by the time you quickly hit F3 to switch to catalog search, after realizing your mistake.

I have a sneaking suspicion that a "long press" prompts a refresh (appears to refresh the F3 page) which is why the symptoms are the same on a long press. The javascript hasn't loaded/grabbed all of the strings for the form before you "sever" the connection to perform a refresh.

Maybe the solution is to open new tabs for each unique "F-key", or maybe even a new tab no matter what F-key you press.

Michael Peters (mrpeters) wrote :

FYI -- this bug exists in 2.3.5 so it likely goes much further back than 2.5.2 or even 2.4.

Jane Sandberg (sandbej) on 2018-12-20
tags: added: fixedinwebby
Andrea Neiman (aneiman) wrote :

XUL client issue -- setting won't fix

Changed in evergreen:
status: Confirmed → Won't Fix
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Related questions