To be honest, I think you overreact a little.The behaviour of substituting TAB-queries by '?' queries might very well be older than v3.1, but there is one huge difference between this last release and the previous one: now, one *must* use the buggy in-line search query form (because that's the only thing that shows up when clicking on a type 7 query), while in the previous release I never used it, since clicking on a type 7 query triggered a popup window that worked fine (with the exception maybe that at some point it started asking twice for searches, but that was not a major trouble).
The simple truth is that the current Overbite version is unusable, while the previous one was mostly fine. I can only suggest that instead of getting angry at the entire world, you should try testing your own software before releasing something that doesn't work.
As of right now, I reverted from 3.1.1684 to 3.0.1627.1-signed, and search queries work again, so I will stay like that.
Mateusz On 09/01/2016 21:08, Cameron Kaiser wrote:
Okay, I'm officially p*ssed off. This has been the case since inline views were introduced *three years ago*. If you pop an inline query window, that's what it's done ever since 3.0. Where were the reports then?? While I acknowledge the bug, you're going to have to deal, since the fix is going to be substantially more complicated than I can do in a point release, and Mozilla has (surprisingly) already approved the update. I'm not really interested in shipping a minor change to revert the old behaviour when the current behaviour had been shipped for quite some time if people had bothered to check *and* OverbiteFF isn't the only client that does this (some old browser versions do too, which is why Bucktooth has specific code to check for that circumstance).
_______________________________________________ Gopher-Project mailing list Gopher-Project@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/gopher-project