[#7935] use of file name filters might result incorrect empty result page
Summary use of file name filters might result incorrect empty result page
Queue Gollem
Queue Version 1.1-RC1
Type Bug
State Resolved
Priority 1. Low
Owners Jan Schneider <jan (at) horde (dot) org>
Requester leena (dot) heino (at) uta (dot) fi
Created 02/02/09 (404 days ago)
Due
Updated 03/19/09 (359 days ago)
Assigned 02/02/09 (404 days ago)
Resolved 03/19/09 (359 days ago)
Attachments
Milestone
Patch No

History
03/19/09 Jan Schneider Assigned to Jan Schneider
Taken from Horde DevelopersHorde Developers
State ⇒ Resolved
 
03/19/09 CVS Commit Comment #2 Reply to this comment
02/02/09 Chuck Hagenbuch State ⇒ Assigned
Assigned to Horde DevelopersHorde Developers
 
02/02/09 leena (dot) heino (at) uta (dot) fi Comment #1
State ⇒ Unconfirmed
Patch ⇒
Milestone ⇒
Queue ⇒ Gollem
Summary ⇒ use of file name filters might result incorrect empty result page
Type ⇒ Bug
Priority ⇒ 1. Low
Reply to this comment
You can recreate a problem like this:

1. Open a directory that has so many files that the directory listing 
has to be split into different pages.

2. Go to last page eg. page 5

3. Set file name filter to show eg. files beginning with a.

4. The filter result page is opened to page 5. If the filter results 
page can be fit in only page then the user sees an empty results page 
number 5.



What user expected to happen:

Show the first page of filter results, not the page number that user 
happened to be browsing in the original directory listing.