View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0002814 | mantisbt | feature | public | 2002-12-27 14:23 | 2014-12-08 00:34 |
Reporter | Assigned To | daryn | |||
Priority | normal | Severity | feature | Reproducibility | always |
Status | closed | Resolution | fixed | ||
Product Version | git trunk | ||||
Target Version | 1.3.0-beta.1 | Fixed in Version | 1.3.0-beta.1 | ||
Summary | 0002814: Prefix CSS class names | ||||
Description | It would be nice, if CSS class names will be prefixed via definedable string. It could improve Mantis ingrattion ability into larger projects. Nepto, <a href="http://nepto.sk/">http://nepto.sk/</a> | ||||
Tags | No tags attached. | ||||
The other option is to have all Mantis forms/ui inside a div with class "mantis". This way our styles will look as follows: div.mantis tr { blah blah } ... and so on. I would prefer this option over using a prefix. |
|
I checked bugzilla and it adds a "bugzilla" class to the <body> tag, essentially achieving the same purpose. This is probably the least intrusive modification we could do; Victor, if you agree I will take care of this. |
|
The thing that we have to keep in mind is integrations with CMS systems, for example, PostNuke, etc. In that case the div option would be better than the body option. Although I would have to agree that the body option is better than what we are doing now. Would it be possible to have the code that generate <body>, generate <body><div class="mantis"> and </body> becomes </div></body>? |
|
sure, though I think the former is better because (IIRC) style defined for <body> are inherited by childs while this does not happens with <div>s I think we will need more input from guys trying such integrations, otherwise we just waste time. |
|
This feature has been added in the master branch. |
|
Marking as 'acknowledged' not resolved/closed to track that change gets ported to master-2.0.x branch |
|