Firefox 25.0.1 in OSX 10.7.5 forces use of default input source, why?
Hi,
I have not noticed this in previous versions of Firefox, but under OSX 10.7.5 version 25.0.1 forces the use of the default input source (e.g. my laptop's keyboard, instead of the attached external keyboard).
All other input devices are greyed out in the Language & Input toolbar drop down when the Firefox application is in focus. This does not happen with any other application on my desktop.
I believe this is the issue relates to this thread also:
https://support.mozilla.org/en-US/questions/977966?esab=a&as=aaq
Cheers,
Sunkai.
Выбранное решение
Okay, this is a broader issue to do with whether the keyboard drivers that are installed are compatible with both 32-bit and 64-bit applications.
Firefox starts in 64-bit mode under OSX by default, and if your keyboard drivers are 32-bit only, then that input source is not usable and is greyed out.
Discussion of this for British layouts can be found here:
http://www.gyford.com/phil/writing/2005/11/20/using_a_british.php#c285152
64-bit British layout drivers can be sourced from here:
http://liyang.hu/osx-british.xhtml
If you are having problems with your own keyboard, with another country's layout, then you will need to find 64-bit drivers for that layout.
Прочитайте этот ответ в контексте 👍 2Все ответы (2)
Выбранное решение
Okay, this is a broader issue to do with whether the keyboard drivers that are installed are compatible with both 32-bit and 64-bit applications.
Firefox starts in 64-bit mode under OSX by default, and if your keyboard drivers are 32-bit only, then that input source is not usable and is greyed out.
Discussion of this for British layouts can be found here:
http://www.gyford.com/phil/writing/2005/11/20/using_a_british.php#c285152
64-bit British layout drivers can be sourced from here:
http://liyang.hu/osx-british.xhtml
If you are having problems with your own keyboard, with another country's layout, then you will need to find 64-bit drivers for that layout.
Sunkai, thank you! After reading your response and the previous threads, I changed Firefox to 32-bit mode and the problem appears to have been resolved. What a relief!