Comment 3 for bug 1538675
Revision history for this message
| Josh Stompro (u-launchpad-stompro-org) wrote | #3 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
bbfa235
(Get the code!)
EG 3.3.4
Another effect of this issue that we have noticed is that when staff open bib results in new tabs, and then view those tabs and decide to place a hold, the hold gets placed without a customers notifications preferences being used.
This was a long awaited workflow that they were looking forward to with the web staff client, since many staff are used to opening links from search results in new tabs in general in a web browser (for google searches for example). Then looking at each tab, deciding if the title/info is what they are looking for, and placing a hold, or closing the tab.
It seems that the staff.js file is missing some prerequisites when the place hold page is loaded in in a new tab.
Josh