Merge lp:~dooferlad/launchpad/upcomingwork_show_incomplete_bp into lp:launchpad
| Status: | Superseded |
|---|---|
| Proposed branch: | lp:~dooferlad/launchpad/upcomingwork_show_incomplete_bp |
| Merge into: | lp:launchpad |
| Diff against target: |
58 lines (+25/-1) 3 files modified
lib/lp/registry/browser/person.py (+5/-0) lib/lp/registry/browser/tests/test_person_upcomingwork.py (+10/-0) lib/lp/registry/templates/person-upcomingwork.pt (+10/-1) |
| To merge this branch: | bzr merge lp:~dooferlad/launchpad/upcomingwork_show_incomplete_bp |
| Related bugs: |
| Reviewer | Review Type | Date Requested | Status |
|---|---|---|---|
| James Tunnicliffe (community) | Resubmit on 2012-05-17 | ||
| Graham Binns (community) | 2012-05-15 | Needs Fixing on 2012-05-17 | |
|
Review via email:
|
|||
This proposal has been superseded by a proposal from 2012-05-18.
Description of the Change
The upcomingwork view shows blueprints that a team or individual is working on. Currently all blueprint work items start in the collapsed view, but we have had a request to have incomplete blueprints to be initially expanded.
This change adds an alt tag to the percentage complete image as well as a title, so it can be reliably found in the DOM and the information encoded in the alt tag used to find if a blueprint is complete or not. Of course, this has a pleasing side-effect of making the page more accessible.
| James Tunnicliffe (dooferlad) wrote : | # |
OK, have tested locally and got back to just your fix, so I hope you like it!
| James Tunnicliffe (dooferlad) wrote : | # |
Just trying to QA with more complex page on a clean checkout and I see the expander sprite (arrow picture) isn't there. Will attempt to track down.
| James Tunnicliffe (dooferlad) wrote : | # |
Ah, seems to be class="expander expanded" is causing problems. Will chase down a solution.
| James Tunnicliffe (dooferlad) wrote : | # |
Humm, would be because the JavaScript that adds the expander arrow looks for class="expander", so it would need a second search, if that one failed, to find class="expander expanded" and then do something different. What I think should be done is, if possible, add the CSS attribute that (if memory serves) is how the expander class knows if it is expanded or not in the template.
| James Tunnicliffe (dooferlad) wrote : | # |
Got it, but not a solution. <tbody class="
<tbody class="
<tbody class="
Still hunting...

Hi James,
As mentioned on IRC the other day, I think a better way to do this is to work out whether or not the expander should be open on the server rather than doing it all in the JS. I've created a branch for this solution here: lp:~gmb/launchpad/upcomingwork_show_incomplete_bp - feel free to merge it into your branch.
I'm not hugely familiar with work items, so I don't know how to do QA on my solution (I can't seem to make items appear in the +upcomingwork view on launchpad.dev, no matter what I try). Please let me know if my solution's not working.
We also need to find something to remove from the LP codebase if we're going to land this, or we need to get it blessed as feature work by lifeless or flacoste. I'll look into the possible options.
Cheers,
Graham