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.

[eblot]

See also #4264.

[rblank]

#7932 reported a possibly frequent clash with Trac element ids (a heading like === attachments ===, which gets an attribute id="attachments", so the CSS for the attachments <div> matches), which would be solved by a clean namespace for element ids. It was closed as a duplicate.

Prefixing all element ids with e.g. trac- should not be too difficult, as ids are mostly referenced by the style sheets. However, IIRC, element classes are quite often referenced in the code, which would make the change much more painful.

I would like to at least start the process and fix the element ids. Would trac- be a good prefix?

[eblot]

Replying to rblank:

I would like to at least start the process and fix the element ids. Would trac- be a good prefix?

The trouble is that this will break all the customized Trac installations. I guess there are many of them... So either this replacement has to wait for a major release (0.12) or better, provide a Python script to parse and update custom CSS file to match the new naming scheme.

[rblank]

Replying to eblot:

The trouble is that this will break all the customized Trac installations. I guess there are many of them... So either this replacement has to wait for a major release (0.12)

That was my intention. The CSS file updater sounds like a good idea, too, and it might even facilitate the conversion of Trac's CSS files.

[rblank]

#8514 was closed as a duplicate.

[rblank]

I guess we'll have enough incompatible changes in 0.12 without that. Let's do that later.