Forum OpenACS Q&A: Re: Portlets, Includelets and bright ideas!

Collapse
Posted by Torben Brosten on
Richard, I see you're trying to reconcile a few different css styles.

Something I've learned with css that really helps with cross browser compatibility is to reverse the cascade of the style definitions by most specific first to least specific last. For example:

div.xowiki-content #wikicmds a {..
div.xowiki-content #wikicmds a:hover {..
div.xowiki-content #wikicmds a:active {..
div.xowiki-content #wikicmds {..

div.xowiki-content div.news-item .item-footer {..

div.xowiki-content pre, div.code {..
div.xowiki-content pre p i, div.code p i {..
div.xowiki-content pre i, div.code i {..
div.xowiki-content pre em, div.code p em {..
div.xowiki-content pre em, div.code em {..
div.xowiki-content pre, .code {..
div.xowiki-content .margin-form .form-button, .margin-form
div.xowiki-content a.external {..
div.xowiki-content a.file {..
div.xowiki-content a.glossary {..
div.xowiki-content h1 {..
div.xowiki-content h2 {..
div.xowiki-content h3 {..
div.xowiki-content h4 {..
div.xowiki-content .box {..
div.xowiki-content .hr {..
div.xowiki-content .item-footer {..
div.xowiki-content .content-chunk-footer {..
div.xowiki-content .image-button img {..
div.xowiki-content {..

from: http://dekkasupply.com/resources/xowiki/xowiki.css

when using this technique, you may experience:

1. a more consistent look between browsers, or have an easier time achieving it.

2. that you don't need to reference the LI directly in css.

At some point I'd like to see the css in xowiki's code moved to its style sheet, and organized this way. (I volunteer, if Gustaf says OK to it. Gustaf?).