this is the main problem with the asp webcontrols. they abstract the html,
and may change the rendered html based on browser agent or even a service
pack. also some of the controls render a span to which the class will be
attached, and not the underlying html element.
you can view source to see the html rendered, but be sure to do it with
several different browsers, and recheck after every sevice pack install.
if you are going to use css and want design control over your site, do not
use the webcontrols (repeaters ok), use the html controls instead.
also many of the controls can be replaced with simple html. your css
designers can probably do flyout and tree menus if you just render the menu
as a standard list: <ol><li>
note: warn you designers to not use id's for css selectors as these are not
reliable with asp.net controls
-- bruce (sqlwork.com)
"Mike Gleason jr Couturier" wrote:
Hi,
Our development team consist of course of programmers and those who do CSS
integration.
I'm afraid our ppl who do CSS, are purist that only did HTML/CSS and they
don't know the HTML ouput equivalent of let's say a asp:ImageButton tag....
Is there any resources or books to help our team of CSS guys integrate .NET
controls?
Thanks!
