> I see. The reason we use a native <img> element is that IE 6 has a tendency
> to reload background images for no good reason, causing sometimes hundreds of
> hits on the server for the same image. It is a horrible bug in a horrible
> browser, but it's there nonetheless and we had to deal with it. A CSS
> background image is more flexible in general of course.
>
> What you can do however is put your own image as:
>
> RESOURCES/ops/images/xforms/help.png
Okay, now I see the true reason behind your choice of implementation.
Makes sense.
Replacing the original xforms-help-image resource is a great idea if one
is using Orbeon Forms XForms Filter for a single web application.
However, if Orbeon Forms XForms Filter is used by multiple web
applications running on the same server then the change would, of course,
have an affect on all the web applications using it, which might not be
what the developer of a single web application want to/is allowed to do.
In addition, it will be easier to update Orbeon Forms to a newer version
because no modifications need to be made--just replace the Orbeon Forms
*.war file.
For these reasons, I think overriding xforms-help-image CSS rules in
your own web application is the way to go.
Regards
-Markku
--
You receive this message as a subscriber of the
[hidden email] mailing list.
To unsubscribe: mailto:
[hidden email]
For general help: mailto:
[hidden email]?subject=help
OW2 mailing lists service home page:
http://www.ow2.org/wws