mirror of
https://github.com/mozilla/gecko-dev.git
synced 2025-01-14 05:44:20 +00:00
723a77ddea
======== https://hg.mozilla.org/integration/gaia-central/rev/0cc496fad27f Author: Min-Zhong "John" Lu <jlu@mozilla.com> Desc: Merge pull request #25840 from mnjul/bug_1093537_input_window_management_from_kbm Bug 1093537 - Move input app window management-related responsibility from KeyboardManager to InputWindowManager. r=alive,timdream,rudyl ======== https://hg.mozilla.org/integration/gaia-central/rev/ddb84c2ad293 Author: John Lu [:mnjul] <jlu@mozilla.com> Desc: Bug 1093537 - Move input app window management-related responsibility from KeyboardManager to InputWindowManager - A lot of events that only affects inputWindow showing/hiding goes to InputWindowManager instead of KeyboardManager now. - "RemoveKeyboard" concept is now separated: -- InputWindowManager._onInputLayoutsRemoved() is called by KeyboardManager to signify that some keyboard layouts have been removed (disabled from system settings, or uninstalled keyboard app). IWM will remove InputWindow references accordingly. -- KeyboardManager._onKeyboardKilled() is called by InputWindowManager to signify that a loaded and currently showing out-of-process keyboard has been OOM'killed. KeyboardManager has to determine a keyboard layout to relaunch. - A closed InputWindow now has height 0 instead of undefined. - Please use inputWindowManager.hideInputWindow()/.hideInputWindowImmediately()/.getHeight() in place of KeyboardManager.hideKeyboard()/.hideKeyboardImmediately/.getHeight(). - inputWindowManager is a singleton and accessible in the window scope. - KeyboardManager had lacked tests about getting device memory and retrieving setting of enabledness of 3rd-party keyboard, which have been added (to InputWindowManager) in this test. Additionally, KeyboardManager.updateLayouts() is tested now (although only roughly).
An explanation of the Mozilla Source Code Directory Structure and links to
project pages with documentation can be found at:
https://developer.mozilla.org/en/Mozilla_Source_Code_Directory_Structure
For information on how to build Mozilla from the source code, see:
http://developer.mozilla.org/en/docs/Build_Documentation
To have your bug fix / feature added to Mozilla, you should create a patch and
submit it to Bugzilla (https://bugzilla.mozilla.org). Instructions are at:
http://developer.mozilla.org/en/docs/Creating_a_patch
http://developer.mozilla.org/en/docs/Getting_your_patch_in_the_tree
If you have a question about developing Mozilla, and can't find the solution
on http://developer.mozilla.org, you can try asking your question in a
mozilla.* Usenet group, or on IRC at irc.mozilla.org. [The Mozilla news groups
are accessible on Google Groups, or news.mozilla.org with a NNTP reader.]
You can download nightly development builds from the Mozilla FTP server.
Keep in mind that nightly builds, which are used by Mozilla developers for
testing, may be buggy. Firefox nightlies, for example, can be found at:
ftp://ftp.mozilla.org/pub/firefox/nightly/latest-trunk/
- or -
http://nightly.mozilla.org/