On 01/03/15 04:08, David C. Rankin wrote:
On 02/28/2015 06:15 PM, Peter wrote:
I started seeing this a while back too. My second thought (my most immediate thought was 'bollocks') was that perhaps this was a deliberate change, given that Startpage is supposed to present results unbiased from other sources, i.e. maybe you'd want to see 'fresh' results rather than ones that are reliant on a previous search. Maybe it's just a (over-zealous) security setting? I doubt that's the case, but it did cross my mind.
And although it would seem likely that it's Firefox that changed something since it occurs with one version and not another, I guess it's also possible that the problem exists in the way Startpage has coded the page, and that it only manifests itself in the latest FF version.
Anyway, here's an bug that relates to it: https://bugzilla.mozilla.org/show_bug.cgi?id=1060082 which is also linked from https://bugzilla.mozilla.org/show_bug.cgi?id=1065234
Peter
It is another Mozilla gift. I found another couple of threads on it. See:
https://support.mozilla.org/questions/1047023 https://support.mozilla.org/en-US/questions/1010942
It does seem that there was a change, and true-to-form, there seems to be nothing provided that lets you select/configure this behavior to regain traditional operations.
1010942 mentions Tools->Options->Override Automatic Cache Management, but this must be a windows or dev option as it is not present in FF35. I have also searched about:config for 'override', 'cache', 'management', etc.. but have not found a probable match.
I'll keep looking. If devs would just remember that the new gee-whiz way they want to do it, might not be the way everybody wants to do it, there would be far fewer issues and complaints. I'm all for new features. But a 'new feature' to one is a horrible inconvenience to someone else. Linux has traditionally been about user choice, and it has been furthered by providing user-options to configure things as they like. The old adage that: "a new feature is a bug if it cannot be turned off" still rings true.
Don't get me wrong, I'm a mozilla supporter and user since 0.x or 1.x days, but since this silly version race from 3.x -> now version 35+ has taken place, it seems like the new crop of devs have completely forgotten these lessons.
Thanks for your help, I'll keep digging and if I find a solution, I'll post it here.
Not a solution but a simple workaround. It may run against your preferred 'workflow' but you could right-click links on search results pages to open in a new tab, or just drag them to an empty part of the tab bar. I find myself increasingly doing that in various search engines because for one reason or another, going back presents annoying quirks. Not just the Startpage issue you bring up, but on DuckDuckGo for example I kept finding that it would skip back to an irrelevant part higher up the results page and I'd have to scroll back down. Another search engine, I forget which, had an irritating delay in page load when navigating back. From time to time you also run into that pitiful design of some miserable web developers worthy of a good chainsaw unboxing whereby clicking Back automatically redirects to the current page and tries to lock you in. Being able to just close a tab, or switch back to the results still open in another tab, seems more useful to me a lot of the time. Peter -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org