vincent pollard wrote: > i have a page that looks a bit like this: > > > <hr /> > > <asp:Label ID="Label1" runat="server" Font-Bold="True" Text="Name"></asp: > Label> > > <asp:TextBox ID="tb" runat="server" Width="200px"></asp:TextBox> > > <asp:Label ID="Label2" runat="server" Font-Bold="True" Text="No."></asp: > Label> > > <asp:TextBox ID="tb2" runat="server" Width="200px"></asp:TextBox> > > <br /><br /> > > <asp:Label ID="Label3" runat="server" Font-Bold="True" Text="Name 2"></asp: > Label> > > > > <asp:TextBox ID="tb3" runat="server" Width="200px"></asp:TextBox> > > > > <asp:Label ID="Label4" runat="server" Font-Bold="True" Text="No. 2"></asp: > Label> > > > > <asp:TextBox ID="tb4" runat="server" Width="200px"></asp:TextBox> > > so, i have no DIV that i could add padding or margin to as i normally would. > > should i add an empty p tag? an empty div? what would you guys recommend? > > > .NET Server Controls - guaranteed to make the lives of all front end coders more interesting.
.NET server controls tend to generate a lot of HTML code that would definitely not be our first choice. Lots of tables, lots of spans. In some controls, there is a "Layout" property which allows you to select "table" or "flow", with "flow" wrapping things in spans. But other than that, you have to view the generated source to see how it renders. Someone who knows the ins and outs of programming could change .NET's behavior to output different tags, but until then, you have to work with what it gives you. Using "content buckets", i.e. ID'd divs to delimit specific areas of the page and assign properties is a good way to go. ______________________________________________________________________ css-discuss [EMAIL PROTECTED] http://www.css-discuss.org/mailman/listinfo/css-d List wiki/FAQ -- http://css-discuss.incutio.com/ List policies -- http://css-discuss.org/policies.html Supported by evolt.org -- http://www.evolt.org/help_support_evolt/
