Feature request: we don't adhere to the css 'unique' param, nor do we sort css/javascript by unique name
Reported by dleffler | April 14th, 2014 @ 03:33 PM | in 2.3.8 (closed)
We currently only use the 'unique' param for inline css code and not the other expCSS::pushToHead() params (though we did in the 2.0 preview release). This is especially important since css is a cascading implementation.
Furthermore, we don't seem to be sorting by unique-name for css nor javascript.
Comments and changes to this ticket
-
expNinja February 3rd, 2016 @ 03:34 PM
(from [06532d86afcf8437decbd858d8cd63e36d1950e6]) Now allows for passing an array of scripts to expJavascript::pushToFoot/expTheme::foot(), etc... like we allow for css; also now compensates for not having passed those scripts or css with the 'unique' param so we assign one based on microtime to keep errors out [#1146] https://github.com/exponentcms/exponent-cms/commit/06532d86afcf8437...
Please Sign in or create a free account to add a new ticket.
With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.
Create new ticket
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile ยป
Bug Tracker for Exponent CMS
expNinja