Summary: | Focus for cursor is in cataloging search input box on additem.pl | ||
---|---|---|---|
Product: | Koha | Reporter: | Barbara Johnson <barbara.johnson> |
Component: | Cataloging | Assignee: | Bugs List <koha-bugs> |
Status: | NEW --- | QA Contact: | Testopia <testopia> |
Severity: | enhancement | ||
Priority: | P5 - low | CC: | m.de.rooy |
Version: | Main | Keywords: | regression |
Hardware: | All | ||
OS: | All | ||
Change sponsored?: | --- | Patch complexity: | --- |
Documentation contact: | Documentation submission: | ||
Text to go in the release notes: | Version(s) released in: | ||
Circulation function: | |||
Bug Depends on: | |||
Bug Blocks: | 31411 |
Description
Barbara Johnson
2020-10-19 16:53:32 UTC
I disagree about this one. The cursor focus on addbooks.pl makes sense because performing a search is one of only two likely actions the user can take--it's either that or create a new record. When the user arrives at additem.pl they might be adding a new item, editing an existing one, or be on to the next task. Only in the last case is the focus on the search field helpful. It was previously considered a bug that focus was on the search field: Bug 11905 I see your point. We use some jQuery to set the focus of the cursor which provides efficiency for our workflow but I can see how that might not apply to every library. It looks like the cursor is (back) in the cataloging search form now? I tested: * From start page open cataloguing module * Cursor is on top in the 'Cataloguing search' Not sure if this makes this resolved or opens a new bug... (In reply to Katrin Fischer from comment #4) > It looks like the cursor is (back) in the cataloging search form now? > > I tested: > * From start page open cataloguing module > * Cursor is on top in the 'Cataloguing search' > > Not sure if this makes this resolved or opens a new bug... Definitely back in in the top search. |