drupal/misc/drupal.css

632 lines
10 KiB
CSS
Raw Normal View History

2003-09-28 21:10:43 +00:00
/* $Id$ */
2003-09-25 07:27:22 +00:00
/*
** HTML elements
*/
fieldset {
margin-bottom: 1em;
padding: .5em;
}
form {
margin: 0;
padding: 0;
}
hr {
height: 1px;
border: 1px solid gray;
}
img {
border: 0;
}
table {
border-collapse: collapse;
}
th {
text-align: left;
padding-right: 1em;
border-bottom: 3px solid #ccc;
white-space: nowrap;
}
th.active img {
display: inline;
}
tr.even, tr.odd {
background-color: #eee;
border-bottom: 1px solid #ccc;
}
tr.even, tr.odd {
padding: 0.1em 0.6em;
}
td.active {
background-color: #ddd;
}
/*
** Menu styles
*/
.menu {
padding: 0 0 0 0.5em;
}
.menu ul {
list-style: none;
border: none;
text-align:left;
}
.menu li a {
width: 100%;
text-decoration: none;
}
li.expanded {
list-style-type: circle;
list-style-image: url(menu-expanded.png);
padding: 0.2em 0.5em 0 0;
margin: 0;
}
li.collapsed {
list-style-type: disc;
list-style-image: url(menu-collapsed.png);
padding: 0.2em 0.5em 0 0;
margin: 0;
}
li.leaf {
list-style-type: square;
list-style-image: url(menu-leaf.png);
padding: 0.2em 0.5em 0 0;
margin: 0;
}
li a.active {
color: #000;
}
td.menu-disabled {
background: #ccc;
}
/*
** Other common styles
*/
.breadcrumb {
padding-bottom: .5em
}
.block-region {
background-color: #ffff66;
margin-top: 4px;
margin-bottom: 4px;
padding: 3px;
}
.block ul {
margin: 0;
padding: 0 0 0.25em 1em;
}
br.clear {
clear: both;
height: 0px;
}
.container-inline div {
display: inline;
}
.container-inline .form-submit {
margin: 0;
}
.error {
color: red;
}
.item-list .icon {
color: #555;
float: right;
padding-left: 0.25em;
clear: right;
}
.item-list .icon a {
color: #000;
text-decoration: none;
}
.item-list .icon a:hover {
color: #000;
text-decoration: none;
}
.item-list .title {
font-weight: bold;
}
.item-list ul {
margin: 0 0 0.75em 0;
padding: 0;
}
.item-list ul li {
margin: 0 0 0.25em 1.5em;
padding: 0;
list-style: disc;
}
.form-item {
margin-top: 1em;
margin-bottom: 1em;
}
tr.odd .form-item, tr.even .form-item {
margin-top: 0;
margin-bottom: 0;
white-space: nowrap;
}
.form-item input.error, .form-item textarea.error {
border: 2px solid red;
}
.form-item .description {
font-size: 0.85em;
}
.form-item label {
font-weight: bold;
}
.form-item label.option {
font-weight: normal;
}
.form-submit {
margin: 0.5em 0;
}
.marker, .form-required {
color: #f00;
}
.more-link {
text-align: right;
}
.node-form .form-text {
display: block;
width: 95%;
}
.node-form .standard {
clear: both;
}
.node-form textarea {
display: block;
width: 95%;
}
.node-form .attachments fieldset {
float: none;
display: block;
}
.nowrap {
white-space: nowrap;
}
.ok {
color: #080;
}
#pager {
clear: both;
text-align: center;
}
#pager div {
padding: 0.5em;
}
.path {
padding-bottom: 0.7em;
font-size: 1.1em;
}
/*
** Module specific styles
*/
#aggregator .feed img {
float: right;
}
#aggregator .news-item {
clear: both;
padding-bottom: 1em;
}
#aggregator .news-item .date {
float: right;
}
#aggregator .news-item .body {
margin-top: 1em;
margin-left: 1em;
}
#aggregator .news-item .body .feed {
font-size: 0.9em;
}
#aggregator .news-item .title {
float: left;
}
#aggregator .news-item .description {
clear: both;
}
#aggregator td {
vertical-align: bottom;
}
#aggregator td.categorize-item {
white-space: nowrap;
}
#aggregator .categorize-item .news-item .body {
margin-top: 0;
}
#aggregator .categorize-item h3 {
margin-bottom: 1em;
margin-top: 0;
}
.book {
margin: 1em 0 1em 0;
}
.book .title {
font-weight: bold;
font-size: 1.3em;
margin-bottom:1em;
}
.book .tree {
padding-top:1em;
border-top: 1px solid #888;
padding-bottom: 1em;
}
.book .name {
padding-top:1em;
font-weight: bold;
font-size: 1em;
}
.book .nav {
border-top: 1px solid #888;
border-bottom: 1px solid #888;
padding-bottom: 3em;
padding-top: 1em;
clear: both;
}
.book .nav .links {
clear: both;
}
.book .nav .titles {
clear: both;
}
.book .nav .prev {
float: left;
text-align: left;
width: 45%;
}
.book .nav .next {
float: right;
text-align: right;
width: 45%;
}
.book .nav .up {
text-align: center;
}
.calendar .row-week td a {
display: block;
}
.calendar .row-week td a:hover {
background-color: #888; color: #fff;
}
.calendar a {
text-decoration: none;
}
.calendar a:hover {
text-decoration: none;
}
.calendar table {
border-collapse: collapse;
width: 100%;
border: 1px solid #000;
}
.calendar td, .calendar th {
text-align: center;
border: 1px solid #000;
padding: 1px;
margin: 0;
font-size: 0.8em;
}
.calendar td.day-blank {
border: 0;
}
The Input formats - filter patch has landed. I still need to make update instructions for modules and update the hook docs. Here's an overview of the changes: 1) Multiple Input formats: they are complete filter configurations (what filters to use, in what order and with which settings). Input formats are admin-definable, and usage of them is role-dependant. For example, you can set it up so that regular users can only use limited HTML, while admins can free HTML without any tag limitations. The input format can be chosen per content item (nodes, comments, blocks, ...) when you add/edit them. If only a single format is available, there is no choice, and nothing changes with before. The default install (and the upgrade) contains a basic set of formats which should satisfy the average user's needs. 2) Filters have toggles Because now you might want to enable a filter only on some input formats, an explicit toggle is provided by the filter system. Modules do not need to worry about it and filters that still have their own on/off switch should get rid of it. 3) Multiple filters per module This was necessary to accomodate the next change, and it's also a logical extension of the filter system. 4) Embedded PHP is now a filter Thanks to the multiple input formats, I was able to move the 'embedded PHP' feature from block.module, page.module and book.module into a simple filter which executes PHP code. This filter is part of filter.module, and by default there is an input format 'PHP', restricted to the administrator only, which contains this filter. This change means that block.module now passes custom block contents through the filter system. As well as from reducing code duplication and avoiding two type selectors for page/book nodes, you can now combine PHP code with other filters. 5) User-supplied PHP code now requires <?php ?> tags. This is required for teasers to work with PHP code. Because PHP evaluation is now just another step in the filter process, we can't do this. Also, because teasers are generated before filtering, this would result in errors when the teaser generation would cut off a piece of PHP code. Also, regular PHP syntax explicitly includes the <?php ?> tags for PHP files, so it makes sense to use the same convention for embedded PHP in Drupal. 6) Filter caching was added. Benchmarking shows that even for a simple setup (basic html filtering + legacy URL rewriting), filtercache can offer speedups. Unlike the old filtercache, this uses the normal cache table. 7) Filtertips were moved from help into a hook_filter_tips(). This was required to accomodate the fact that there are multiple filters per module, and that filter settings are format dependant. Shoehorning filter tips into _help was ugly and silly. The display of the filter tips is done through the input format selector, so filter_tips_short() no longer exists. 8) A more intelligent linebreak convertor was added, which doesn't stop working if you use block-level tags and which adds <p> tags.
2004-08-10 18:34:29 +00:00
.tips {
margin-top: 0;
margin-bottom: 0;
padding-top: 0;
padding-bottom: 0;
The Input formats - filter patch has landed. I still need to make update instructions for modules and update the hook docs. Here's an overview of the changes: 1) Multiple Input formats: they are complete filter configurations (what filters to use, in what order and with which settings). Input formats are admin-definable, and usage of them is role-dependant. For example, you can set it up so that regular users can only use limited HTML, while admins can free HTML without any tag limitations. The input format can be chosen per content item (nodes, comments, blocks, ...) when you add/edit them. If only a single format is available, there is no choice, and nothing changes with before. The default install (and the upgrade) contains a basic set of formats which should satisfy the average user's needs. 2) Filters have toggles Because now you might want to enable a filter only on some input formats, an explicit toggle is provided by the filter system. Modules do not need to worry about it and filters that still have their own on/off switch should get rid of it. 3) Multiple filters per module This was necessary to accomodate the next change, and it's also a logical extension of the filter system. 4) Embedded PHP is now a filter Thanks to the multiple input formats, I was able to move the 'embedded PHP' feature from block.module, page.module and book.module into a simple filter which executes PHP code. This filter is part of filter.module, and by default there is an input format 'PHP', restricted to the administrator only, which contains this filter. This change means that block.module now passes custom block contents through the filter system. As well as from reducing code duplication and avoiding two type selectors for page/book nodes, you can now combine PHP code with other filters. 5) User-supplied PHP code now requires <?php ?> tags. This is required for teasers to work with PHP code. Because PHP evaluation is now just another step in the filter process, we can't do this. Also, because teasers are generated before filtering, this would result in errors when the teaser generation would cut off a piece of PHP code. Also, regular PHP syntax explicitly includes the <?php ?> tags for PHP files, so it makes sense to use the same convention for embedded PHP in Drupal. 6) Filter caching was added. Benchmarking shows that even for a simple setup (basic html filtering + legacy URL rewriting), filtercache can offer speedups. Unlike the old filtercache, this uses the normal cache table. 7) Filtertips were moved from help into a hook_filter_tips(). This was required to accomodate the fact that there are multiple filters per module, and that filter settings are format dependant. Shoehorning filter tips into _help was ugly and silly. The display of the filter tips is done through the input format selector, so filter_tips_short() no longer exists. 8) A more intelligent linebreak convertor was added, which doesn't stop working if you use block-level tags and which adds <p> tags.
2004-08-10 18:34:29 +00:00
font-size: 0.9em;
}
#forum .description {
font-size: 0.9em;
margin: 0.5em;
}
#forum td.created, #forum td.posts, #forum td.topics, #forum td.last-reply, #forum td.replies, #forum td.pager {
white-space: nowrap;
}
#forum td.posts, #forum td.topics, #forum td.replies, #forum td.pager {
text-align: center;
}
.locale-untranslated {
font-style: normal;
text-decoration: line-through;
}
#node-admin-filter ul {
list-style-type: none;
padding: 0px;
margin: 0px;
width: 100%;
}
#node-admin-buttons {
float: left;
margin-left: 0.5em;
clear: right;
}
dl.multiselect dd.b, dl.multiselect dd.b .form-item, dl.multiselect dd.b select {
font-family: inherit;
font-size: inherit;
width: 14em;
}
dl.multiselect dd.a, dl.multiselect dd.a .form-item {
width: 8em;
}
dl.multiselect dt, dl.multiselect dd {
float: left;
line-height: 1.75em;
padding: 0px;
margin: 0px 1em 0px 0px;
}
dl.multiselect .form-item {
height: 1.75em;
margin: 0px;
}
#permissions td.module, #blocks td.region {
font-weight: bold;
}
#permissions td.permission, #blocks td.block, #taxonomy td.term, #taxonomy td.message {
padding-left: 1.5em;
}
#access-rules .access-type, #access-rules .rule-type {
margin-right: 1em;
float: left;
}
#access-rules .access-type .form-item, #access-rules .rule-type .form-item {
margin-top: 0;
}
#access-rules .mask {
clear: both;
}
.poll .bar {
height: 1em;
margin: 1px 0;
background-color: #ddd;
}
.poll .bar .foreground {
background-color: #000;
height: 1em;
clear: left;
float: left;
}
.poll .links {
text-align: center;
}
.poll .percent {
text-align: right;
}
.poll .total {
text-align: center;
}
.poll .vote-form {
text-align: center;
}
.poll .vote-form .choices {
text-align: left;
margin: 0 auto;
display: table;
}
.profile {
clear: both;
margin: 1em 0 1em 0;
}
.profile .picture {
float: right;
margin: 0 1em 1em 0;
}
.node-form .poll-form fieldset {
display: block;
}
img.screenshot {
border: 1px solid #808080;
display: block;
margin: 2px;
}
- Patch #12232 by Steven/UnConed: search module improvements. 1) Clean up the text analyser: make it handle UTF-8 and all sorts of characters. The word splitter now does intelligent splitting into words and supports all Unicode characters. It has smart handling of acronyms, URLs, dates, ... 2) It now indexes the filtered output, which means it can take advantage of HTML tags. Meaningful tags (headers, strong, em, ...) are analysed and used to boost certain words scores. This has the side-effect of allowing the indexing of PHP nodes. 3) Link analyser for node links. The HTML analyser also checks for links. If they point to a node on the current site (handles path aliases) then the link's words are counted as part of the target node. This helps bring out commonly linked FAQs and answers to the top of the results. 4) Index comments along with the node. This means that the search can make a difference between a single node/comment about 'X' and a whole thread about 'X'. It also makes the search results much shorter and more relevant (before this patch, comments were even shown first). 5) We now keep track of total counts as well as a per item count for a word. This allows us to divide the word score by the total before adding up the scores for different words, and automatically makes noisewords have less influence than rare words. This dramatically improves the relevancy of multiword searches. This also makes the disadvantage of now using OR searching instead of AND searching less problematic. 6) Includes support for text preprocessors through a hook. This is required to index Chinese and Japanese, because these languages do not use spaces between words. An external utility can be used to split these into words through a simple wrapper module. Other uses could be spell checking (although it would have no UI). 7) Indexing is now regulated: only a certain amount of items will be indexed per cron run. This prevents PHP from running out of memory or timing out. This also makes the reindexing required for this patch automatic. I also added an index coverage estimate to the search admin screen. 8) Code cleanup! Moved all the search stuff from common.inc into search.module, rewired some hooks and simplified the functions used. The search form and results now also use valid XHTML and form_ functions. The search admin was moved from search/configure to admin/search for consistency. 9) Improved search output: we also show much more info per item: date, author, node type, amount of comments and a cool dynamic excerpt à la Google. The search form is now much more simpler and the help is only displayed as tips when no search results are found. 10) By moving all search logic to SQL, I was able to add a pager to the search results. This improves usability and performance dramatically.
2004-10-31 03:03:27 +00:00
.search-form {
margin-bottom: 1em;
}
.search-form p {
margin-top: 0;
margin-bottom: 0.2em;
padding-top: 0;
padding-bottom: 0;
}
.search-form input {
margin-top: 0;
margin-bottom: 0;
}
.search-results p {
margin-top: 0;
}
.search-results dt {
font-size: 1.1em;
}
.search-results dd {
margin-bottom: 1em;
}
.search-results .search-info {
font-size: 0.85em;
}
#tracker td.replies {
text-align: center;
}
#tracker table {
width: 100%;
}
#user-login-form {
text-align: center;
}
.more-help-link {
font-size: 0.85em;
text-align: right;
}
tr.watchdog-user {
background: #ffd;
}
tr.watchdog-user .active {
background: #eed;
}
tr.watchdog-content {
background: #ddf;
}
tr.watchdog-content .active {
background: #cce;
}
tr.watchdog-page-not-found, tr.watchdog-access-denied {
background: #dfd;
}
2005-03-27 21:28:25 +00:00
tr.watchdog-page-not-found .active, tr.watchdog-access-denied .active {
background: #cec;
}
tr.watchdog-error {
background: #ffc9c9;
}
tr.watchdog-error .active {
background: #eeb9b9;
}
.comment .links .form-item {
display: inline;
white-space: nowrap;
}
.comment .links .form-item br {
display: none;
}
#comment-moderation-button {
text-align: center;
}
/* Tab navigation */
ul.primary {
border-collapse: collapse;
padding: 0 0 0 1em;
white-space: nowrap;
list-style: none;
margin: 5px;
height: auto;
line-height: normal;
border-bottom: 1px solid #bbb;
}
ul.primary li {
display: inline;
}
ul.primary li a {
background-color: #ddd;
border-color: #bbb;
border-width: 1px;
border-style: solid solid none solid;
height: auto;
margin-right: 0.5em;
padding: 0 1em;
text-decoration: none;
}
ul.primary li.active a {
background-color: #fff;
border: 1px solid #bbb;
border-bottom: #fff 1px solid;
}
ul.primary li a:hover {
background-color: #eee;
border-color: #ccc;
border-bottom-color: #eee;
}
ul.secondary {
border-bottom: 1px solid #bbb;
padding: 0.5em 1em 0.5em 1em;
margin: 5px;
}
ul.secondary li {
display: inline;
padding: 0 1em;
border-right: 1px solid #ccc;
}
ul.secondary a {
padding: 0;
text-decoration: none;
}
ul.secondary a.active {
border-bottom: 4px solid #999;
}
/*
** Autocomplete styles
*/
/* Suggestion list */
#autocomplete {
position: absolute;
border: 1px solid;
overflow: hidden;
}
#autocomplete ul {
margin: 0;
padding: 0;
list-style: none;
}
#autocomplete li {
background: #fff;
color: #000;
white-space: pre;
cursor: default;
}
#autocomplete li.selected {
background: #0072b9;
color: #fff;
}
/* Animated throbber */
html.js input.form-autocomplete {
background: url('throbber.gif') no-repeat 100% 2px;
}
html.js input.throbbing {
background-position: 100% -18px;
}
/*
** Progressbar styles
*/
.progress {
font-weight: bold;
}
.progress .bar {
background: #fff url('progress.gif');
border: 1px solid #00375a;
height: 1.5em;
margin-top: 0.2em;
}
.progress .filled {
background: #0072b9;
height: 1em;
border-bottom: 0.5em solid #004a73;
width: 0%;
}
.progress .percentage {
float: right;
}
/*
** Collapsing fieldsets
*/
html.js fieldset.collapsed {
border-bottom-width: 0;
border-left-width: 0;
border-right-width: 0;
margin-bottom: 0;
}
html.js fieldset.collapsed * {
display: none;
}
html.js fieldset.collapsed table *,
html.js fieldset.collapsed legend,
html.js fieldset.collapsed legend * {
display: inline;
}
html.js fieldset.collapsible legend a {
padding-left: 15px;
background: url('menu-expanded.png') 5px 50% no-repeat;
}
html.js fieldset.collapsed legend a {
background-image: url('menu-collapsed.png');
}
// Note: IE-only fix due to '* html' (breaks Konqueror otherwise).
* html.js fieldset.collapsible legend a {
display: block;
}