Merge lp:~jcsackett/launchpad/package-pickers-navigation-jumps into lp:launchpad
Status: | Merged |
---|---|
Approved by: | j.c.sackett |
Approved revision: | no longer in the source branch. |
Merged at revision: | 13265 |
Proposed branch: | lp:~jcsackett/launchpad/package-pickers-navigation-jumps |
Merge into: | lp:launchpad |
Diff against target: |
37 lines (+9/-0) 2 files modified
lib/canonical/launchpad/icing/style-3-0.css (+4/-0) lib/lp/app/browser/tales.py (+5/-0) |
To merge this branch: | bzr merge lp:~jcsackett/launchpad/package-pickers-navigation-jumps |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Benji York (community) | code | Approve | |
Review via email: mp+65222@code.launchpad.net |
This proposal supersedes a proposal from 2011-06-17.
Commit message
[r=benji][bug=698020,698024] Fixes a few minor UI issues with package picker.
Description of the change
Summary
=======
Package pickers have a variety of visual issues.
* Navigation links change position as you navigate through batches because the picker can resize for longer package names
* BinaryAndSource
This fixes those two issues.
Proposed Fix
============
* Set the picker widget to use a fixed width, so that it doesn't resize as the batch loads.
* Update the code selecting the sprite css to provide the package sprite for IBinaryAndSourc
Preimplementation
=================
Spoke with Curtis Hovey about the CSS fixes for the picker.
Implementation
==============
lib/lp/
-------
* Updated the code that provides sprite_css to provide the appropriate sprite for IBInaryAndSourc
lib/canonical/
-------
* Changed yui3-picker's width to 40%, to closely mimic its previous 'auto' behavior but have a fixed width at a given window size.
Tests
=====
No new tests, as these were trivial cosmetic changes.
QA
==
Follow through the instructions on the linked bugs, which provide "What should happen" examples for QA.
Lint
====
make lint was not generating output for me. I will get it running and fix any lint before landing.
The building of JavaScript via a page template in form-picker- macros. pt
looks like a JS injection hazard.
In particular the strings inserted verbatim from the view. The JS
should really be just a string literal (or even better, moved to its own
file) and the data can be exposed to the browser using the JSON request
cache (see IJSONRequestCache).