After using the new FireFox 3 for a few days, I realized what I thought was a change in features was actually FireFox not recognizing the Colemak layout for Command shortcuts. For example, creating a new tab by Cmd-T using the Cm position gets no response (I now realize it it goes to the find box). To create a new tab, you have to use the Qwerty position for T.
It all worked fine with FireFox 2.
anybody else notice this?
No, works for me. That's with Firefox 3.0 on Mac OS X 10.5.3 with the Colemak.keylayout in /Library/Keyboard Layouts.
(I do have said problem in Eclipse, though - when the command key is pressed, the app responds to QWERTY key locations)
I am using FireFox 3.0 on Mac OS X 10.4.11
I am not ready for 10.5 yet. what a pain if that is the reason.
I am using FireFox 3.0 on Mac OS X 10.4.11
I am not ready for 10.5 yet. what a pain if that is the reason.
Confirm that is indeed the reason. Firefox's Cmd-keys stay Colemak on Leopard but revert to Qwerty on Tiger. (The latest versions of other browsers seem to be fine on Tiger. You may want to try Camino, which seems to be the browser least different from Firefox. By the way: it is Firefox, not FireFox: Save your fingers from at least one shift-press, thereby boosting your wpm. :-)
I use Camino, Opera, and Shiira but I keep coming back to Safari and Firefox. The fact that I still had 1.5.4 instead 1.6.1 demonstrates that Camino hasn't been a habit lately. Nice that it doesn't screw up the layout though.
As for where I unconsciously use caps :-P
I'm having the exact same issue: OS X 10.4.11, and FF 3.0.1. Anyone know if a bug report has been given to Mozilla? This would not be my favorite reason to change browsers and/or OS. :-(
Thanks!
Ah yes..."good" news...two bugs submitted:
https://bugzilla.mozilla.org/show_bug.cgi?id=439815
https://bugzilla.mozilla.org/show_bug.cgi?id=435375
Now we just need some smart cookie to fix 'em!
Here's hoping.
This issue is now resolved for me. I assume an update to Firefox fixed it.
Bug fixed in Firefox trunk.
I am updated to FF 3.5.3 but the problem is still occurring - anyone have any tips on how they fixed it?
I still have the same problem with FF 3.5.x latest as well.
Seems the only fix is to upgrade to Leopard or Snow Leopard.
