Issue Bug Closed

#56019ResourceCompressor: concatenateCss with forceOnTop gives wrong order

Stefan Neufeind 02/16/14, 17:11 updated 10/02/18, 12:09

Description

While testing #53116 (about concatenateJs and forceOnTop) I also checked if that part works fine for CSS. The forceOnTop works if you don’t concatenate them:

page >

config.concatenateCss = 0
page = PAGE
page {
  includeCSS {
    b = fileadmin/b.css
    b {
      forceOnTop = 0
    }
    c = fileadmin/c.css
    c {
      forceOnTop = 1
    }
    a = fileadmin/a.css
    a {
      forceOnTop = 1
    }
  }
}

gives:
<link rel="stylesheet" type="text/css" href="fileadmin/a.css?1392566437" media="all">
<link rel="stylesheet" type="text/css" href="fileadmin/c.css?1392566430" media="all">

<link rel="stylesheet" type="text/css" href="typo3temp/stylesheet_993134cfc3.css?1385132976" media="all">
<link rel="stylesheet" type="text/css" href="fileadmin/b.css?1392566433" media="all">

(okay, we might look if we can get rid of that newline in the middle)

But with config.concatenateCss = 1 the order is then:
  • default CSS
  • b
  • c
  • a
Expected behaviour (as in non-concatenated example):
  • a
  • c
  • default CSS
  • b

Reviews 2