id summary reporter owner description type status priority milestone component version severity resolution keywords cc branch changelog apichanges internalchanges 5997 Clean name-spaces for CSS for 0.11+? shap@… "I suspect that it may be too late for this, but I think this is a low-risk change. Trac uses CSS all over the place. This is good. The problem is that I need to pass through some content that *also* uses CSS, and there is a problem of name space collision in the choices of names for the class attribute. Since Trac is cutting over the template system, now is an opportune time to look at CSS issues if there is a desire to do so. How difficult would it be for Trac to adopt the convention that all class attributes and all id attributes that are emitted from the trac templates would begin with ""trac-"" so that they are less likely to collide with CSS within content? In our case, we cannot simply import the incoming content once and have done; it is a reference manual that we need to maintain externally via our version control system. Our goal is to simultaneously make it available within the Wiki for commenting and feedback. I considered re-writing the class attributes on our content using XSLT. It is doable, but it is probably beyond the skills of most XSLT authors." enhancement new normal next-major-releases general devel normal css consider patch leho@… Ryan J Ollos