Interesting! I had never noticed this before. After a little experimenting, I see what's going on.
When you perform a search, it sorts the results (the entire result set) by relevance by default, and then displays the thumbs in the appropriate number of pages based on your preferences (rows per page). When you select one of the other 2 sort options (Oldest First, Newest First), it does the exact same thing first (pull results, sort by relevance, put in pages), then it sorts each page by Oldest First or Newest First.
It's doing exactly what it's coded to do I would imagine, but it's certainly not what you or I would expect it to do.
I had never noticed before because I have my rows per page set to 100, and no image search I've ever done has exceeded 1 page. Thus, I get the full results re-sorted by my choice (oldest or newest) correctly for the full result set.
I think web site suggestions is a good place for this thread! I would think it would be relatively easy for Langdon to change the code to get the expected behavior instead of the current weirdness. |
