Frontend Performance: Remove inline styles

Bug #312167 reported by Stuart Colville on 2008-12-29
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Launchpad itself
High
Unassigned

Bug Description

Some pages around the site have around 45 elements with inline styling. See the bugs pages for example.

Removing them to an external stylesheet will reduce page weight across the board. Moved to an external file will help as the css *should* be cached whereas each *new* page visited by the user won't be.

Changed in launchpad:
importance: Undecided → Low
status: New → Triaged
Curtis Hovey (sinzui) on 2009-12-21
tags: added: css
Jonathan Lange (jml) on 2010-03-12
affects: launchpad-foundations → launchpad-web
Zearin (zearin) wrote :

Aww, come on. Launchpad…don't let me down. Use CSS smartly. :)

Curtis Hovey (sinzui) wrote :

We would appreciate help with CSS. I think Launchpad's CSS is manages by 10% of the engineers. There is still a tremdous amount of design exceptions in the applications and we need to remove the global CSS because the styles are not removed. Inlined styles are not bad, but many engineers over use them because they are not comfortable fixing the root problem in the site design.

huwshimi (huwshimi) on 2011-09-20
Changed in launchpad:
importance: Low → High
anatoly techtonik (techtonik) wrote :

Chrome -> Tools -> Development Tools -> Audits

Move combo.css include before JS include. 81% of combo.css rules are not used.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers