Man, I love the .net framework. Each release see me writing less and less of the boring stuff, allowing me to concentrate on the more exciting things in development. However, as each release passes by, I'm always left with the thought : "How did we cope before this release??!?!!"
It struck home good and proper today.
A Web Agency strives for perfection in design, perfection in usablity, perfection in accessability, perfection.*. W3C validation is one of the many tests we put our sites under, and it gives some really good feedback on your mark-up ; which attribute have you forgetten to add? Which elements fit inside which elements?
We know, by now, that <span> can contain very few HTML elements. This has been the case for all eternity. So, why oh why, does setting
RepeatLayout.Flow on a DataList make anyone @ Microsoft think it's going to get away with wrapping each template up in a <span>
when it can contain so few elements?
Thats the problem i was having today. Alexey had coded me up some excellent HeaderTemplate, FooterTemplate and ItemTemplate for one of our ZoomSpace applications. The raw HTML looked brilliant, the HTML was W3C compliant, everyone was happy, especially me.
Along comes DataList to ruin my day by injecting it's dodgy, non-compliant, and downright short-sighted markup into my ResponseStream.
DataList was prevalent in .net 2.0. A good, lightweight, databound control which you could use to edit items, delete stuff, add new items, the lot. I know the purer way would be to use the Repeater, but i needed the data-driven code. I could have used ListView, but this a .net 2.0 application so that's out too.
We've been using ListView for a while. It's pure mark-up, no additions and no weirdness. How easy I forget how different things were!!
Be the first to rate this post
- Currently 0/5 Stars.
- 1
- 2
- 3
- 4
- 5