diff options
| author | Yohei Yukawa <yukawa@google.com> | 2018-04-24 18:36:23 -0700 |
|---|---|---|
| committer | Yohei Yukawa <yukawa@google.com> | 2018-04-24 18:36:23 -0700 |
| commit | b1845f317cfc23bfaa0ebc5ef0c05aa72bb3e6b8 (patch) | |
| tree | 7df92fbf5ef7f7b1686596967f49de524808db80 /tools/aapt2/java/JavaClassGenerator_test.cpp | |
| parent | 88363dfc70170d3560efe9db8117567555e4e830 (diff) | |
Deprecate private AsciiCapable protocol
The concept "AsciiCapable InputMethodSubtype" was initially introduced
as a private protocol based on a magic keyword "AsciiCapable"
specified in "imeSubtypeExtraValue" attribute in API level 15 [1],
then became a public API "isAsciiCapable" attribute in API 19 [2].
However, it turns out that there remains one place in InputMethodUtils
where the previous private protocol is still used.
With this CL, InputMethodUtils stop relying on the previous private
AsciiCapable.
[1]: I1a83b227498073c47567f73566043c273809adc9
c36905673a7bcafe9ec74e82e6c4977f2aca6a50
[2]: Ic3ace4b6e0432d56696bcbc0be336aec1dc744a5
dc8abf6cee0bcf44e2cad8155f0c151105d46471
Fix: 78537996
Test: make doc-comment-check-docs -j
Test: atest InputMethodPreferenceTest InputMethodUtilsTest
Change-Id: I56c0c19878657a41882c2d784e1ac96a52ab33f6
Diffstat (limited to 'tools/aapt2/java/JavaClassGenerator_test.cpp')
0 files changed, 0 insertions, 0 deletions