Hello Robert,

Please create another thread for the next time. We were talking a different product now. However, Xu GuoChun has resolved his issue in here. At does not problem if you want to use your own filter, but it would be better, if you handled all of them in InitializeDataSource. In order to handle it manually, you would need to turn off AllowAutoQueryHandler. In this way, you can load or filter with request which is called LoadOnDemand.

Regards,
Handy

Hello,

I have seen your sample a while ago. If you were talking about gap issue with bottom <div> in 1.png, as I told you, this is not WebGrid fault. Please see my response at July 27, 2011 11:48 PM. I have given the prove there. It is because different behavior rendering in XHTML, not because WebGrid.
I already explained by using 3 diffents div looks like your structure page. The gap is happened because different rendering in <p> tag. You can also see Karl's post at August 30, 2011 7:05 PM.

As I said before, If you placed only WebGrid in XHTML, you might not find any issue, except for charting because it has not support XHTML yet.
But if you placed WebGrid with others element and the layout is mess up, you would need to customize your style. I have suggested some workarounds for style before. This happens because you could not expect all other elements to work perfectly in XHTML without any customization.

You can try to have others element without WebGrid and you will notice that you needs to set style.
The style can be different with HTML doctype.

I thought you already understand this last time, that's why I agreed to check the remaining issue about WebGrid is not resized well when you resized the browser.

Please let me know if there is something that I am missing.

Regards,
Handy

Hello Neena,

It seems you wrongly placed in product category. It should WebGrid, right? For the next release, WebGrid will improve security by eliminating  XSS exploit  through the use of JSON as the control data format. You can see our roadmap in previous thread for further information.

Regards,
Handy

Hello,

In clientside, you can select a row by the key value. Perhaps, this can be used for your scenario.

function SelectRow()
{     var grid = ISGetObject("WebGrid1");     
      var row = grid.RootTable.GetRowByKeyValue("VINET"); //get WebGridRow object by key value.      
      row.Select(); // select this row for focus
}

Hi,

Perhaps, you misunderstood what I said before. Forgive me for not explaining in detail.
I could replicate your issue in here. However, this is not a bug.
AlwaysShowAllRowsOnDropDown is not designed if you have many list in your WebCombo rows. It only supports if you have some list rows and want to show all together in the list when set the text/value. 

In your scenario, this is not recommended to use the properties because it would be failed.
Morelikely, it would best if you used LoadOnDemand scenario. If you check carefully, in LoadOnDemand, AlwaysShowAllRowsOnDropDown would be automatically ignnored even though this property is set.
This is the correct behaviour. You can also see my attachment about how to implement LoadOnDemand via behind code.

But if you still want to show all the rows via the property, it seems you need to request this feature.

Regards,
Handy