Hello,

I've tried your sample on my end. At first, I did replicate your issue in here.

I notice that this error only occurs if you use XHTML DocType.

If you change it to <!

The sample works fine.

Hope this helps. Thank you.

Regards,
-Martin-

Hi Marin,

I tried changing the doc type as  you suggested. It did not make the slightest difference.

Besides, isn't your company boasting support for xhtml?

Regards,

Rudy

Hello Rudy,

After further investigation, it seems that there is a bug in WebCallOut control. The XHTML DocType works fine when using IE8 browser. The error happens when we use IE9 browser.

I've reported this issue to the developer team, and they have fixed this issue.

I will run a test on the latest hotfix build before I send the nightly build to your Email.

I will let you know the result as soon as possible, and please check your inbox to get the latest hotfix build.

Thank you.

Regards,
-Martin-

Hi Martin,

I have received the nightly build. WebCallOut now works both using xhtml doctype and html doctype.

However it only works when I use the normal mouse rollover method. When I tried to use javascript to show the callOut, it didn't work. Because on my sample that I gave you there are both rollover and javascript show method on the same page, so you can try both there. The show method will only work once you have loaded the control using the rollover method, but if you try to click the button to show the callout the first time the page loads, the server side show method does not get trigerred, hence the content control is not loaded.

Am I missing something in the javascript to get the content control to load first? is this a separate function that needs to be activated manually?

Hello,

I got your point. However, I couldn't assume this issue as a bug yet in WebCallOut.

Now, the issue is being investigated further by the developer team.

I will let you know the result as soon as possible.

Thank you.

Regards,
-Martin-

Hello,

After deep investigation on the control, the developer team has been fixed some issues for this scenario.

In the sample you've provided, you were using Show() to display callout. You need to use ShowAutoDetect() instead.

Here is the code:

function showCallOut(callOutId)
{
   var callout = ISGetObject(callOutId);
   var el = document.getElementById("link1");
   callout.ShowAutoDetect(el, true);
   return false;
}

link1 is the id of the 1st word:

<a id="link1" href="#" onclick="showCallOut('DocumentCallOut')">Add Document</a>

Then, ShowAutoDetect(el, true) where el is the element that triggers callout to be shows, and 2nd parameter is used to determine whether you want to have latency before the callout shows or not.

Please check your inbox for the latest WebDesktop hotfix.

Thank you.

Regards,
-Martin-