Usually you want to try and stay away from id specific css rules when you can help it. The obvious reason being that this starts to build up a lot of duplication in your css class definitions.
Don't forget that you can do things like this: <span class="someCssClass anotherCssClass" >content</span> The farther left the css definition goes the higher priority its rules will be given... On 10/18/06, Peter Beshai <[EMAIL PROTECTED]> wrote:
Is it seen as bad practice to have both jwcid and id (both equal to each other) in the html template? Currently I have only jwcid attributes, but this causes all my css that points to ids not to show up when I preview my page as just html. Is this seen as unnecessary duplication (ie having both jwcid and id since presumably id will be overwritten at runtime) or is this the way it should be done? Peter Beshai _________________________________________________________________ Voyez vos amis en faisant un appel vidèo dans Windows Live Messenger http://imagine-msn.com/messenger/launch80/default.aspx?locale=fr-ca --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
-- Jesse Kuhnert Tapestry/Dojo/(and a dash of TestNG), team member/developer Open source based consulting work centered around dojo/tapestry/tacos/hivemind. http://blog.opencomponentry.com
