]> git.koha-community.org Git - koha.git/commit
Bug 11369: (follow-up) Correct usage of me.searchid in browser.js
authorFridolin Somers <fridolin.somers@biblibre.com>
Wed, 26 Feb 2014 16:03:13 +0000 (17:03 +0100)
committerFridolin Somers <fridolin.somers@biblibre.com>
Wed, 7 May 2014 16:33:15 +0000 (18:33 +0200)
commit7ee0085b2ea8a33f25d731a4239f93c7be244219
tree52ecd5066a163b58bf7c83e82aeecc89b77c5772
parente597446b9934e8216ccccf4a12cfe1657a959efd
Bug 11369: (follow-up) Correct usage of me.searchid in browser.js

In browser.js, at creation of browser, the searchid is transmited to
JS object into me.searchid.
To be consistant, me.searchid should always be use, never searchid alone.
In browseRecords function, setting searchid as parameter is useless
because it is defined in me.searchid.

Test with test plan of Bug 10404

Signed-off-by: Kyle M Hall <kyle@bywatersolutions.com>
Signed-off-by: Katrin Fischer <Katrin.Fischer.83@web.de>
Signed-off-by: Galen Charlton <gmc@esilibrary.com>
(cherry picked from commit 98edbf00cc10c908820eb1126a176ed12a04300d)
Signed-off-by: Fridolin Somers <fridolin.somers@biblibre.com>
koha-tmpl/intranet-tmpl/js/browser.js