adjust admin css to not depend upon the !important declaration.
If I take a copy of the admin templates and modify base_site to include my own CSS in the block extrastyle, the existing administration css will attempt to overwrite my changes (even those I declare as !important) when loading certain views. For example, the loading of changelists.css will alter my rules as the change_list template also adds to extrastyle, and does so after mine are injected. I imagine that I could alter where I inject CSS to use the extrahead block instead of extrastyle, but it doesn't seem too logical to do so.
Mostly, I'm finding it nigh on impossible to move the filters menu to the left of a changelist, as the changelists.css says to add a margin-right with !important. I can't counteract this, as my stylesheet (complete with !important) is included beforehand, thus is superceded.
I propose rejigging the CSS to not be dependent upon !important (maybe it can be got around by using even finer grained specificity?) where possible so that we might customise the administration without having to resort to butchering the existing admin templates (and making future merges potentially a pain), which serve their purpose very well.
Change History
(11)
| Triage Stage: |
Unreviewed → Accepted
|
| Severity: |
→ Normal
|
| Type: |
→ Cleanup/optimization
|
| Resolution: |
→ fixed
|
| Status: |
new → closed
|
Not a blocker for 1.0.3.