The ActionTrackerPlugin comes with a basic css stylesheet for the tables it generates. These are uggly -- which is worth a bug item in itself -- and don't match the current skin.

The NatSkin comes with 12 styles each of which has an own look and feel. It has support for a set of plugins that add css classes to their output so that the plugins match the style of the skin. Ergo the skin must be able to override any base definitions of a plugin's css.

Unfortunately the addToHEAD() api of the twiki core does not allow to specify where the call will add the stuff into the header and defaults to append it. This in effect will override the skin's css efforts which it should not as the skins should have hightest precedence.

We need to add another parameter to addToHEAD() to either prepend or append to the HEAD. Then all plugins that make use of this api need to change. Some of my plugins do not use addToHEAD() at all just for this reason and add their css to the HEAD on their own. If the api would allow to prepend to the HEAD this function would be much more usefull. MD

---

This topic was lost from the lists due to not having a codebase field. Rediscovered 3/2/07. Just set it to "No Action" if it is dead. It sounds like something that should be disucssed in codev, though.

CC

---

addToHead is used by plugins. It is more common for skins to override plugin styles, than for plugins to override plugin styles.

The simplest of rules would then be that addToHead should be always the first style element below the <base> tag.

-- AC

Hmmm. This is a deeper issue; the html headers are stored in a hash, which is inherently unordered. So the action here is:

1. Move the html headers in TWiki.pm to an ordered collection (array)
2. Expose the full headers collection via an appropriate API
3. Deprecate addToHEAD

Just waiting for someone to do it....

CC

This proposal has changed somewhat over time - see TWiki:Codev.ProcessAddToHeadAdds

-- SvenDowideit - 31 Mar 2008