I saw that on Scott Guthrie’s blog earlier. I’m still undecided on this… it’s basically taking a control that renders badly, then implementing new rendering behaviour using an adapter.

The adapter idea is nice if you want to leave the same interface and plug in different behaviour, but I’m not sure you’ll really want to do that. It’s using the framework that allows controls to render differently to different browsers, but just with a generic rule.

I can’t quite see when you would choose to implement an adapter, or when to subclass the control to change rendering behaviour. I guess if you already have a large site already using a particular control it would be more convenient, but both would end up with similar results.

I like having the option and will be playing with this stuff, but not quite convinced it’s necessary yet!

Thought you might be interested in this: http://www.asp.net/cssadapters/Default.aspx. I have to admit I haven’t tried it out yet, so I don’t know how good it actually is!