Intersoft Community - WebCombo - WebCombo in WebGrid

WebCombo in WebGrid

yudi — Tue, 20 Oct 2015 01:50:55 GMT

Glad to know that set ResultBoxWindowType to Normal resolve the reported problem.

Should you need further assistance or run into any problems regarding our controls, feel free to post it into our forum. We would be happy to assist you again.

WebCombo in WebGrid

rotithov — Mon, 19 Oct 2015 09:09:18 GMT

Great.....It woks...Thank Yudi

Thanks a lot...it helps me a lot.

WebCombo in WebGrid

yudi — Mon, 19 Oct 2015 03:07:15 GMT

I have seen another similar thread in here which mentions same problem and ASPNET-187 raised for this.

ASPNET-187 was reported by Dimitris B in the following thread: WebCombo integrated with WebGrid on IE11.

If you are experiencing this issue when create WebCombo programmatically, set the ResultBoxWindowType of WebCombo's LayoutSettings to Normal should resolve the problem.

I modified Programmatic.aspx sample of WebCombo by adding a line of code in combo_InitializeLayout LayoutEventHandler and find that the reported problem is no longer persist.

protected void combo_InitializeLayout(object sender, LayoutEventArgs e)
{
    // Setup Behavior
    WebCombo combo = (WebCombo)sender;
    combo.DataTextField = "ContactName";
    combo.DataValueField = "CustomerID";
    combo.LayoutSettings.ResultBoxWindowType = DisplayType.Normal;
}

Please let me know if you have different result.

WebCombo in WebGrid

rotithov — Fri, 16 Oct 2015 11:04:35 GMT

Please take it as question not a general discussion.

WebCombo in WebGrid

rotithov — Fri, 16 Oct 2015 07:21:03 GMT

We are using WebCombo in out project integrated with WebGrid(Versions used: WebCombo 6.0.7200.260, WebGrid 9.0.7200.4).Whenever a webcombo is clicked, we get the JS error. we are upgrading from IE9 to IE11

"Line: 1

Error: Object doesn't support property or method 'addRule'"

Page specifies HTML5 as its document type and the same is done with the rendering mode of each webcombo butstill problem persist.

I have seen another similar thread in here which mentions same problem and ASPNET-187 raised for this.

Any help appriciated.

Thanks and Regards,

Vaishnavi