Closed Bug 344293 Opened 20 years ago Closed 16 years ago

front.png too hard to customize when using multiple instance/single source

Categories

(Bugzilla :: User Interface, defect)

defect
Not set
minor

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: jhg, Unassigned)

Details

User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; .NET CLR 1.1.4322; .NET CLR 2.0.50727) Build Identifier: Currently the "ant" graphic displayed on the front page (front.png) is loaded as a background image in index.css. When you have a complete source directory for each instance this is not a problem. However, when using the new "multiple instance/single source" capability, there's no easy way to customize the graphic in each instance. The only way is to make a separate CSS for each instance, and then a custom template that refers to the custom CSS. It is my humble opinion that the front page graphic is part of the page's content, not its presentation, and therefore the graphic reference belongs in the template. If it were referenced there, it would be trivial to customize it per instance since there's already a custom template directory for each instance. If there's a really good reason for it to remain in the CSS, then the CSS architecture needs to be enhanced so that it is governed by the multiple- instance paradigm in the same way as the templates are. I debated whether to make this an enhancement or a normal-priority bug. Since I believe this is an unintended consequence of the multiple-instance changes, I'm making it a bug, but am open to reclassifying it as an enhancement request. Reproducible: Always
We can reclassify ourselves. :)
Severity: normal → minor
OS: Windows XP → All
Hardware: PC → All
it's implemented as a css background image to allow css skins to easily change it.
I'd say it should work if you replace <div class="intro"></div> by an <img> tag (or something) in the instance's custom index.html.tmpl...
front.png is gone since Bugzilla 3.4.
Status: UNCONFIRMED → RESOLVED
Closed: 16 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.