pre_cat_fields.xul buttons not visible when number of characters in code : name : description dropdown exceeds horizontal pixels of screen resolution

Bug #767507 reported by Michael Peters on 2011-04-20
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Evergreen
Status tracked in Master
2.0
Undecided
Unassigned
2.1
Undecided
Unassigned
2.2
Undecided
Unassigned
Master
Undecided
Michael Peters

Bug Description

Evergreen 2.0.4
OpenSRF 1.6.3

File impacted is pre_cat_fields.xul.

Discovered in Indiana when we applied a few short descriptions to the config.circ_modifier table. When on some 800x600 screens you're unable to perform "Check out" due to the fact that the width of the "Circ Modifier" dropdown is approximately 921px.

As you can see from the screenshot, it doesn't appear we're using an extremely long description for these, but perhaps another method for displaying the description (tooltip?) is in order.

Michael Peters (mrpeters) wrote :
Michael Peters (mrpeters) wrote :

Additonal screenshot, showing how this impacts an 800x600 monitor.

Michael Peters (mrpeters) wrote :

All,

Admittedly, this isn't the most elegant of solutions but it is a solution no less. This small patch adds an automatic overflow to the pre_cat_fields.xul so users can always resort to scrolling to access the rest of the window.

Perhaps we could consider this as a suitable fix in future versions. The 'ugly' scrolling only occurs when your window width is smaller than that of the descriptions in the Circ Modifier dropdown so while this may hurt a bit cosmetically, it does help functionality.

Hope others find this helpful if they run into this in the future.

Changed in evergreen:
status: New → In Progress
assignee: nobody → Michael Peters (mrpeters)
Mike Rylander (mrylander) wrote :

Committed as-is for now, trunk through 2.0, and leaving in-progress for later adjustment.

Is there currently a util function for extracting part of the circ mod (or any kind of param to the server call that returns it)? I would think that just the Name (or Code, not certain what the distinction is intended to be) would be used everywhere in the staff client, and the Description would be used in the OPAC (including in the staff client).

Jason Etheridge (phasefx) wrote :

In common.properties:
# %1$s = circ modifier code, %2$s = circ modifier name, %3$s = circ modifier description
staff.circ_modifier.display=%1$s : %2$s : %3$s

You can override this without editing common.properties directly by creating a common_custom.properties in the same directory and adding a line like so:
staff.circ_modifier.display=%1$s

Jason Stephenson (jstephenson) wrote :

Is any more work being done on this? I'd like to make it "Fix Committed."

Michael Peters (mrpeters) wrote :

No more work from my end.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers