progress bars on RoadMap are wrong

[jtauber@…]

Often show complete when not 100% or partially complete when 0%

[Christian Boos]

Can you provide us with the actual numbers, closed tickets vs. total number of tickets, so that we can try to reproduce the issue? Also, do you have the latest trunk, as there were some recent changes in this area…

[jtauber@…]

The most common is shading half the bar for 0% (e.g. when closed is 0 and active is 1) (you can currently see that at ​http://trac.pyworks.org/pyjamas/roadmap ).

I'll update to the latest (currently running @4045) and see if I notice it again.

[sid]

The roadmap page displays fine for me… the shading box for the 3rd milestone is all white, not 50%. What browser are you using?

[sid]

Hmm. Works fine for me on Firefox 2.0 on Mac, but renders incorrectly (as 100% filled bar when should be 0%) on Opera 9. The code output is different than from 0.10:

<div class="info">
  <h2><a href="/pyjamas/milestone/0.3">Milestone: <em>0.3</em></a></h2>
     <p class="date">No date set</p>
     <table class="progress">
       <td class="closed" style="width: 0.0%">
         <a href="/pyjamas/query?status=closed&amp;milestone=0.3" title="1 of 1 ticket closed"></a>
       </td>
       <td class="open" style="width: 100.0">
         <a href="/pyjamas/query?status=new&amp;status=assigned&amp;status=reopened&amp;milestone=0.3" title="1 of 1 ticket active"></a>
       </td>
     </table>
     <p class="percent">0.0%</p>
     <dl>
       <dt>Closed tickets:</dt>
       <dd><a href="/pyjamas/query?status=closed&amp;milestone=0.3">0</a></dd>
       <dt>Active tickets:</dt>
       <dd><a href="/pyjamas/query?status=new&amp;status=assigned&amp;status=reopened&amp;milestone=0.3">1</a></dd>
     </dl>
 </div>

In particular, the percentage is now displayed with decimal points, and the <td class="open" style="width: 100.0"> is missing a percent sign.

[Christian Boos]

Right, reproduced. OTOH, with Firefox 2.0, I've got <td class="open" style="">, which is also not that correct.

I'll check whether this bug survives after the patch on #2314 is integrated.

[jtauber@…]

Just for the record, in answer to Sid's question - I am seeing the problem on Safari. I'll verify once this bug or #2314 is closed.

[Christian Boos]

r4150 seems to have fixed it for me (Opera 9).

Please confirm for other browsers.

[jtauber@…]

r4150 isn't working at all for me. I've filed #4090 instead of explain here.

[jtauber@…]

Okay, upgraded to r4179 and it works on Safari.

[sid]

Your site (linked in comment:2) works now for me as well on Firefox 2.0 and Opera 9. Seems okay to close now.

[Christian Boos]

Works fine for IE 6 too, so whatever was the problem, it went away with Justin's patch ;)