User story #4961
closed
Clean-up js/css ressources links
Added by François ARMAND almost 10 years ago.
Updated about 9 years ago.
Category:
Performance and scalability
Description
Our Javascript and CSS ressources links are a mess and we need to clean them up before even considering other performance optimization on them.
So for now, at least:
- use the minified version of the used library (jquery, ui, etc). That accounts for hundreds of ko
- clean-up ressources links: prefer full feature package to individual plugins (especially for UI - each http connection is very expensive), put ALL js loading in the main template (browser are very good to optimize identic headers), etc.
- Assignee changed from Ade Bradshaw to François ARMAND
- Status changed from In progress to Pending technical review
- Assignee changed from François ARMAND to Nicolas CHARLES
- Pull Request set to https://github.com/Normation/rudder/pull/543
PR is here: https://github.com/Normation/rudder/pull/543
The responsivness seems to be far far better !
(or perhaps it's just a fealing coming from the clean HEAD in the common-layout).
I think I tested all the pages to check nothing brokes, but perhaps I missed some (workflows ? compliance pop-up ? etc)
- Status changed from Pending technical review to 12
oh, this has been merged, but due to bad ticket number, it does not appear
commit is : rudder:f605e2e22fa78870d0acaf9d143f310d99ff7792.
- Status changed from 12 to Pending release
- Status changed from Pending release to Released
This bug has been fixed in Rudder 2.11.0~beta1 that was released yesterday.
- Tracker changed from Enhancement to User story
Also available in: Atom
PDF
Updated by 
Updated by 
Updated by 
Updated by