> > It is a matter of keeping your CSS code clean and maintainable. > > did I say "go write spaghetti"? The OP is not allowed to use IDs.
You did: Quote: in practice there is no real difference between id's and classes :EndQuote This is a wrong statement, to make it even remotely true it should say "Some browsers, in their forgiving manner don't distinguish between IDs and classes. Although they do recognise the different specificity they will allow you to use more than one ID with the same name in a document which is contradictory to the w3c guidelines" > Whether he writes clean code is between him and his maker. The point > is, just using classes will make no difference to the way the website > *functions*. See specificity, only using classes will get you into trouble overriding settings and makes it hard to use contextual selectors without mucking about with the HTML. IDs are there to identify unique sections and elements in the page, not store business logic variables. In forms, this intermingles, but you should still be allowed to identify and style the different page segments in CSS without resorting to unambiguous selectors. > > some developers still seem think the most important target is the > browser. > heh. who would think that? the end user perhaps? nah... The end user cares about _her_ browser, on _her_ environment and with _her_ settings. Who are we to anticipate all of these variables? If her experience throughout the site is of a consistent quality, all is fine. The only ones who will find differences between browsers are developers, the test team or misguided project owners. Back to the problem: Why don't you come up with a list of IDs that you and the development team agree on? Some .NET developers are prone to create horrible, bloated and invalid IDs. You can separate the structure layer out in .NET aswell, it just means you cannot use the design view of Visual Studio, and that means more work. However, you will be the one who has to answer when the final result looks bad or doesn't display properly, therefore it is a good plan to CYA by working closely with the development team and don't allow them to do things that are your job. this is off-topic though and better suited for the evolt list ______________________________________________________________________ css-discuss [EMAIL PROTECTED] http://www.css-discuss.org/mailman/listinfo/css-d List wiki/FAQ -- http://css-discuss.incutio.com/ Supported by evolt.org -- http://www.evolt.org/help_support_evolt/
