This error message is quite odd and we have not received such reports so far.

We are willing to advise you further but in order to do so we would need you to elaborate on your specific scenario and possibly give us a step-by-step guide that we can use to observe the problematic behavior.

Why don't you try to duplicate the problem?  I've already given you the exact issue and I'm sure you are very capable of creating a quick sample to verify this issue.

I have forwarded this issue to WebCombo development team. A work item, #702, has been submitted regarding this minor glitch.

I’ll keep you updated with any new I heard from the team regarding this work item.

Thank you for your valuable feedback.

Thank you, but I would not consider this a "minor" glitch as it creates a big headache for the workaround we had to create.

I have forwarded this issue to WebCombo development team. A work item, #702, has been submitted regarding this minor glitch. ...

Yudi,

Will you update threads when an item has been fixed and is released in a build/patch?  Basically, how will I know when this (or any other) fix has been implemented?  Thank you.

I have checked the status of work item #702 and find that the work item has not been fixed yet.

You may try to replace controlId parameter with the id of your WebCombo as a workaround of this issue.

function WebCombo1_OnKeyDown(controlId, keyValue) {
    //ISGetObject(controlId) is equals to
    //ISGetObject("WebCombo1")
    //Note: WebCombo1 is the ID of the corresponding WebCombo
    var WebCombo1 = ISGetObject(controlId);
    var WebCombo1 = ISGetObject("WebCombo1");

    return true;
}

I’ll keep you updated as soon as I heard news from the team regarding status of this work item.

Hi Yudi,

Thanks for checking.  We have a workaround for now but would really like this fixed soon.  Also, we do not hard-code control names into any of our client-side code because we can't since we don't know what control triggers this handler.  It's easy to do that when you have a simple page, but we work with a very complicated application with many controls.

I hope we can get a fix soon though.  Thanks again.

Thank you very much for your patience and understanding.

I’ll inform you at once if I heard any news regarding this work item. Meanwhile, is it possible for your project to use the old version of WebCombo 4 assembly?

Hi Yudi,

No we can't go back, but thankfully we have a workaround which works right now.  My only concern in the workaround implmentation is that it can break if the architecture changes in a future release and that's why it would be nice to have a fix so we don't have to rely on infused code for a workaround.  Thanks a lot.

Yudi,

Has this been fixed in 2011 R1?

The “passes null for controlId and some random value for keyValue” has been fixed in 2011 R1.

To add a client-side event, I recommend you to add it in OnInit or OnLoad event instead of in OnPreRender.

Glad to hear.  Thanks Yudi.