- Unable to commit suggestion by tap at the right edge of the row.
It turned out that the ListView doesn't fill the entire width of the
window. Fix this issue by specifying match_parent instead of
wrap_content. The Holo theme already has a match_parent attribute.
- Follow up of I03e0f602970b3b8f638f6c7b8cdff7be07ec17a6
Unexpected trancation happens on Matrial suggestion window was fixed,
but same issue happens on the Holo suggestion window. Fixing by
removing ellipsize=marquee.
Bug: 15347319
Bug: 27341560
Change-Id: Ic8445022634e9130f9462e02bfb08d4877396ba3
* changes:
Fixing crash when focusing tasks.
Minor tweaks to layout and visuals.
Improving transition from paging to stack.
Fixing issue with persistent screenshot notification
Updating task description when activity is visible.
There are two major changes in this CL:
1. Now IMMS resets its internal state whenever the system locale list
is changed, rather than just checking the primary system locale.
2. For software keyboard subtypes,
InputMethodUtils#getImplicitlyApplicableSubtypesLocked() now takes
the entire system locale list into account when determining what
subtypes should be enabled by default when the user does not
explicitly enable one or more subtypes.
Bug: 27129703
Change-Id: Iaf179d60c12b9a98b4f097e2449471c4184e049b
This is a preparation CL to take secondary system locales into
account in InputMethodUtils#getImplicitlyApplicableSubtypesLocked().
Suppose the following situation:
available subtypes:
en-US, en-IN, and en-GB, fr, fr-CA, fr-CH, fr (QWERTZ)
system locales:
en-GB, en-US, fr-MC
Basically we want to have at most one subtype for each language appears
in system locales. Hence the goal of this utility method is to filter
the above available subtypes into en-GB and fr. In other word, we do
not want to enable both en-GB and en-US subtypes in this scenario.
This CL introduces LocaleUtils#filterByLanguage() for this purpose, with
some unit tests. Note that that method is not used in production yet.
Bug: 27129703
Change-Id: I315cf3722a06e00bdbfac284c4949578da8fe78d
When doing the actual layout pass, desiredWindowWidth/Height might be wrong,
because window manager has the final say how large the surface is, so use
that size.
Bug: 27342700
Change-Id: I4f74fdef66ba7aa88b86f8c95fb391b1cc847beb
This reflects the change in PackageManager service:
frameworks/base commit 921dd754ab49df0cd580ff96503f7616c4c85f4a.
Bug: 27327503
Change-Id: Ic13788a3850c4d1a3a566b208853de9a6d2c5237
to reduce some flakiness and save time used on opening test root over
and over again.
Bug: 27271765
Change-Id: I6fa191ed8e0c7e8e071e4dd17c62aab5db1e23a5
- We call bindVisibleTaskViews() at the new scroll value expecting all
visible task views at that scroll to be bound synchronously, however,
the call to computeVisibleTaskTransforms() would not produce the
correct visible range if the visible range at the current and new
scroll resulted in gaps (ie. at scroll 0, 0-3 are visible, and at
scroll s, 5-8 were visible). As a result, the task view would not be
bound, causing a later crash.
Instead of the optimization before, which would assume every task
after the first non-visible task would also be non-visible, we can
just update the transforms for all task views. This ensures that
all visible task views should be bound, even if they are not in a
contiguous range. A global range is still provided in the call to
allow accessibility to focus the next task when a task is unbound at
the two ends of the stack.
- Also removing expensive calls to remove all listeners and cancel
animations that are not even started.
Bug: 27295423
Change-Id: Ib309e9de3095cacb178ae9ff5c53b8ee2c7ddac0
- Constructing max dim paths to be dependent on focused range
- Reducing highlight on tasks
- Making header/icons smaller
Change-Id: Ia7cf8b996428012e9619a640e178b4b42e094d68
- When we start scrolling, project the tasks onto the unfocused curve,
then reduce the offsets from the projected task indices back to the
normal indices as you scroll. This doesn’t give you a perfect result,
especially when scrolling in the same direction as the tasks are
offset, but is better than what we have now.
Change-Id: I055b08257fe1427e00e26ffa02f261cf51a8a2e0
- Ensure that we dismiss notifications when cancelled
- Removing unnecessary notification id and cancel extra
- Fixing the strings when capturing a screenshot fails
Bug: 27149651
Bug: 27177097
Change-Id: Ie2ea4318309fff4041acb04833216fdd5cf8838a
Initial pass at Network Security Config documentation, this also adds a
Security section to the list of topics which is currently just a stub.
Bug: 26931435
Change-Id: Iae0ec98a202ad3222b8f3ef39df77ecd2316504a
Bug: 27186019
Theory: It appears to be possible for FontRenderer
to not unbind its PBO prior to textures being uploaded,
resulting in trying to glSubTexImage2D with a bound
GL_PIXEL_UNPACK_BUFFER. In that scenario the void* is
the offset into the PBO which given a non-null data
will almost certainly overrun the end of the buffer. This
in turn produces a GL_INVALID_OPERATION error.
Change PixelBuffer to avoid leaking this state for now.
This will result in more calls to glBindBuffer/glUnbindBuffer
in the worst case, but the worst case is already bad so this
shouldn't be a problem. In the normal case we avoid binding
the PBO at all ever, so this doesn't impact that.
Change-Id: I05473f0d2f9a3a5da0e33d8f9ddea4731ce970e3
