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)
committerGalen Charlton <gmc@esilibrary.com>
Fri, 2 May 2014 23:18:55 +0000 (23:18 +0000)
commit98edbf00cc10c908820eb1126a176ed12a04300d
tree357d8d012e337dcbba0831495d05600a51ecfe6e
parent0cada7a323db7f9871b67a07e3343642543b64e0
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>
koha-tmpl/intranet-tmpl/js/browser.js