Feeling Lucky
?
?
[#25892] - [4.0] [backend-template] Unused CSS
- Closed
- 4 Feb 2020
- Medium
- Build: staging
- # 25892
As stated in the PR for the new template, it's importing a lot of unused CSS, such as:
@import "../../../../../media/vendor/bootstrap/scss/carousel";
@import "../../../../../media/vendor/bootstrap/scss/navbar";
@import "../../../../../media/vendor/bootstrap/scss/media";
The killer though is the Bootstrap utilities.
@import "../../../../../media/vendor/bootstrap/scss/utilities";
I would strong suggest creating a new utilities.scss and only define the ones used by the template.
joomla-cms-bot
- | Labels |
Added:
?
|
||
franz-wohlkoenig
- | Labels |
Added:
?
|
||
| Status | New | ⇒ | Discussion |
C-Lodder
- comment
- 16 Aug 2019
The backend template should make most of Bootstrap available
That's still possible by a sort of tree shaking approach
HLeithner
- comment
- 16 Aug 2019
Loading everything in each request isn't very nice but as long as there is no way to only load whats needed by a page or extension it better to have everything ready for the extension dev.
If you can came up with a good solution that can easily handled by 3rd party it would be great.
brianteeman
- comment
- 4 Feb 2020
I am going to close this in the absence of a suggested solution based on the comments of @HLeithner and @mbabker above
| Status | Discussion | ⇒ | Closed |
| Closed_Date | 0000-00-00 00:00:00 | ⇒ | 2020-02-04 13:12:05 |
| Closed_By | ⇒ | brianteeman |
Disagree. The backend template should make most of Bootstrap available to developers out-of-the-box to make integrations easier, the template shouldn't arbitrarily strip out parts of Bootstrap that the template designers did not decide to use in the core layouts (contrary to what some will say, the backend is more than 3 screens).