Bug #20477
CSS in BE has no general rules, only specific
Status: | Closed | Start date: | 2009-05-19 | |
---|---|---|---|---|
Priority: | Should have | Due date: | ||
Assigned To: | Steffen Kamper | % Done: | 0% |
|
Category: | - | Spent time: | - | |
Target version: | - | |||
TYPO3 Version: | 4.3 | Is Regression: | ||
PHP Version: | 5.3 | Sprint Focus: | ||
Complexity: |
Description
This leads to the fact that if you write your own BE-module, you have to write your own CSS rules.
Currently we have two kinds of BE-modules:- modules using docheaders
- modules without docheaders
Both should get the basic rules assigned so you don't have to care about the generic look of your module
(issue imported from #M11150)
Related issues
History
#1 Updated by Steffen Kamper about 6 years ago
best example you find in current css:
body#typo3-alt-doc-php, body#typo3-db-list-php, body#typo3-mod-web-perm-index-php, body#typo3-mod-web-info-index-php, body#typo3-mod-web-func-index-php, body#typo3-mod-user-ws-index-php, body#typo3-mod-user-ws-workspaceforms-php, body#typo3-mod-php, body#typo3-mod-tools-em-index-php, body#typo3-wizard-rte-php, body#typo3-pagetree, body#typo3-db-new-php, body#typo3-move-el-php, body#typo3-show-rechis-php, body#typo3-wizard-table-php, body#typo3-wizard-forms-php, body#ext-cms-layout-db-layout-php, body#ext-tstemplate-ts-index-php, body#ext-version-cm1-index-php, body#ext-setup-mod-index-php, body#ext-tsconfig-help-mod1-index-php, body#ext-lowlevel-dbint-index-php, body#ext-lowlevel-config-index-php, body#ext-indexed-search-mod-index-php, body#ext-cms-layout-db-new-content-el-php, body#imp-exp-mod {stylesheet.css (Linie 189)
height:100%;
margin:0;
overflow:hidden;
padding:0;
}
#2 Updated by Francois Suter about 6 years ago
We definitely need a set of generic rules, then each module can add its own specific styles.
Needed also are styles for messages (success, info, notice, warning and error).
#3 Updated by Steffen Gebert over 5 years ago
Yes, I talked to Benni and we want to get rid of this body-monster (especially as it should be (almost) no problem to just change the generic rule.
I wanted to wait until #22507 is comitted, hopefully this happens tomorrow and we get this one also in tomorrow.
#4 Updated by Steffen Kamper over 5 years ago
Committed to trunk rev 7502