News for hackers. Stuff that matters.
Re:Firefox on Mac textarea edit bug open since 2005 by thought_alarm on Wednesday August 31, 2011 @10:44PM (#2948450)
The real problem is that Mozilla lacks a Mac OS X usability advocate with the authority to expedite sensible solutions to these kinds of problems.

As we all know, the standard OS X shortcut for moving backward and forward is Cmd+[ and Cmd+]. The Cmd+Left/Right shortcut for moving backward/forward is decade-old cruft (even though Safari still conditionally supports it).

If the Mozilla platform cannot handle supporting this cruft on top of the standard Cmd+Left/Right text editing behavior, then at the very least remove the cruft. Instead, the problem is allowed to linger for years and years as people bicker back and forth about what to do about it. That shouldn't be acceptable to anyone.

Re:Firefox on Mac textarea edit bug open since 2005 by ugh on Wednesday August 31, 2011 @11:26PM (#2948540)
You mean the standard OS X shortcuts if you use a US keyboard, right? The shortcuts on a German keyboard (which does not have [ and ] keys) for back and forward are Shift-Cmd-Ö and Shif-Cmd-Ä (that’s using Safari), clearly inferior to Cmd-Left and Cmd-Right.

Cmd-Left and Cmd-Right are necessary.

(Google Chrome has actually Cmd-[ and Cmd-] as back and forward even with my German keyboard layout – which is quite dumb and shows that they don’t seem to care much for localization. Cmd-[ translates to Alt-Cmd-5 on a German keyboard.)

Re:Firefox on Mac textarea edit bug open since 2005 by silverlight on Thursday September 01, 2011 @09:31AM (#2949936)
You know it's an open source project and you could go ahead and add code yourself to support a more sensible shortcut on German keyboards, right?

The sense of entitlement when it comes to something created and used freely, solely for the purpose of making the world better, sometimes simply astounds me.

Re:Firefox on Mac textarea edit bug open since 2005 by ugh on Thursday September 01, 2011 @09:38AM (#2949966)
I can’t, actually, I’m not a developer, but that’s very much besides the point.

I don’t think something should be protected from criticism just because it’s free. Just because it’s open source doesn’t mean I have to try to fix it before I’m allowed to criticize it. I can simply recognize shoddy workmanship and move on.