- Apr 25, 2013
-
-
Jean Chalard authored
Bug: 7226877 Change-Id: Ib6c32bfee9977c27dbf7e1e590b2b00d9ceb7301
-
Jean Chalard authored
This adds a number to the extension. Note that for DownloadManager to keep this, the server needs to send it a mime type it does not recognize. Right now, it does not recognize application/json so it's okay, but we'd do well to remove the content/type header from the server to prevent problems. Bug: 8467516 Change-Id: Ic484f66ac3f67c36f59f2c0bcb8c7fdeb6e8590d
-
Jean Chalard authored
Bug: 8715614 Change-Id: I307d83923070994525cf0d27aad403e881a89314
-
Satoshi Kataoka authored
Bug: 8600958 Change-Id: Ic472500406b9d54ec4052c490ee7cef62fc4e52a
-
- Apr 24, 2013
-
-
Tadashi G. Takaoka authored
Bug: 8159728 Change-Id: Ia37ab32b63e4eda29bf1411719d00846525c278f
-
Satoshi Kataoka authored
Bug: 8701480 Change-Id: If8242cfe61f3e56712fd6e25e36858cff7f0d177
-
Tadashi G. Takaoka authored
Bug: 8159728 Change-Id: I1ab846d0910aacbd2f979289d72bafea8a8e0378
-
- Apr 23, 2013
-
-
Jean Chalard authored
Bug: 8651863 Change-Id: I748f35726d72ede926d5b06ed87ff029317f1ac3
-
- Apr 22, 2013
-
-
Satoshi Kataoka authored
Bug: 8533258 Change-Id: I00e4916f86f29dd476c51a65e8fa5a6c136fd179
-
Tadashi G. Takaoka authored
Bug: 8600958 Change-Id: I303adfbe25a56cc9b5ee9f3b5169a5bca0ad6c4a
-
Tadashi G. Takaoka authored
Bug: 8633367 Change-Id: Ifc0f97b1fdf5e5cc3601c24a503058c4822478dc
-
Jean Chalard authored
Change-Id: I954856b7fec0b91e19a467f2a87978d49caa639d
-
- Apr 19, 2013
-
-
Tadashi G. Takaoka authored
This is a preliminary implementation because the welcome screen video is just a placeholder. Bug: 8159728 Change-Id: I6a2459a266babec2f078fc393b18c77b0b7992a8
-
Tadashi G. Takaoka authored
Bug: 8159728 Change-Id: I05ff6578980ec2e210ebb482ea51b1600e74a4f4
-
Tadashi G. Takaoka authored
Bug: 8159728 Change-Id: I1578fc31875a1edbfea213fb5e1a1b464d02e941
-
Jean Chalard authored
Also, theoretically, we don't want to retrieve older suggestions if there are no results for a recorrection - that would look random. This bug addresses this too. Bug: 8657919 Change-Id: I44f36d34a708a968ab71fa0592da57f4c97d4b7f
-
Jean Chalard authored
Bug: 8657736 Change-Id: I459d1c200826c1c394f8207475ecf60a4f356793
-
Tadashi G. Takaoka authored
Bug: 8159728 Change-Id: I62ccbebaae0a0c4a93ad7c155fc3020a7f357f3c
-
- Apr 18, 2013
-
-
Jean Chalard authored
Bug: 8344402 Change-Id: I41b8440f0d72a66fde3f6feb0db8239c9bb10ea3
-
Tadashi G. Takaoka authored
Bug: 8159728 Change-Id: Ia5a14a35292b43dc1eaa2d4edd65134040355149
-
- Apr 17, 2013
-
-
Tadashi G. Takaoka authored
Bug: 8159728 Change-Id: I46c77c31973ae492c2a12291f2e0b154f64d26c9
-
Tadashi G. Takaoka authored
Bug: 8159728 Change-Id: I9f6f04b09b2cefdb7ece76a4f3c39ab56d0c8fab
-
Tadashi G. Takaoka authored
This is a follow up of Ide3cd3acba. Bug: 8632344 Change-Id: Iafe51798a1a74eff5d8fcd6f0117d16b419d447d
-
Tadashi G. Takaoka authored
Bug: 8632344 Change-Id: Ide3cd3acba3987317cff709fa591eadaa71834e8
-
- Apr 16, 2013
-
-
Jean Chalard authored
This is about as ad-hoc as it gets, but then again, what we want is probably as ad-hoc as it gets. All URL boxes I know of double as search bars, and not adding automatic spaces there sucks (e.g. in Chrome URL bar). And in other boxes actually you don't want to add a space if it looks like a URL. QSB isn't even a search box, and it behaves like this. So I think this is actually the right answer to the problem. Bug: 7062925 Change-Id: Ib09472b34644fd5bf2dc84bb97cedeeba28bcd02
-
Jean Chalard authored
Change-Id: Ibf2cdedf510c296561bb5eeb6ff18c3414d6d6f4
-
Jean Chalard authored
Bug: 7657025 Change-Id: I2f8fe7fc4596a498322ba5ccabbd0c18a2bc36cf
-
Jean Chalard authored
Change-Id: Ib4d002f90cd3a0e9ad4c04b883b0c1f05ada3ccf
-
Jean Chalard authored
Bug: 8620678 Change-Id: Ia91761f33518a010b2844d34523cadece261c67e
-
Jean Chalard authored
Bug: 8620758 Change-Id: I39f07939ebb6148a48aae5b915ee807002a5b02d
-
- Apr 15, 2013
-
-
Jean Chalard authored
Bug: 8583091 Change-Id: I9195d68e44e9a282e25ccd2978d7b4088f600170
-
Jean Chalard authored
The only place where it's used is checked for nullity. Also, it's possible, also difficult, to match a different recapitalize with the old code, triggering a bug that this fixes. Change-Id: I717d6df489025c75d1caca290a9086c3b39a9306
-
Jean Chalard authored
Bug: 7980115 Change-Id: I8de31068992aec712eaad132857d9dc61f28e30a
-
Jean Chalard authored
Upon pressing Shift, if there is currently a selected string, have Latin IME change its capitalization. This does not yet have the keyboard mode follow the mode - the change is complicated enough as is. Bug: 7657025 Change-Id: I54fe8485f44e04efd72c71ac9feee5ce21ba06f2
-
Jean Chalard authored
Bug: 8084810 Change-Id: I1743c09c43ca6835bb2f607684b037bf17d36335
-
Jean Chalard authored
If the user gestures a word, then hits backspace in disapproval, and gestures about the same thing again, make sure that we don't suggest the same thing again. Bug: 7549311 Change-Id: I793bc4df7c3841fa8f2f4146707c26e873f374c1
-
Tadashi G. Takaoka authored
Bug: 8560722 Change-Id: I825b135bd13aca17e712330660978b834648dbc3
-
Tadashi G. Takaoka authored
Bug: 8613600 Change-Id: I279d3264080aede59203205c45763c7f8ff08ae6
-
Tadashi G. Takaoka authored
Bug: 8605150 Change-Id: Iadbebfb80e765c97e58e8524eb87419f2a9e41d4
-
Jean Chalard authored
There are two problems here. The first one is the tests would send an invalid unicode character. Although we could want dicttool to handle this more gracefully, it's fine for now. The second problem is much more serious. If a node has more than 128 children, then the java code will crash trying to read the dictionary back because of a bug that this change fixes. In theory, it's possible that happens when we try to load the user history dictionary back from the disk - native code is not affected so there is no other point that may cause a problem. In the practice, that means you'd need to have 129 words with a common prefix (including empty string) but all different after this. It's almost impossible with Google Keyboard since there are only so many keys on the keyboard that you can make a word out of, and then again you'd have to do it repeatedly until it actually enters the user history dictionary, wait for it to get saved on the disk. The bad news is, if you manage to get this far, the keyboard will crash every time and won't be able to get up until you clear data for the package. The good news is, the dictionary itself is not corrupted and only the reading code is wrong. So updating to a newer version would actually even recover from this situation. All in all, considering how almost-impossible this is to trigger, I don't think even a single user actually did hit this bug. Bug: 8583091 Change-Id: Iabb2a7f47cbd9ed3193d2a3487318d280753e071
-