At the moment, the basic 'out-of-the-box' OpenACS renders well on a broad range of browsers. However, increasingly, when OpenACS is used as a toolkit it is 're-skinned'.
When re-styling the basic OpenACS, and when creating pages in xowiki, the best practice is to use W3C standards including CSS. However, this immediately creates a problem with IE5.x, IE6 and IE7, all of which to varying extents either do not fully support the standards, or implement features incorrectly. This road leads to 'coding for individual browser' hell!
Instead, there is a javascript library which confers W3C compliance on these older IE versions, in some cases adding capabilities (i.e. child selector to IE6). The full list of improvements is here:
http://ie7-js.googlecode.com/svn/test/index.html
Whilst this would not always be necessary in all applications, I can certainly see it being useful. It can be added by modifying the openacs templates to source the necessary scripts in the HEAD of every document. The scripts are here:
http://www.charlescooke.me.uk/web/lab_notes/ie7_script.html
Would it be worth adding this as a subsite parameter to acs-subsites and including the scripts in 'resources', so that this retroactive standards compliance behaviour can be activated without having to hack the templates?
Any thoughts?
Regards
Richard