- #FIREFOX 40.0.3 NOT RESPONDING MAC OS X#
- #FIREFOX 40.0.3 NOT RESPONDING PATCH#
- #FIREFOX 40.0.3 NOT RESPONDING SOFTWARE#
- #FIREFOX 40.0.3 NOT RESPONDING MAC#
#FIREFOX 40.0.3 NOT RESPONDING MAC#
For FF to be considered a stable release by Mac users, this functionality needs to be restored. There are some workarounds for the keyboard shortcuts being broken (Menu Master is one, but it has a success rate of only 90% every time you go to use a keyboard shortcut), and Quickeys is another.
#FIREFOX 40.0.3 NOT RESPONDING SOFTWARE#
It is frankly one of the fundamental rights of the user to use the software the way he wants, and in my own case I've got a dozen or so keys that I use in Safari a certain way, which I'd like to fix. I'd like to chime in and request that Firefox PLEASE support the OS-based keyboard shortcuts. It can be as simple as some entries in about:config for the menu items that do not currently have keyboard shortcuts on OSX. If you can't fix this, then consider adding a utility (or enabling an add-on) that will allow users to change the keyboard mappings within Firefox. I avoided upgrading to RC1 and RC2 because of this, I'm sure other users will avoid upgrading to FF3 when the final version is released. I don't really care if it's fairly standard or not, but it shouldn't be dismissed too casually.
This is a big feature for OSX users, especially power users like the early adopters of Firefox. Do you know how many 3rd party websites advertise this feature as a workaround for the shortcomings in Firefox and other apps? There are quite a few, but I'm going to avoid saying anything sneaky like "clearly there are more users than you know about, and they're all going to be very annoyed when FF3 launches." Ever seen how fanatical and illogical Mac users can be over something like this? There's nothing "clear" about whether the vast majority of users do or do not use this feature.
#FIREFOX 40.0.3 NOT RESPONDING MAC OS X#
With all due respect Josh, please note that "clearly the vast majority of Mac OS X users don't use that feature." is an even sneakier phrase than "Fairly standard". > particular, so what is "fairly standard" supposed to mean? > users don't use that feature of Mac OS X, even fewer with Gecko apps in > "Fairly standard" is a sneaky phrase - clearly the vast majority of Mac OS X I think we can find a way to make this feature with with XUL apps, I'll keep it in mind when I'm working on further key handling improvements in the next release of Gecko.
The consequences of not fixing that bug were far more severe than this, and it is now even later. If you're trying to advocate the go-ahead for another risky patch, your own statement here is a solid argument against doing so. > included), but that didn't stop us from landing it. > works, very late in the game, and it caused several regressions (this one > I consider bug 398514 a very risky change to the way our key event handling "Fairly standard" is a sneaky phrase - clearly the vast majority of Mac OS X users don't use that feature of Mac OS X, even fewer with Gecko apps in particular, so what is "fairly standard" supposed to mean? Eventually we'll be able to make even more progress and hopefully fix this bug, but we've run out of time for this release.
We finally had to deal with those issues and it was worth it even with consequences like this bug.
#FIREFOX 40.0.3 NOT RESPONDING PATCH#
We had fundamental problems with keyboard event handling from Firefox 1.0 up until the patch for bug 398514 landed. > 398514 made Gecko incompatible with a fairly standard Mac OS X feature. > bug 398514, and won't work fine in Firefox 3 final because the fix in bug > (Firefox 2), worked fine in Cocoa builds (Firefox 3b5) prior to the landing of this feature worked fine in Carbon builds
0 kommentar(er)
