Check out this mark-up

it's a bit of .net whacko

[RossWal]

[3]
<h1> <span id="GRDVProductDetails_ctl02_LblProductTitle">Telephone Widgets:</span>
      <span id="GRDVProductDetails_ctl02_lblSubTitle"><BR />Why you need them</span>&nbsp;</h1>
[/3]

That's the HTML - beyond being ugly, is it valid markup? Can spans be embedded in an H1?

[tedster]

Yes, spans can be embedded in an H1 tag. Gotta love that .NET stuff, though. i see more of it than I want to these days. And it really is something the developer can and should control.

We've got some pretty good threads in our .NET forum about taming the beast. Here's a good one:

[webmasterworld.com...]

[RossWal]

Thanks Tedster. I've seen that thread. Been away from the WebmasterWorld MS area for a while - time to make my way back there I suppose.

[tedster]

When it comes to .NET burdens, how about some of those untamed __VIEWSTATE ids? One client brought me a site where the name of the id alone was a single character string over 30kb long.

[dbdev]

does it look the same in ff, ie?

does your analytics show the majority of visitors on cable versus dial-up?

... then who cares what .net calls/renders an id.

/point

[tedster]

Not caring about file size or bandwidth can be a kind of self-fulfilling prophecy. If your page's file size is very large because of poor choices in .NET (or any other area), you are not likely to do well with the audience that has slower connections. It's not worth obesessing about, but it is worth conscious attention and responsibility. If you only go with default choices, then that habit pattern works against the success of your website.