Hi,
Someone skilled in css would have to laboriously work through all the
current style sheets and try and untangle the mess that is there. My
guess is that every one of those !important declarations has been put
in as a 'quick fix' for some issue or other, so taking them out will
break whatever they were fixing.
I feel a need for a staging server, and someone with a lot of
persistence and free time on their hands.
Louis told earlier that it was impossible to get a staging server.
But just to get started (tigris.css):
font-family: "Lucida Grande", Verdana, Arial, Helvetica, sans-serif !important;
font-family: Verdana, Arial, Helvetica, sans-serif !important;
might only break some fonts, I'd say that the implications are minor... its not
that our current website is like the finesse in font styling...
a:visited, #bodycol a:visited {
color: #036;
text-decoration: none;
}
a:link, #navcol a:link, #navcol a:visited, #bodycol a:link, .tasknav a:link, .tasknav a:visited {
color: #06c;
text-decoration: none;
}
a:hover, a:active, #navcol a:hover, #navcol a:active, #bodycol a:hover, #bodycol a:active, .tasknav a:hover, .tasknav a:active {
text-decoration: underline;
}
a:link.selfref, a:visited.selfref {
color: #334 !important;
text-decoration: none;
}
a:active, a:hover, #navcol a:active, #navcol a:hover { color: #f30 !important; }
.functnbar4 a, .functnbar4 a:link, .functnbar4 a:visited {
color: #fff !important;
}
#navcol a, #breadcrumbs a {
text-decoration: none;
}
While the declarations here can be tricky, especially since there is no
background that can be assumed, I think it can hardly become worse than
the current situation (new styling of links has been bluntly introduced
with the update of Collabnet, and the styling implications were not
discussed at all, despite my remarks in the past).
Note that the code here results in the following in inst.css:
#loginbox a:link, #loginbox a:visited, #searchboxbanner a:link,
#searchboxbanner a:visited, #tasknav a:link, #tasknav a:visited, #navcol
a:link, #navcol a:visited, .application a:link, .application a:visited,
.tasknav a:link, .tasknav a:visited, #breadcrumbs a:link, #breadcrumbs
a:visited, .docs a:link, .docs a:visited {
color: #06348C !important;
}
#footer a:link, #footer a:visited, #searchboxbanner a:link, #searchboxbanner
a:visited {
color: #0033CC !important;
}
#loginbox a:hover, #loginbox a:active, #searchboxbanner a:hover,
#searchboxbanner a:active, #tasknav a:hover, #tasknav a:active, #navcol
a:hover, #navcol a:active, .application a:hover, .application a:active,
.tasknav a:hover, .tasknav a:active, #breadcrumbs a:hover, #breadcrumbs
a:active, .docs a:hover, .docs a:active, #footer a:hover, #footer a:active {
color: #698ed1 !important;
text-decoration: none !important;
}
To give another example, the currently the MAIN page breaks (people
complain about 'buttons' not looking as buttons, part of the reason:
they have underlined text, button's don't have underlined text), because
of this line in inst.css:
#loginbox a:link, #loginbox a:visited, #searchboxbanner a:link,
#searchboxbanner a:visited, .tasknav a:link, .tasknav a:visited, #bodycol
a:link, #bodycol a:visited, #footer a:link, #footer a:visited {
text-decoration: underline !important;
}
If people have worked around these !important's there is no problem,
later !important rules override earlier !important rules... but the
thing is that if you are building a page, and have difficulties finding
out why you can't set the text-decoration underline to 'none'... that
works counter productive.
There can only be a problem if there are wrong overrides that are
currently overridden by earlier !important rules, but are ineffective at
this moment because of an !important declaration in inst.css or
tigris.css ...
If we want to prepare our style for a style that is transferable, also
to a maybe new content management system, we should try to create CSS
and HTML code that is as independent as possible from the current Collab
framework.
g.,
Maarten
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
