Want to build your own 24/7 FAQ knowledge base?
LibraryH3lp subscriptions
include unlimited independent internal or public-facing
knowledge bases.
9592 views | Last updated on Nov 04, 2024 proactive Ebsco integrations
If you have a chat snippet embedded within the sidebar you'll probably find that if you enable proactive chat invitations on that snippet, the proactive chat invitations are restricted to the chat widget in the sidebar and won't freely float over the rest of the page. This is because Ebsco sandboxes the chat snippet inside an iframe. The workaround is to add a second, "proactive-only" chat snippet to Ebsco which is not placed within the sidebar but instead you'll add the chat code snippet as part of the footer or your EDS customizations.
LibraryH3lp proactive chat invitations use a common, 3rd party library (jQueryUI) to present the invitation dialogs to patrons. Ebsco has it's own styling for the dialogs from this 3rd party library which override any theme you may choose for your proactive chat invitation. If you are adding a proactive chat invitation, you'll probably want to add the following bit of custom styling to the "Offline Appearance" area of your chat snippet (for pop-up and follow-me chat boxes) or directly to Ebsco (for embedded chat boxes):
<style type="text/css"> .ui-dialog { z-index: 1000; } .ui-dialog .ui-widget-header button.ui-button .ui-icon-closethick { margin: -8px; } .ui-dialog .ui-widget-header { padding: 20px 0 0 15px; } .ui-dialog .ui-widget-header > span:first-child { font-size: 1.2em; } .ui-dialog .ui-dialog-content p { font-size: 1.2em; margin-top: 20px; } .ui-dialog .ui-resizable-se { display: none !important; } </style>
The proactive chat invitation uses a common 3rd-party library called jQueryUI to make the chat invitation dialog, and Ebsco defines a function called window.preventDefault, which overrides the jQueryUI code that handles placement.
<script type="application/javascript"> window.preventDefault = undefined; </script>
FAQ URL: