Issue Bug Closed

#93184"includeCSS" with "excludeFromConcatenation" wrongly moved before concatenated file

Kurt Ludikovsky 12/29/20, 14:16 updated 07/17/24, 12:12

Description

*Problem*
When a CSS-file is excluded from concatenation by the inlineCSS disableCompression-parameter it is positioned before the concatenated CSS-files. This destroys the intended effect of overwriting styles, and makes the file useless.

*Details*
With

config {
  minifyJS = 0
  minifyCSS = 0
  compressJs = 0
  compressCss = 0
  concatenateJs = 0
  concatenateCss = 0
}

and

page.includeCSS {
  file1 = fileadmin/templates/assets/css/mybootstrap.css
  file1.disableCompression = 1
  file1.excludeFromConcatenation = 1
}

the resulting output is
clipboard-202012291457-5armt.png

While with

config {
  minifyJS = 1
  minifyCSS = 1
  compressJs = 1
  compressCss = 1
  concatenateJs = 1
  concatenateCss = 1
}

and

page.includeCSS {
  file1 = fileadmin/templates/assets/css/mybootstrap.css
  file1.disableCompression = 1
  file1.excludeFromConcatenation = 1
}

the noncompressed file is put at first
clipboard-202012291502-sax59.png

This is – as I assume – against the intention as those exclusions are basically used for testing and modification of before defined styles.

Reviews 0

No change resolves or names this issue in its commit message, and no comment links one.