Bug 6569 - Split menu button not working with "search to hold" operations
Summary: Split menu button not working with "search to hold" operations
Status: CLOSED WORKSFORME
Alias: None
Product: Koha
Classification: Unclassified
Component: Circulation (show other bugs)
Version: master
Hardware: All All
: PATCH-Sent (DO NOT USE) normal (vote)
Assignee: Owen Leonard
QA Contact: Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-07-08 17:06 UTC by Owen Leonard
Modified: 2012-10-26 00:41 UTC (History)
2 users (show)

See Also:
Change sponsored?: ---
Patch complexity: ---
Documentation contact:
Documentation submission:
Text to go in the release notes:
Version(s) released in:


Attachments
Revised fix (2.04 KB, patch)
2011-07-08 17:09 UTC, Owen Leonard
Details | Diff | Splinter Review

Note You need to log in before you can comment on or make changes to this bug.
Description Owen Leonard 2011-07-08 17:06:22 UTC
When you use the "Search to hold" function the interface offers a "split" menu button in two places: On the search results screen and the item detail screen. In both cases the button is not working properly. When you click the down-arrow to expand the menu the form is submitting right away. The form shouldn't submit unless you choose one of the options in the menu.
Comment 1 Owen Leonard 2011-07-08 17:09:52 UTC
Created attachment 4609 [details] [review]
Revised fix

Before this patch, clicking the down-arrow on the "Place hold"
split menu button would submit the form right away with the
default action. After applying the patch the form should not
submit until you choose one of the two menu items ("Place hold"
or "Place hold for [Patron]").
Comment 2 Nicole C. Engard 2011-07-09 12:16:45 UTC
I talked with Owen about this on IRC and I don't have a problem. It seems to be something specific on his machine.  Owen, should be close this?
Comment 3 Owen Leonard 2011-07-11 16:48:32 UTC
I can reproduce this bug across multiple browsers but only with this particular installation. I can't imagine what the difference is, but if it's just me then this bug is invalid.