summaryrefslogtreecommitdiff
path: root/java/src/com
Commit message (Collapse)AuthorAgeFilesLines
* Implement text entry key API for accessibility services in AOSP Keyboardryanlwlin2020-05-253-16/+4
| | | | | | | | | | | | | | | | | | | From Android Q, Talkback supports lift-to-type feature if the node claims it is a text entry key via setTextEntryKey(). We implement this API to show how this API is applied. This CL uses AccessibilityNodeInfoCompat instead of AccessibilityNodeInfo so that the same functionality can be used even on pre-Q devices when the AccessibilityService supports it. With that, this CL removes the legacy code of lift-to-type feature, which was implemented in the AOSP Keyboard side. Bug: 131644969 Test: manual - enable Talkback suporting lift-to-type,check Talback perform click action when finger is lifted. Change-Id: I1ec2928f5a9ba0bde999b09d4c0b9c922f179a2a
* Create display context when switching IME to new display for AOSP IMElumark2020-05-252-9/+42
| | | | | | | | | | | | | | | | | | | | To address IME service context's Resources / DisplayMetrics update when switching IME window to another display after onConfigurationChange. We use Context#createDisplayContext to create display specific context when display changed, to ensure soft keyboard can re-layout with correct resources. Bug: 126930163 Test: manual with AOSP IME as below steps: 1) Settings > Developer options > enable "Simulated Display" & "Force desktop mode". 2) Reboot device 3) Launch app (i.e. Contacts) with bluetooth or usb mouse in Simulated display. 4) Tap EditText on app to see see if IME window layout correctly on simulated display. 5) Launch app (i.e Files) on primary display. 6) Tap EditText on app to see if IME window layout correctly on primary display. Change-Id: I0ed6a079af1ed90c75fee1d36d5ce3ef3c41f8ed Merged-In: I0ed6a079af1ed90c75fee1d36d5ce3ef3c41f8ed
* LatinIME: Fix back-arrow finishing activityMichael W2020-05-253-4/+12
| | | | | | | | | | | | | | | | | | | | | | * When going to a sub setting menu and pressing the action bar up arrow instead of the device's back key, the settings are closed instead of going one level up as expected * Call "onBackPressed" instead of "finish" to fix that * For InputMethodSettings create a new flag to alter the behaviour for our use case but to keep existing behaviour for other callers Test: - Open the keyboard settings from Settings app and navigate between menus -> action bar back icon only goes one levelup - Open keyboard settings directly from keyboard: behaviour is the same, last "up" action takes you back to where you came from Change-Id: I4f01e80e7f35ddbd2af1baae899d689f1144a5a1
* LatinIME: Remove dividers everywhereMichael W2020-05-256-17/+46
| | | | | | | | | | | * Instead of removing the dividers per fragment, create a custom fragment which does the job Test: * Go to every setting and verify that there are no divider lines between every preference Change-Id: Id76dfa2e3ce3999242c8dd09a531ab06ccacd203
* LatinIME: Remove divider linesMichael W2020-05-182-0/+24
| | | | | | | | * In order to make it look less like it doesn't belong to settings, remove the divider lines that are currently everywhere Change-Id: Ie4a2db64517280da28ac0159390b587a748e95b4
* LatinIME: Do we really still want Holo?Michael W2020-05-181-44/+1
| | | | | | * Remove Holo keyboard selection Change-Id: I2a67bc147afd9f5c86f0c723eda70083891707cd
* LatinIME: Add setting for theme to follow system settingMichael W2020-05-182-22/+42
| | | | | | | | | * Add a setting to follow the system design (light/dark) * Make it default for >= Q * Rework the handling to differentiate between selected theme (by id) and actual theme we use Change-Id: I380e3540b2437102685aa632c5b0a2f2dff11e1b
* LatinIME: Add Luxembourgish keyboard & spellchecking dictionaryMichel Weimerskirch2019-12-111-193/+239
| | | | Change-Id: Ie53bcb49b568a44a7bdcc8c7437d9981062487b6
* LatinIME: HU enable predictive dictionary and remove unused lettersTamás Tóth2019-12-111-32/+5
| | | | Change-Id: I6658bae54793c59b3c0839edda6933950920185e
* LatinIME: Enable spellchecker for additional languagesblunden2019-12-111-1/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | We include more dictionaries than stock builds so let's also enable spell checking for languages that use only the supported unicode characters. Change-Id: Iff9aea56edde10e47a754df39682f4f72c269756 LatinIME: Enable Greek spell checking * We already ship a dictionary for Greek Change-Id: I99ee7c98a88515c4c69b654210c10696135d7560 Add support for Ukrainian spell checking Change-Id: Ie8a39c9206ec1a2e4cccc43d77890abe00080747 Add support for Polish spell checking * The script type for Polish is Latin, so no need to add it to ScriptUtils Change-Id: I5203c56858912ea53bc6069e23fa136af60361bf Add support for Czech spell checking * Czech script type is Latin so no need to add it in ScriptUtils Change-Id: I62085658ff7f7bbbca79e9895d57f1adb48592d4 Add support for Croatian spell checking * The script type for Croatian is Latin, so no need to add it to ScriptUtils Change-Id: I057ba38adf705e62b16ee9e2d2aa7d46bf3b865f Add support for Hebrew spell checking * Hebrew type is already declared in ScriptUtils Change-Id: Id420c256b298d9692d8c415dfc75bd4d3116ca29 Add support for Portuguese spell checking * Script type for Portuguese (Portugal) is Latin so no need to add it in ScriptUtils Change-Id: I2955f267a1f7d81b9180cf4c53718f72724f782d Add support for Bulgarian spell checking Change-Id: I9ff3c73979e68a7a11a657aa6e83769da6607115 Add support for Georgian spell checking * Georgian script type is already defined in ScriptUtils Change-Id: I7e1eb3e985aa44903baed918f58bb6aaace15147 Add in spellchecker.xml support for en_AU, lt, lv, nl, ro, sl, sr, tr Settings for missing dictionaries in menu. Now the xml file have the same amount of 32 (+hu_zz) languages as all .dict files. https://github.com/LineageOS/android_vendor_lineage/tree/lineage-16.0/overlay/dictionaries/packages/inputmethods/LatinIME/java/res/raw https://github.com/LineageOS/android_packages_inputmethods_LatinIME/tree/lineage-16.0/java/res/raw Change-Id: I9fa6245f57a0976d96e0dab37c2e25ef1180e899 Change-Id: I425f0163cd0b34917d6041d75c0e244526ddc268
* LatinIME: Set proper keyboard for Georgian scriptVasyl Gello2019-12-111-0/+2
| | | | | | | Fixes the runtime exception 'Wrong script supplied: 5' Change-Id: Id4f244f7e229532998e846a8d41749d90f7913bd Signed-Off-By: Vasyl Gello <vasek.gello@gmail.com>
* LatinIME: Add new type for Bulgarian scriptVasyl Gello2019-12-112-0/+4
| | | | | | | | Declaring the script type as Cyrillic leads to usage of 'east_slavic' template, which is incorrect for Bulgarian layout. Signed-Off-By: Vasyl Gello <vasek.gello@gmail.com> Change-Id: Ieec27701367f00c4b5e345cee7bf387f923da8f1
* LatinIME: Add shortcuts supportJanet Sun2019-12-116-23/+97
| | | | | | | | | | | Making sure to include unit test changes this time. Adjust for deleted files and delete references to them. This reverts commit fe674a441f0ece3d772acba01be09a0a0d8ff5ce, "am 12d80ebe: Remove shortcut support from LatinIME." Ticket-Id: CYNGNOS-3129, CYNGNOS-3267 Change-Id: I136e307f93445b353e0d798284fd0fbaee61c0d9
* Don't interrupt active gesture input by modifier key presses.Danny Baumann2019-12-111-3/+8
| | | | | | They're likely to be caused by palm touches. Change-Id: Ic1e0b86c5bf5d4c22f888f0bb77342584e45763e
* LatinIME: Add fallback loader for JNI libSteve Kondik2019-12-114-3/+21
| | | | | | | | | | | | | | | | | | | | | | Prefer the JNI lib with gesture typing support. If not available / installed fall back to the standard one without geture typing. Change-Id: I70a5f43386a9c72809a70bd286f3702378d6f9be LatinIME: Only enable gesture mode if gesture lib is available * Prevents keyboard FC when gapps is not loaded. Change-Id: I0d48e1cd80534513205f61913c798b48573ea38c LatinIME: Remove gesture preference if gesture lib is unavailable Gesture typing won't work without the gesture library, so remove the preference to not mislead users into thinking that gesture typing is supported. Change-Id: I387ae83fd174b57fc48fe7bcfc37e3010ce89b12
* LatinIME: Regenerate KeyboardTextsTableMichael Bestas2019-12-111-0/+36
| | | | | | * Add Burmese Change-Id: I650fdac232bb1aa6c35798e782edaa2ab829c5fc
* LatinIME: support for incognito modeJoey2019-12-112-1/+6
| | | | | | | | Don't learn suggestions when input specifies the IME_FLAG_NO_PERSONALIZED_LEARNING flag Change-Id: I224c36deda560657996cffa2922392a64e45b53f Signed-off-by: Joey <joey@lineageos.org>
* Fix send button not being centered for non-standard densities.Danny Baumann2019-12-111-10/+3
| | | | Change-Id: I6e6717dc7487eeafca121e94d93aff5c3aae5f6c
* Remove extend touchable region for AOSP keyboardlumark2019-12-111-4/+1
| | | | | | | | | | | | | | | Remove EXTENDED_TOUCHABLE_REGION_HEIGHT from LatinIME#onComputeInsets to prevent keyboard touch region covered navigation bar when in split-window mode with display density < 240 case. Fix: 134893742 Test: manual as below steps: 1) Set window density as 240 with "adb shell wm density 240" 2) Launch a app (i.e. Messages) from recents activity, set as split-screen mode. 3) Tap Search bar to show IME keyboard. 4) Press home / back / recents key if it works, expect it works. Change-Id: I596b7276041fecc50d2bc095c7e51664f632368d
* Launch AOSP Keyboard Settings on the same displayYohei Yukawa2019-05-041-2/+19
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This CL demonstrates how an IME can show an Activity on the display where the IME is shown. The key points are: * The current display ID can be obtained as follows. final int curentDisplayId = inputMethodService .getSystemService(WindowManager.class) .getDefaultDisplay() .getDisplayId(); * When launching an Activity, specify the target display ID as follows. inputMethodService.startActivity(intent, ActivityOptions .makeBasic() .setLaunchDisplayId(curentDisplayId) .toBundle()); Fix: 131718879 Test: Manually verified as follows. 1. Build aosp_blueline-userdebug and flash it. 2. adb shell settings put global force_desktop_mode_on_external_displays 1 3. adb shell settings put global overlay_display_devices 1920x1080/320 4. adb reboot 5. With a mouse, launch any application that has input field in the secondary display. 6. Click that input field to bring up AOSP Keyboard. 7. Long click the comma key then select the gear icon. 8. Select "Android Keyboard Settings (AOSP)" 9. Make sure that the AOSP Keyboard Settings is launched in the secondary display, not in the default display. 10. Go back to the step 7. 11. Select "Languages" 12. Subtype Enabler for AOSP Keyboard is shown in the secondary display, not in the default display. Change-Id: I9f89f371c38d9a7b5a06d018d4b41aa09815ea24
* Merge "Fix dicttool build" am: a92d0f9262 am: 438a303732Tadashi G. Takaoka2018-10-311-0/+3
|\ | | | | | | | | | | am: 6aed05232b Change-Id: I558fb5ff22a7428d1d82eac82b4caba469ed48d4
| * Fix dicttool buildTadashi G. Takaoka2018-10-291-0/+3
| | | | | | | | | | | | | | | | | | | | | | | | This CL partially reverts - Id88b02b74bdfe4ca05b08181ceb6b34d5652fc0c - I05c7d8429e8d9a26139456763c77997340fea8c2 And followup (remove shortcut support) - I73b7dc008a5acaf75a31a36a2d332b5afabd82d0 Bug: 28255684 Test: make -j10 dicttool_aosp Change-Id: I2e01ed86b9517a1141aee35ea6d8ef39258981d1
* | Remove unused class PersonalDictionaryLookupYohei Yukawa2018-07-041-651/+0
| | | | | | | | | | | | | | | | | | | | | | | | PersonalDictionaryLookup has never been used. Usually proguard can remove this class but it also makes it difficult to run unit tests. We should just remove this unused class. Bug: 111164993 Test: compile Test: No new test failure Change-Id: I732db94cb3aac4ed9c6b5954679b896334a12a9c
* | Merge inputmethodcommon into LatinIME repoYohei Yukawa2018-06-244-0/+431
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This is a preparation to deprecate frameworks/opt/inputmethodcommon repository. Currently repository 'inputmethodcommon' is used only from LatinIME. Having such a repository only for one project is overkill. Also, to add gradle build support to LatinIME project, it would be much easier LatinIME didn't have such a dependency. This CL mechanically copies files in 'inputmethodcommon' repository to 'LatinIME' repository. In theory there should be no behavior change. Bug: 110741521 Test: tapas LatinIME && make -j Change-Id: I3fabb038be9a944dcd9ef79ffcc89800a5f0bf5a
* | Migrated various apps under packages/inputmethods/LatinIME/ to androidxvineel sadineni2018-05-1517-26/+26
| | | | | | | | | | | | Bug: 76692459 Test: mmma packages/inputmethods/LatinIME/ Change-Id: Ib76af6f6db1a0dd5cf64a06a4ea56151712e9692
* | Merge java-overridable/ into java/ againYohei Yukawa2018-05-0620-0/+940
|/ | | | | | | | | | | | | | | This CL a logical revert of a previous CL [1], which separated Java files into common ones and overridable ones. Now that that overriding concept is no longer used, there is no need to keep having separate directory structure. [1]: Ic734bd4d20aa050c688a3158b1a382ae0ac18991 fb74ab15c1343084740d65ef8744cad33a678e82 Fix: 79323502 Test: make -j aosp_taimen-userdebug && make -j Test: tapas LatinIME && make -j Change-Id: I2090bc25d18e6d4f24e91c2cbfe832755cbb4e8f
* Introduce a custom intent action to close software keyboardYohei Yukawa2017-09-011-0/+37
| | | | | | | | | | | | | | | | | | | | | This CL introduces a custom intent action for apps to ask AOSP Keyboard to close its software keyboard with guarding it with a signature-protected permission. Any app that is signed with the same signature as AOSP Keyboard can have the following line in AndroidManifest.xml <uses-permission android:name="com.android.inputmethod.latin.HIDE_SOFT_INPUT"/> to request AOSP Keyboard to close its software keyboard as follows. sendBroadcast(new Intent("com.android.inputmethod.latin.HIDE_SOFT_INPUT") .setPackage("com.android.inputmethod.latin")); Test: Manually verified with a test app. Fixes: 65270710 Change-Id: I4fd2e3a7336ec66c70582a2f274a200cbf035a7f
* Follow class package change: LocaleList am: 156139edd8 am: 03a540cc3aYohei Yukawa2016-05-181-1/+1
|\ | | | | | | | | | | | | | | | | am: 947cc7d7cd * commit '947cc7d7cd32417c016ef474889ed93114395c4e': Follow class package change: LocaleList Change-Id: I7e665d609267182bcfcf11e3fb309dbe9d02c830
| * Follow class package change: LocaleListYohei Yukawa2016-05-171-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | In order to avoid layering violation, LocaleList needs to be moved from android.util package to android.os package [1]. This CL follows up that package change. No behavior change is intended. [1]: Ia8de2ee9df3dd0a42b1fe84574439519b680fe18 Bug: 28819696 Change-Id: Ie795c191e299358c7c463693823f309ce61cc985
* | Calling getClass on a class will return Class.class.Ian Rogers2016-05-091-2/+2
|/ | | | | | | | Bug introduced in 5ac4638f999db4fea8a9e24171dbceb640a10858. Bug found by error prone: Bug: 27723540 Change-Id: I4325f3bc1f1186bd24d4b0074f0c573cc5cb4e31
* Start full screen mode on first tap when HW keyborad is connected.Keisuke Kuroyanagi2016-03-151-1/+1
| | | | | | | | | | | | | | | | | | | | LatinIME checks hardware keyboard presence and software keyboard visibility to decide whether to start full screen mode. This doesn't work well with the recent update on "Show input method" (Bug: 22517687, Id4d332e3909590c68345e). On the first tap, software keyboard is not shown and hardware keyboard is connected; so full screen mode is not started. However, onEvaluateInputViewShown may return true ant software keyboard may be brought up. In this care, on the second tap, software keyboard is visible so full screen mode will be started regardless of hardware keyboard presence. This CL checks onEvaluateInputViewShown to decide whether to start full screen mode. Bug: 27234709 Change-Id: I587262cc36e5fccc59620b4bd2d2c3c05c72232f
* Map "sr-Latn" to "sr_ZZ" for internal use.Yohei Yukawa2016-03-041-1/+24
| | | | | | | | | | | We want to expose Serbian (Latin) layout as "sr-Latn" to the system, while our internal logic may not be ready to deal with "sr-Latn" yet. As a temporary workaround, we remap "sr-Latn" into "sr_ZZ" for our internal use. Bug: 27348943 Change-Id: I93ff0c75b3687bb1b913f451b9eb5f2820beefbc
* Revert "Close FileChannels in UpdateHandler#copyFile."Yohei Yukawa2016-03-031-10/+2
| | | | | | | | | | | | | | This reverts commit 3e2670265e17e91c5a8cfff01711f973dccd2a0c. It turns out that the behavior change in libcore was unintentional, and it was already fixed [1]. Let's revert our workaround back to see if the existing code is compatible with N. [1]: Ibacb192abc37870c74a2500d65b94d68f9c2318e 5e7b572c2b494ab86ddd2baca3883a40a6064c1e Bug: 26239281 Change-Id: I6cd2340492d93251231e7ee37c3d4f82c1721293
* Merge "Close FileChannels in UpdateHandler#copyFile." into nyc-devKeisuke Kuroyanagi2016-02-251-2/+10
|\
| * Close FileChannels in UpdateHandler#copyFile.Keisuke Kuroyanagi2016-02-241-2/+10
| | | | | | | | | | Bug: 26239281 Change-Id: Ib30beb3548f8fb4a8e338b5da863ae28c252bc2b
* | Fix runtime crash on KitKat and prior.Yohei Yukawa2016-02-221-2/+8
|/ | | | | | | | | | | | | | | | | | This is a follow up CL to the previous CL [1], in which we started calling Window#setNavigationBarColor(int) when the window visibility is changed. One thing we missed is that calling Window#setNavigationBarColor(int) on KitKant or prior devices would result in a runtime crash. Hence with this CL we do not call that method unless the OS version is N or leter, because specifying Color.TRANSPARENT would make sense on N+ devices. [1]: I14d9490e00caa852035a05830e76114cbe6af8f2 6c04339c5aadb5118b0e0a8178b3d569956bbad7 Bug: 22564251 Bug: 27302540 Change-Id: Ib7299dd8c3dad4271f8fac453e690c83bda4a954
* Follow API removal of LocaleList#getPrimary().Yohei Yukawa2016-02-092-5/+14
| | | | | | | | | | | This follows up to a recent CL [1] that removed #getPrimary() method from LocaleList class. [1] I75f77aea6b75e38793ed8477e5e5a4420d5e6d85 fee44846376c212114223fc4259382921e6dca7a Bug: 26984092 Change-Id: Ied4678d35c4dcb380ce24e9bce9336dbbf6c16b8
* Suppress redundant TYPE_WINDOWS_STATE_CHANGED.Yohei Yukawa2016-02-021-1/+3
| | | | | Bug: 23975618 Change-Id: I5933beaa5b28404f85e100461bdeab5496eb3c0e
* Experimental automatic language switching support.Yohei Yukawa2016-01-222-1/+70
| | | | | | | | | | | With this CL, LatinIME switches the current subtype from its enabled subtypes based on the first locale in EditorInfo#hintLocales. This functionality is still experimental, and will be triggered only when EditorInfo#hintLocales is specified by the application. Bug: 22859862 Change-Id: Ibd0559b370d8aa0d50d1bada8ecfdac0ed8db898
* Support EditorInfo#hintLocales in compat library.Yohei Yukawa2016-01-222-0/+48
| | | | | | | | This CL updates LatinIME's compatibility library so that we can access EditorInfo#hintLocales without directly depending on unreleased SDK. Bug: 22859862 Change-Id: I4ba7d294bc314002c3abf8842f097a4249783364
* Use "languageTag" in RichInputMethodSubtype.Yohei Yukawa2016-01-212-1/+19
| | | | | | | | | | With this CL, RichInputMethodSubtype#getLocale() starts returning a Locale object that is initialized with "languageTag" when it is specified. No behavior change is intended when "languageTag" attribute is not available or specified. Bug: 22858221 Change-Id: I23f2e479b8e284ce589c6950b071ba84c5dd8ce1
* Merge "Hide settings-key until the device is unlocked."Yohei Yukawa2016-01-072-0/+91
|\
| * Hide settings-key until the device is unlocked.Yohei Yukawa2016-01-072-0/+91
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Starting in N, we are going to have new APIs to officially support the situation where apps need to run before the user has unlocked their device for the first time. For IME developers those APIs would be important not only because IMEs developers may want to support other apps that support that feature but also because IMEs developers have already needed to pay attention to the same situation where the IME is running so that the user can enter the initial password (e.g. for an encrypted device). Bug 11270326 is a perfect example of this scenario. Now we can disable settings-key until the device is unlocked by using the new API when running in Android N devices. Bug: 11270326 Change-Id: Ie1c6efa63b60b91430f1a78dde624d0f3dff3c69
* | Merge remote-tracking branch 'goog/mnc-dr-ryu-dev'David Riley2015-12-213-99/+172
|\ \ | |/ |/|
| * Check if last shown Emoji category ID is still validDmitry Torokhov2015-12-081-2/+18
| | | | | | | | | | | | | | | | | | | | | | | | | | When upgrading to a new version of APK we may find that the stored Emoji category ID is no longer applicable. For example it happened when we brought in the new Unicode 8.0 Emojis. Also restore the "Symbols" emoji category on pre-kitkat devices which was accidentally dropped when bringing in Unicode 8.0 Emojis. b/25972978 Change-Id: I91c044603b0aac8757cb8597d3af995f84b822f3
| * Unicode 8.0 emoji additions to Google Keyboard.Chieu Nguyen2015-11-112-19/+135
| |\ | | | | | | | | | | | | | | | | | | am: 7674a65367 * commit '7674a653678b542d795b0bd05c241654ffe1015a': Unicode 8.0 emoji additions to Google Keyboard.
| * \ Revert "Unicode 8.0 emoji changes to Google Keyboard."Ian Pedowitz2015-11-102-140/+19
| |\ \ | | | | | | | | | | | | | | | | | | | | | | | | am: e1d5012683 * commit 'e1d501268396e58bfdd37a0a50dfeb2ac48139a8': Revert "Unicode 8.0 emoji changes to Google Keyboard."
| * \ \ Unicode 8.0 emoji changes to Google Keyboard.Chieu Nguyen2015-11-092-19/+140
| |\ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | am: 9cc42549d1 * commit '9cc42549d18f1e28ffc8dae94ff36728933f53f1': Unicode 8.0 emoji changes to Google Keyboard.
| * | | | Fix AltR+1 -> ESC shortcuts bringing on-screen keyboardDmitry Torokhov2015-11-032-97/+154
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Change the way we decide whether we want to show on-screen keyboard by not only paying attention to modifiers, but also keeping track whether the key sequence started in the right state. We are still misfiring if user presses a non-modifier key and then our modifier hot-key, but such sequence is unlikely. Given the fact that we do not want to store too much state I believe this deficiency is acceptable. Bug: 25087681 Bug: 24142161 Change-Id: I1a6b5e8e903c27a87134a6c9a7cd474a0607d5c8 (cherry picked from commit 7c513455918a52bd28c1c8181cb2880db0973b4b)
* | | | | Change NavigationBar invisible if the input view is not shown.Seigo Nonaka2015-12-081-0/+13
| |_|_|/ |/| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The opaque navigation bar guard view does not make much sense when the IME does not show software keyboard at all. LatinIME does not show any UI when the hardware keyboard is connected. With Iea77915ecc55eedaf19899e72c44f704ba9d852c, input method can change the navigation bar visibility. This CL changes navigation bar invisible when the hardware keyboard is connected. Bug:22564251 Change-Id: I14d9490e00caa852035a05830e76114cbe6af8f2
generated by cgit v1.2.3 (git 2.25.1) at 2025-12-20 22:32:53 +0000