[ List Archives Home ] [ Thread index for 2008 ]
[ Date index for 2008 ]
[ Author index for 2008 ]
[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
John,
I would be interested in what you find out about Meebo and your OPAC search page. I ran into a similar problem testing Hab.la (
http://www.hab.la/). Habla is similar to Meebo in that it lets visitors chat with you, however the chat box "floats" from page to page (as long as the script is included in that page) and carries the conversation along with it. I ran a quick test on our OPAC but every time I hit return to send a message it submitted a search in the OPAC. We put the Habla experiment on hold after we found they limit the number of simultaneous users to five; however, for future reference I would like to hear if you found a way around it.
Thanks,
Nathan Landis
Library Information Systems Specialist
Greenwood Library ~ Longwood University
Redford and Race Street, Farmville, Virginia 23909
Tel: 434.395.2438 fax: 434.395.2453
>Date: Wed, 09 Jan 2008 15:35:10 -0800
>From: John Wenzler <jwenzler at sfsu dot edu>
>Subject: [IUG] Meebo and WebPAC in Firefox
>To: innopac at innopacusers dot org
>Message-ID: <OFAAEB12B9 dot 6DC3B965-ON882573CB dot 00819069 at sfsu dot edu>
>Content-Type: text/plain; charset="us-ascii"; format=flowed
>
>Hello,
>
>I have a question that the JavaScript experts out there may be able to answer. Our library is using meebo >(www.meebo.com) for IM reference, and we have been experimenting with adding the meebo widget to WebPAC so that >students can ask questions from a search page.
>
>For testing I put a widget on our opacmenu page in staging:
>
http://opac.sfsu.edu:2082/search
>
>It works fine in IE, but I am having a problem with FireFox on PCs.
>The problem is that whenever you type an IM message and hit the return key in FireFox, a search query gets sent >to WebPAC, you get a search results page, and you lose your IM session.
>
>In looking at the JavaScript on the WebPAC search pages, we think that we have identified the source of the >problem, but we don't know how to fix it. Our search pages have the following script, which gets added with the ><!--{submit}--> token:
>
>
><script language="javascript">
>function iiiDoSubmit_1() {
> var name = "iiiFormHandle_1";
> if (document.getElementById)
> obj = document.getElementById(name);
> else if (document.all)
> obj = document.all[name];
> else if (document.layers)
> obj = document.layers[name];
> obj.form.submit();
>}
>if (document.layers)
> document.captureEvents(Event.KEYDOWN);
>document.onkeydown =
> function (evt) {
> var keyCode = evt ? (evt.which ? evt.which : evt.keyCode) : event.keyCode;
> if (keyCode == 13)
> iiiDoSubmit_1(); };
></script>
>
>We think that "if (keyCode == 13) iiiDoSubmit_1(); };" is submitting a search whenever you hit the "return" key >anywhere on the page.
>
>Any suggestions for getting around this?
>
>Thank you,
>John Wenzler