User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:22.214.171.124) Gecko/2010010604 Ubuntu/8.04 (hardy) Firefox/3.0.17 Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:126.96.36.199) Gecko/2010010604 Ubuntu/8.04 (hardy) Firefox/3.0.17 Binary package hint: firefox-3.0 When using the incremental search in the history sidebar, the results are not shown in chronological order, so for many news sites it is impossible to guess which of the many identical labels might be the line we want. When the main display sort order is Chronological shouldn't the search results match? Also, in the search results, there is only the page title, it is not possible to get the date or any other meta-data on the link to help distinguish the link, the only option is to actually load the page and guess from there. ProblemType: Bug Architecture: i386 Date: Wed Jul 23 09:53:09 2008 DistroRelease: Ubuntu 8.04 NonfreeKernelModules: fglrx Package: firefox-3.0 3.0+nobinonly-0ubuntu0.8.04.1 PackageArchitecture: i386 ProcEnviron: PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games LANG=en_CA.UTF-8 SHELL=/bin/bash SourcePackage: firefox-3.0 Uname: Linux 2.6.24-19-rt i686 CancelOk the problem persists in Mozilla/5.0 (X11; U; Linux i686; en-US; rv:188.8.131.52) Gecko/2010010604 Ubuntu/8.04 (hardy) Firefox/3.0.17 and is easy to duplicate Reproducible: Always Steps to Reproduce: 1. Press Ctrl H to see the history; this bug, 251149 will be at the top of the list 2. enter the search string "[Bug" 3. the history list will CLEARLY show the Bug numbers increasing monotonically. Expected Results: search order results need to be in the same chronological order as the original listing
just a note on the reproduce steps: that bug number reflects the Ubuntu bug number; the effect is the same with any history items where the Title contains some historical ID number or date, the plain listings are sorted by date going backwards, the search results are sorted alphabetically. Search results should obey the current sort-order settings.
You need to log in before you can comment on or make changes to this bug.