Comment 1 for bug 1457698

Discussed this with Chris. Problem is real. Basically, the Nearby Scope fires more than one query at a particular child, but with different department, or potentially different query string and/or filter settings. Doing this is quite legit. The loop detection is too stringent right now because it axes off any query that loops around, regardless of whether the query details are the same or not.

We need to change the loop detection to take all of the query state into account. That way, queries that differ in some detail will still be forwarded to children, but queries that loop around unchanged and therefore indicate a real accidental loop are still axed.