446079600ece83b22cb91865bcbeb694292b0108 |
|
16-Mar-2017 |
Andrii Kulian <akulian@google.com> |
Separate global and override config sent to client There is some flakiness in View#onConfigurationChanged callback - if ViewRootImpl receives config update earlier than ActivityThread, it may not detect the configuration change and skip inner updates. Also now ViewRootImpl assumes that it receives the global config as a param, but instead it gets merged config from WM. This means that ViewRootImpl#sConfigCallbacks was sending incorrect values to the recipients. This CL switches to sending global and override configuration to the client separately. Also in case if there is a corresponding activity, it first updates it and waits for update callback to ViewRootImpl. This way global config and override config for activity will always be set first and resources will be updated before inner state of ViewRootImpl is updated. Bug: 35870157 Bug: 34164473 Test: android.server.cts.ActivityManagerDisplayTests Test: testOnMovedToDisplayCallback Change-Id: Ic9e7541cf25ecfac6ec90e48f7efb0ece91f657e
/frameworks/base/core/java/android/view/AccessibilityIterators.java
|
6090995951c6e2e4dcf38102f01793f8a94166e1 |
|
19-Nov-2013 |
John Spurlock <jspurlock@google.com> |
Remove unused imports from frameworks/base. Change-Id: Ia1f99bd2c1105b0b0f70aa614f1f4a67b2840906
/frameworks/base/core/java/android/view/AccessibilityIterators.java
|
bbd31559f32f86a100904fe8a5bc37677b5ba441 |
|
11-Jun-2012 |
Svetoslav Ganov <svetoslavganov@google.com> |
NPE when iterating by character and word in Launcher widgets. 1. The character and word iterators were use the application context to keep track of locale changes. However, for widgets the context from which the app context is obtained is custom created therefore the app context is null and the iterators code does not expect that. Now we are caching the locale and update it when the configuration changes. bug:6642281 Change-Id: I3fd201ab9e4efd79e3bdc8afd8ee644e4354a7fb
/frameworks/base/core/java/android/view/AccessibilityIterators.java
|
39f2aee640eea62b43fa79f28dec3a962e5cb065 |
|
29-May-2012 |
Svetoslav Ganov <svetoslavganov@google.com> |
Updating the behaviour of accessibility text iterators. 1. Iterators were skipping content on reversing direction. 2. The cursor was positioned at the beginning of the next text segment when moving forward and at end of the previous text segment when moving backwards. This is incorrect and now the cursor is positioned at the end of the segment when moving forward and at the beginning when moving backward. 3. The cursor position was not properly set when reaching the end/start of the text. 4. The iterators were reporting strictly the next/previous segment even if the cursor is within such a segment. Thus, when traversing some content may be skipped. Now moving forward moves the selection to the next segment end and the start position is either the old index if it was within a segment or the start of the segment. Same in reverse. bug:6575099 Change-Id: Ib48a649cec53910339baf831a75e26440be6e576
/frameworks/base/core/java/android/view/AccessibilityIterators.java
|
9768832da837e7716555d394bd13fb879a223860 |
|
17-May-2012 |
alanv <alanv@google.com> |
Fix paragraph iterator. Bug: 6509239 Change-Id: I628d7fd07cda24c66a0fa3f456e0141786e768a5
/frameworks/base/core/java/android/view/AccessibilityIterators.java
|
6d17a936f73976971135aa1e6248662533343292 |
|
28-Apr-2012 |
Svetoslav Ganov <svetoslavganov@google.com> |
Text traversal at various granularities. 1. Implementing text content navigation at various granularities. For views that have content description but no text the content description is the traversed at character and word granularities. For views that inherit from TextView the supported granularities are character, word, line, and page. bug:5932640 Conflicts: core/java/android/view/View.java Conflicts: core/java/android/view/View.java Change-Id: I66d1e16ce9ac5d6b49f036b17c087b2a7075e4c0
/frameworks/base/core/java/android/view/AccessibilityIterators.java
|