Message4355
It was a while ago since I looked a this, so my memory is a bit hazy...
I believe what I mean is something like the following scenario:
* assume there are 10 issues in the tracker
* I am looking at a page that contains next/previous links containing
'pagesize=10'
* While I am looking at this page, someone else creates a new issue
(meaning 11 issues in total)
* I then click on a next/previous link, the 'pagesize=10' value is
propogated to the following page that loads and any next/previous links
loaded on the 'following' page still contain 'pagesize=10' instead of
'pagesize=11' (which is the new total).
I just realised that for most people this might be confusing as there
probably won't be any next/previous links (because it is showing all
possible issues already). I have set up some custom views/reports where
the next/previous links actually mean next/previous month (not pagination).
The example of a saved query (like you mentioned) would indeed seem to
be another instance where the inability to distinguish between 'all
issues' and '# issues' would be an issue.
I still may not be explaining myself clearly, so feel free to query me
further.
Also, thanks for picking up on the errant '_size' references. I'll sort
another patch to fix these. |
|
Date |
User |
Action |
Args |
2011-07-26 01:36:34 | jerrykan | set | messageid: <1311644194.99.0.767718846734.issue2550678@psf.upfronthosting.co.za> |
2011-07-26 01:36:34 | jerrykan | set | recipients:
+ jerrykan, ber, satchit, ThomasAH |
2011-07-26 01:36:34 | jerrykan | link | issue2550678 messages |
2011-07-26 01:36:34 | jerrykan | create | |
|