Merge lp:~rharding/launchpad/info_portlet_1052551 into lp:launchpad
| Status: | Merged |
|---|---|
| Approved by: | Richard Harding on 2012-10-15 |
| Approved revision: | no longer in the source branch. |
| Merged at revision: | 16150 |
| Proposed branch: | lp:~rharding/launchpad/info_portlet_1052551 |
| Merge into: | lp:launchpad |
| Diff against target: |
85 lines (+26/-18) 4 files modified
lib/lp/blueprints/javascript/addspec.js (+1/-1) lib/lp/blueprints/templates/blueprint-portlet-privacy.pt (+12/-5) lib/lp/blueprints/templates/specification-index.pt (+4/-4) lib/lp/bugs/templates/bug-portlet-privacy.pt (+9/-8) |
| To merge this branch: | bzr merge lp:~rharding/launchpad/info_portlet_1052551 |
| Related bugs: |
| Reviewer | Review Type | Date Requested | Status |
|---|---|---|---|
| Benji York (community) | code | 2012-10-15 | Approve on 2012-10-15 |
|
Review via email:
|
|||
Commit Message
Update the JS initialization for the blueprint information type portlet.
Description of the Change
= Summary =
See the bug for details on how users are unable to change the InformationType
on the bluesprints from the portlet.
== Implementation Notes ==
This fixes a couple of manual styles added to the choice widget setup as well
as a missed rename for the javascript method setup_informati
setup_choice.
#24 Removes manual display:none set on the Edit action icon.
#47 Removes the manual setting of the icon to display:inline
The rest is mainly some matching of the layout of the HTML to the same thing
in the bug portlet so that I could compare the html and css classes required
to get things to work correctly.
There's also the drive by update of adding the JS module dep lp.app.choice to the addspec.js. It's indirectly gotten from requiring information_
== Q/A ==
When viewing a blueprint you should see the privacy portlet on the right side
and the edit icon should be available to change the information type.
| Richard Harding (rharding) wrote : | # |
> Looks good. A couple of minor points:
>
> It would be nice to fix the long line on line 26 of the diff.
Doh, thanks for the heads up on that.
> Would it be possible to put the explicit style attributes on line 31 and 79
> into a stylesheet?
If there was a true widget with CSS properties I'd definitely move it off. As it is, the best shortcut might be to try to turn the div's into p's of textual content, however they're set to have 0 padding and margin (ugh!).
So for now I'm going to leave this as existing bad code and hope someone gets a change to come behind and do a nice portlet widget with CSS that can be reused rather than stick such a specific rule on #information-

Looks good. A couple of minor points:
It would be nice to fix the long line on line 26 of the diff.
Would it be possible to put the explicit style attributes on line 31 and 79 into a stylesheet?