Custom query has wrong results in Safari 2.0.1

[Blake Ramsdell]

I tried doing a query of the open Trac 0.9 issues using Safari 2.0.1, and the result was much more than that — I got many tickets for milestones other than 0.9.

The link I clicked on was:

​http://projects.edgewall.com/trac/query?status=new&status=assigned&status=reopened&milestone=0.9

Which displays correctly in Firefox 1.0.7 (it currently shows four issues — #2101 #2182 #2106 and #2097).

[blaker@…]

If you need further info, you can contact me by email at blaker@…. It blows my mind that Firefox is right and Safari isn't, but I don't have a good answer. Same machine, side by side windows and they're different.

[anonymous]

On a hunch, I checked my cookies, and there was a trac_session that expired on 1/27/06. I deleted it, restarted Safari, and everything is cool. I have no idea what his problem was, but that fixed it. I imagine this is "invalid", but it might be interesting to see what could cause it. I tend to be a fairly meticulous guy, so I think my environment is under control and that I wasn't making it up.

[Matthew Good]

Were most of the tickets listed shown in grey and italics? In preparation for 0.9 there has been some clean up and postponing of tickets. Trac now saves the results of the last query you ran to make it possible to navigate through the results with "next" and "previous" links and return to back to the same query. When you revisit the query page it will still show any results that matched the query when you last ran it, but greyed to indicate that they don't match the query now. Clicking the "Update" button will clear the results.

[Blake Ramsdell]

You're right — that was probably exactly the case — I do remember that there was a visual style difference between the ones that shouldn't be on the list and the ones that should. Sorry about the alarm.