Is it bad to use runat="server" on <tr>?

Question

I'm supporting an application that uses runat="server" all over the place to show/hide table rows.

For example, in places where there are dependent DropDownLists, the row with the child ddl will be hidden until a value us chosen in the parent ddl.

Is that a bad practice? Is there a better way to do this?

Answer 1

I use runat="server" anytime I need it. So I think you can use it too. :-)

Answer 2

I think that's absolutely terrible practice. First of all you do not need to make the trip to the server to hide and show controls, unless you need new data.

Second, any decent javascript framework will allow you to hide show controls based on the control's id, class name, or whatever css selector. Moreover using a javascript post/get to a generic handler will give you the data that you need without the postback.

I'd suggest using JQuery, or some other alternative.

Answer 3

It depends on how much you care about performance. Anything that is marked with runat="server" goes through more processing than just client side tags.

Personally, I've used them before. Especially in the situation where a table cell or table row is relying on data from the server. You can use Javascript or JQuery with a hidden field but you still have to hit the server for the hidden field, so it doesn't buy much.