Comment 145 for bug 691380

(In reply to Wayne Mery (:wsmwk) from comment #141)
> Surprisingly I'm pretty much liking the addon. One nit is if I filter on X
> in tab A and then on Y in tab B, that Y is shown in tab A when I go back to
> A. Even though A is still filtered on X.

Well, again, since I don't use tabs, I would never have encountered those issues... most likely Iago can fix them though if you report it to him...

> That said, this bug seems to have gone off the rails, starting in comment
> 115 - 117, and 124. Let me point out that *Blake didn't start this*, and the
> direction wasn't brought back in focus by anyone back then, until ~comment
> 129, that the addon doesn't focus on what you (Charles) want.

Not sure what you mean... the addon totally fulfills this bug request. We - users - are often told that an Addon is a good way to get a feature implemented, because then the code is already written, and thus, the Unified Search Addon was born.

> STM the current addon focused on reunification

No, initially, the Addon focused precisely on fulfilling my original request, as hammered out in the mockups so artfully done by Thomas D. The 'unification' aspect (unifying the Global Search etc) was added *afterwards*...

> and it's conversation should probably go in a different bug. Not that it will
> change the direction of the addon - which seems clear enough to me - but it
> may help get this bug back on topic. How quickly it progresses is a different
> matter.

Again, I don't follow. This addon *totally* fulfills my request, so please I wish you guys would stop telling me that it doesn't - I should know, I made it, and am using (and now totally dependent on), and that is why I'm now asking for the Unified Search addon to be incorporated into the core code (since that would be the last step in fulfilling this bug request).