[MAGNOLIA-1367] css loading: some dynamic loading as for js Created: 09/Feb/07 Updated: 17/Mar/09 Resolved: 20/Jan/09 |
|
| Status: | Closed |
| Project: | Magnolia |
| Component/s: | admininterface |
| Affects Version/s: | 3.0.1 |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major |
| Reporter: | Philipp Bärfuss | Assignee: | Philipp Bärfuss |
| Resolution: | Obsolete | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Template: |
|
| Acceptance criteria: |
Empty
|
| Task DoD: |
[ ]*
Doc/release notes changes? Comment present?
[ ]*
Downstream builds green?
[ ]*
Solution information and context easily available?
[ ]*
Tests
[ ]*
FixVersion filled and not yet released
[ ] 
Architecture Decision Record (ADR)
|
| Date of First Response: |
| Description |
|
would be nice if all css placed in a special place are loaded automatically. We do that for the js class files placed in js-classes. This mainly simplifies to provide additional css classes by modules |
| Comments |
| Comment by Magnolia International [ 20/Jan/09 ] |
|
Most of the issues related to this are solved by the new "resources" module (allowing one to store resources like javascript and css in the repository) and the webdav support (allowing to edit said resources from a remote editor) |