Krautrock ist verboten

Why is the Can thread locked?

Another blue2blue senior moment?

too many butttons for people over seventy

I also hit the wrong buttons many times per day

Another blue2blue senior moment?

Gotta be. I'll go fix it.

______________

Yep. As I've had to sheepishly explain before, it's because, for some idiotic reason, the tab order in Chrome is different than Firefox -- when you tab out of the edit window, no matter if it's a new post or you've been editing an old one, the cursor jumps to the SAVE button as one would expect.

It's consistent. It makes sense.

But in the sleek but often infuriating and illogical Chrome, when you tab out of the edit window in a NEW post, you end up first on the show-my-signature checkbox and then to the CLOSE THIS THREAD checkbox.

However in EDIT mode, when you tab out of the edit window, you end up first on the show-my-sig button and THEN on the save button. So, with a new post, it's tab-tab-click. But when editing an existing post, it's tab-click.

It's absurd and illogical and completely upside down from what one's procedural memory ('muscle memory') expects -- and, of course, Chrome drives one crazy if he's used to the logical and consistent function of tabbing in Firefox.

Sadly, the latest versions of Firefox slow down and lock up when I use them on this board. (And, yes, I've done a number of strip-outs of all FF registry entries, clean FF installs, etc. It just can't seem to handle this BB (at least on my rig) since the upgrade to 10.x at the start of the year. Though it was *perfect* in version 9.x.

Drives. Me. Nuts.

And... sorry.

Damn, happened again. I actually ended up locking this thread as I posted my explanation above.

AGGGGGGGGGGGGH!!!!!!!!!!!!!!!!

PS... mind you, this doesn't happen at another large audio site that uses this BB software, but that appears to be because their form layout keeps the checkboxes below the Post/Save button.

I suspect that the difference between FF and Chrome behavior is that one follows the tabindex property (which developers can use to control/override tab order) and the other one doesn't. And I'm betting that it's Chrome that's the F-up, there.

(Although they claim full support for tabindex -- but they're always breaking their own capabilities. And -- yep -- as I search around, I see more developers complain about unexpected tabindex behavior in Chrome and having to write tweaky/hacky code to come up with workarounds. And the problems go back TWO YEARS at least... Surprise, surprise. Freakin' Webkit open sore browsers. That's what Google gets for being lazy and adopting Apple's open source Webkit framework that runs the dorky Safari. At least they optimized the code and made Chrome much faster than that POS.)

That's it. You can only use Firefox from now on.

I'd love to be able to go back to using FF -- which is my preferred browser by a stretch (although Chome is fast enough, it's a HUGE RAM hog and, despite the hoo haw BS from its 'developers' (it is, after all, derived from Apple's open sourced Webkit framework -- although it must be recognized that Google hugely improved the speed of rendering by rewriting the JavaScript engine), individual instances of Chrome are NOT completely independent and crashing one window or tab often CAN bring down the rest.

Unfortunately, as noted, since FF 10.x (actually 10.1 is when I first noticed it but I believe I went straight from 9.x to 10.1), FF on my rig has been all but unusable, locking up on javascript-heavy sites (like this one or that of our purplish colleagues over in the UK) -- and major publication and commercial sites.

I've done complete removals, scrubbing the Registry of all references to FF and clean reinstalls -- to no avail.

Still, I'll try again in a while. But after spending DAYS trying to get FF working -- and temporarily hosing up my system so much that I thought I might have to do a clean install of the OS [dodged that bullet, thank heaven], having done multiple R&R's of FF, I just had had it. Due dilligence, up yours. As the punkers might say.

it's always good to download a complete install & stash it somewhere when you have something working & they want to push an upgrade on you.

FF & winamp are prime offenders in punishing you with nags for not upgrading - - but I'm still on FF 3.6 and plan to stay there till they get their collective sh*t together.

if you want to downgrade, PM me & i'll put the FF install file out on a file transfer site for you.

I think I'll start a petition to remove the responsibility of modship from blue2blue. Reason: senility

:lol:

I think I'll start a petition to remove the responsibility of modship from blue2blue. Reason: senility

Nah mate, Blue keeps us on our feet.

Still on 3.6 here as well.