If one’s back button does not work with Firefox try this to gather more information: right click on ‘back’ and see if the proper history drops down. If the proper history drops down click on a previous item and see if the correct screen appears.
The reason I suggest his is that on a large group of forums, gardenweb.com, the single click on ‘back’ stopped working for Firefox only but the drop down history could be used to effect backness, as it were. It took them a long time to diagnose and fix the problem, but then they are, to put it kindly, quite slow.
A problem we didn’t create? A problem we cannot duplicate in our own experience?
I told you what we had, what we knew, and I asked for more information.
No, that’s your assertion. That’s not what I said.
Why is it that any negative technical outcome you have here at this website is our responsibility and our problem, regardless of the situation? To personalize it and yell at me because I don’t have an answer or a solution to this problem is inappropriate.
While we do want to help people have the best experience they can here and will facilitate as we can, moderators and administrators are not and cannot be expected to be tech support. This goes double for software with hacks in it like browsers with plug-ins – that’s what most all those things are, they’re hacks to the existing software and have no guarantees.
None of us are in technical positions at any of the software companies involved.
I gave you the information I had and I asked for help from those who are more experienced users of the browser originally in question. Again, we are not tech support and should not be expected to be so. I’m glad Xash was able to contribute a bit more to the situation but I note even he could not diagnose nor fix the problem.
Hyperbole much?
The staff here – including myself – do our best to make this work. It’s a greatly imperfect universe, filled with buggy software and bad code, and we do what we can with what we know and have available to us.
Now how about we stop hijacking this thread and get back to the issue, if indeed a solution can be found?
No, but you’re wrong. It is browser specific. Servers don’t control things like pressing back buttons (unless they’re running dot net, which this one is not.) Browsers control things like that.
That’s why there’s no problem with IE8. The back button always works because the browser is programmed to go back a page when the back button is pressed. Someone mentioned a known bug in Firefox. IE8 has its share of bugs, but that’s not one of them.
As to Tuba’s dismissive tone, that’s just Tuba. She waddles into topics like these, not understanding the first thing about them, and goes on auto-pilot with the dismissals. It’s just the nature of thing. We have to learn to live with it.
So if I may piggyback my problem on this, what could be causing that? Still getting an error screen much of the time, both when I press Submit for a post and just to open a thread. Back up and and repeat, then it works. This includes for posts.
Sometimes I try Refresh instead of Back and get just a blank screen. I then use Back once to get to the error screen and again to get to the previous screen. I use IE.
FWIW, it doesn’t seem to be happening anymore…at least, not right now and not for the last couple days, not on any of my home computers nor my work one.
Perhaps the Gremlins are aware that I, too, have a multimeter nearby, and I’m not afraid to use it!
A little more data:
A recent firefox tab with this problem (on the GQ threads page) showed 2 entries in the cache for the page (checked by right clicking the back arrow) despite the fact that I had just opened the tab, went to my SDMB Main bookmark and then clicked GQ once.
I immediately opened another tab, did the same thing and no dup cache entry.
When I clicked the back arrow on the bad tab, I noticed that it did appear to go back temporarily because you can see the forward arrow change from grey to green, then it would flip back to the same page and state (forward arrow back to grey). In addition, if you click back fast enough twice it makes it back, if you click back too slowly, it has moved forward again before being able to click the second time.
I heartily recommend that you download and install IE8, along with its patches. There are far more security enhancements, including the ability to “browse privately”, such that cookie co-ops can’t follow you around from site to site. It is also more stable than IE7.
Confirmed. My infraction was the use of the term “waddle”, which upon a search reveals more than 300 posts (the number our search engine would allow to be returned) that use the term.
Admittedly, it was interpretable in the way Rico did. But I probably should have phrased it more like this: “TubaDiva drops into threads like this knowing nothing about the topic, and responding with dismissal.”
Yes, calling someone rude and unhelpful is a personal insult – now and always in the past. This is nothing different or new.
ACCEPTABLE: What you said was rude and unhelpful.
NOT ACCEPTABLE: You are rude and unhelpful.
The first is about the moderation decision or the post. The second is about the person. This distinction has ALWAYS been our standard. The discussion should be about the what the poster says, not about the poster her/himself. In the same way, the discussion should be about what the moderator says/does and not about the moderator him/herself.
I assume there was an implication that the term has been used many times in the past, but not warned. I did look at usage over last two months (we do take every accusation seriously), and the term has been used (1) by a poster, referring to himself/family after Thanksgiving dinner, (2) to refer to pregnant women in general, (3) to compare people who wear their pants lwo to penguins, (4) to describe sumo wrestlers. So, the fact that a word has been used often on the boards doesn’t mean it’s not an insult when applied to another poster.
And, of course, the context here is more than just the walking motion.
