Hi Daniele,

I think you can choose whether it will be stored in PageCache (browser), Session (browser), or FileServer (IIS Server). You pick one of them as you cache storage by using DataCacheStorage property. WebCombo will load the data at first load then it will load the data from its cache while postback. Hope this helps.

Regards,
Bernard

Hi BJay,

I've analyzed your problem. If you want to open new window when you click WebNotification to your desired page you can used this code:

function Button1_onclick() {
    var WebNotify = ISGetObject("WebNotification1");
    var myNotification = WebNotify;
    myNotification.ContentText = "This notification is sent from button click. Check it out!";
    myNotification.CaptionText = "NotifyWindowURL does not work";
    myNotification.NotifyWindowClickable = true;
    myNotification.NotifyWindowURL = "http://www.intersoftpt.com/";
    myNotification.NotifyURL = "http://www.intersoftpt.com/";
    WebNotify.Notify(myNotification);
}

You can put NotifyURL attribute inside your WebNotification in client-side. It works fine here if I used this code. You can try to implement this code in your local end. And please tell me if this matter still happen on your local end. Hope this helps.

Regards,
Bernard

Hi Eric,

Maybe for this scenario we can trigger click action on WebPaneManager's grip by using this code on server-side:

ClientScript.RegisterStartupScript(this.GetType(), "msg", "<script language='javascript'>window.setTimeout(function (){document.getElementById('ws_WebPaneManager1_Pane0_V_grip').click();}, 10);</script>");

ws_WebPaneManager1_Pane0_V_grip is Id that you can get from grip's image from WebPaneManager. The collapse progress start when image inside splitter between two have been pressed. So we can trigger the javascript from client-side in server side by using that code. But this just a workaround regarding your problem. We currently enhance WebPaneManager to support HTML5 and it is better if we have elegant method from server-side regarding this matter. If you want, I'll make this as feature request to our developer team. Hope this helps.

Regards,
Bernard

Hi Pierre,

I can't replicate this problem using WebGrid 8. This problem might be had been solved by our developer team. You can try to use your code in our WebGrid 8. Hope this helps.

Regards,
Bernard