lazr-sam.css should be placed under lazr/build/assets/ along with required image files
Bug #365812 reported by
Māris Fogels
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| LAZR Javascript Library |
Triaged
|
Low
|
Unassigned | ||
| Launchpad itself |
Invalid
|
Low
|
Unassigned | ||
Bug Description
The lazr-sam.css file should be placed in the lazr/build/assets/ directory instead of its current location, lazr/build/.
If we place all of the image assets alongside it then we won't have to worry about asset paths either.
Currently, we can't use lazr-sam.css because the image paths in the file are absolute, and we would have to dump all the images into the lazr/build/ directory, which clutters everything immensely.
Fixing this should eliminate at least six CSS file requests from every Launchpad page.
| description: | updated |
| tags: | added: javascript performance |
| Changed in lazr-js: | |
| importance: | Undecided → Medium |
| status: | New → Triaged |
| Changed in launchpad-foundations: | |
| importance: | Undecided → Medium |
| status: | New → Triaged |
| tags: | added: ui-easy |
| tags: |
added: easy ui removed: ui-easy |
| Changed in lazr-js: | |
| importance: | Medium → Low |
| Changed in launchpad: | |
| importance: | Medium → Low |
| Changed in launchpad: | |
| status: | Triaged → Invalid |
To post a comment you must log in.
