Providing Tooltip Help Messages Dynamically Using Ajax Functionality

This is actually part of context sensitive help requirements in our web application project. We should be able to provide small informative messages for html components displaying them as tooltips in our web pages when user moves mouse over those components.
It is also in the requirements that continiously appearing tooltip message windows in those pages along the mouse movement shouldn’t be disturptive against user. Hence, we let the user determine the time of tooltip message appearence as pressing CTRL at the same time  moving mouse over components will enable tooltip message appearence.
We should further be able to change content of tooltip messages and add new tooltip messages for other components without any source code modification.
Our solution has two parts, one on the client side, employing javascript to fecth any available tooltip messages from serverside using Ajax functionality for currently focused html components (via CTRL + mouse over at this time) and displaying them with opening a DIV element, as tooltip message container, and positioning it near the bottom right corner of the related component.
On the server side there is a HelpServlet employed as Ajax service end point, returning tooltip messages according to given html component ids. Tooltip message solution is closely related with our other part of the context sensitive help mechanism as they both employ page help context ids together with component ids. The reason for that, we need unique tooltip message identifiers accross the whole web application in order to identify each component’s tooltip message. As a result we glue page help context id together with html component id and use it as key for component’s tooltip message, and ask HelpServlet with that key if there is any available tooltip message for the currently focused component.
Tooltip messages on the server side are kept in a message properties file and loaded at the startup time by HelpServlet.
Below is the client side javascript code:

var appContextPath  = '/webAppContext;
var helpServletPath = '/helpServlet';
var http;

function getPageHelpContextID() {
    var pageCtxObj = document.getElementById('form1:pageCtxId');
    if(pageCtxObj) {
        return pageCtxObj.value;
    } else {
        return document.forms[0].id;

function showToolTip(evt) {
    evt = (evt)?evt:event;
    if(evt.ctrlKey) {
        var element = (evt.target)?evt.target:evt.srcElement;
        var toolTipElement = document.getElementById('toolTip');
        if(!toolTipElement) {
            toolTipElement = document.createElement('div');
            toolTipElement.id = 'toolTip';
            toolTipElement.style.backgroundColor= '#FFFF99';
        toolTipElement.style.left=findPosX(element) + element.offsetWidth + 10;
        toolTipElement.style.top=findPosY(element) + element.offsetHeight + 10;

function hideToolTip(evt) {
    evt = (evt)?evt:event;
    var element = (evt.target)?evt.target:evt.srcElement;
    var toolTipElement = document.getElementById('toolTip');

function findPosX(obj) {
    var curleft = 0;
    if (obj.offsetParent) {
        while (obj.offsetParent) {
            curleft += obj.offsetLeft
            obj = obj.offsetParent;
    else if (obj.x)
        curleft += obj.x;
    return curleft;

function findPosY(obj) {
    var curtop = 0;
    if (obj.offsetParent) {
        while (obj.offsetParent) {
            curtop += obj.offsetTop
            obj = obj.offsetParent;
    else if (obj.y)
        curtop += obj.y;
    return curtop;

function fetchAndDisplayToolTipMsg(msgId) {
    if(msgId) {
        http = createHttpRequestObject();
        sendHttpRequest(getPageHelpContextID() + ':' + msgId);

function createHttpRequestObject() {
    var ro;
       if(window.ActiveXObject) {
        ro = new ActiveXObject("Microsoft.XMLHTTP");
        ro = new XMLHttpRequest();
    return ro;

function sendHttpRequest(toolTipMsgId) {
    http.open('get', appContextPath + helpServletPath +'?toolTipMsgId=' + escape(toolTipMsgId),true);
    http.onreadystatechange = handleHttpResponse;

function handleHttpResponse() {
    if(http.readyState == 4) {
        var toolTipElement = document.getElementById('toolTip');
        var msg = http.responseText;
        if(msg && (msg.length > 0)) {
            toolTipElement.innerText = msg;

In order to activate above functionality we must add two event handlers in the BODY html element as follows:

<BODY onmouseover="showToolTip(event);" onmouseout="hideToolTip(event);" ...>

As you see above, main entry points are showToolTip() and hideToolTip() functions which are called on mouse over and mouse out events accordingly. In showToolTip(), we first create DIV element to display tooltip messages in it if there hasn’t been created before, then we fecth tooltip message for the current component from server side via XmlHttpRequest, and finally display it by placing any available tooltip message into the DIV element.

And here below is the excerpt from server side HelpServlet:

protected void doGet(HttpServletRequest request,HttpServletResponse response)
    throws ServletException, IOException {
    String toolTipMsgId = getToolTipMessageId(request);
    String msg = getToolTipMessage(toolTipMsgId);
    returnToolTipMessage(response, msg);
private void returnToolTipMessage(HttpServletResponse response, String msg) 
            throws IOException, UnsupportedEncodingException {
       if(StringUtils.isNotEmpty(msg)) {
        OutputStream out = response.getOutputStream();

private String getToolTipMessage(String toolTipMsgId) {
        String msg = toolTipMessageProperties.getProperty(toolTipMsgId);
        return msg;

private String getToolTipMessageId(HttpServletRequest request) {
        String toolTipMsgId = request.getParameter("toolTipMsgId");
        return toolTipMsgId;

As you see above, we get toolTipMsgId parameter value from request, and lookup corresponding tooltip message value in the properties file. Finally if there is an existing tooltip message for the component, we return that message as plain text through the servlet response.

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.