OPAC Search-button consistency is lacking

Bug #1212371 reported by Pasi Kallinen
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Evergreen
Incomplete
Low
Unassigned

Bug Description

*Eg master

The "Search" button in the OPAC is not in consistent location. In Advanced and Expert searches, the button is in the left side of the screen. In Numeric search, the button is aligned right in the table cell.

In Browse the Catalog -page, the "Go" button is a standard HTML input button, not the green EG "button".

Tags: opac
Revision history for this message
Ben Shum (bshum) wrote :

Checking on this bug since things have changed in master since it was originally reported.

Changed in evergreen:
status: New → Incomplete
Revision history for this message
Eva Cerninakova (ece) wrote :

1. The "inconsistency" depends on the point of view.

E.G.:
- All advanced search interfaces are consistent having search field in more than one line and submit button placed under search fields.
- But if we prefer another point of view, it would be more consistent, if only interfaces with option to add search row, would have more than one lines and those without option to add the search row would be placed on one line only.
- It is consistent that:
In cases, when the search query fields are placed on one line, the button is on the right side and in cases (The Basic Search and the Browse the catalog interfaces)
In cases, when the search query fields are placed in more than one line, the search buttons are placed under the search fields aligned to the left side of the screen (The Advanced Search, The Numeric Search and the Expert Search).

However, it is true, that, the way, how buttons are placed on lines and what type of HTML element is used, vary in various search interfaces.
- Basic search: the "div" elements are used for search fields and buttons, all placed one line
- Browse the Catalog: the "div" elements are used for search fields and the submit button, all placed one line
- Numeric search: the "div" elements are used for search fields and the submit button. The search fields are placed on two lines, the submit button is placed under the search fields (3 lines total).
- Advanced search: the "div" element is used for the submit button. The submit button is placed under the search fields table (which make perfect sense to me in this interface due to its purpose)
- Expert search: the search field and the search button are placed within the HTML table, including the"Add Search Row" option. The search button is placed under the two rows of search fields, which make sens as there is an option to add search row and also the option to select the library on additional row.
- Browse the Catalog: the "div" elements are used for the search fields and the submit button, all placed on one line.

2. In the "Browse the Catalog" interface is now the Evergreen style "Browse" button, not the standard HTML input button (the state in Evergreen 3.2.0)

Revision history for this message
Terran McCanna (tmccanna) wrote :

Noting that the buttons are consistent in the Bootstrap OPAC.

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

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.