There will be, in the future, a flag (View.DRAG_FLAG_GLOBAL) that means
for the drag to be cross-application. For now that flag constant is @hide
and furthermore the server-side implementation strips it, enforcing
local-only drags.
Change-Id: I8db840480ab90e18a5b8ecf29d62b4e6eafd405e
bug:3338078
1. The bug was that I was claculating delta month and day from
the current date but was changing the latter in the middle
thus causing inconsistent state.
Change-Id: Id3082b01778fc2b3116aa412aff3f12e9ebf0c97
Fixed a bug in FastScroller that could cause a crash on an empty list
in always-show mode.
Fix holo light button text color
Change-Id: I7b50043d715b9b870eb34808017d743ba64d2e08
Bug:3313519
In Find ActionMode, Enter should call find on page (rather than
advancing focus to the WebView).
In TextView, pass and Enter key down to super, so that the
pressed state can get called properly, and the
onClickListener will fire.
Change-Id: Ia875fa6b5cf02565a0d066a009e68ce97718b032
Rationalized the use of hideControllers and stopSelectionActionMode.
Hiding the selection controller should be done exclusively by stoping text selection
mode.
Bug 3322636
Change-Id: I30b4a651aa5fb5a865d636bec495a2b96ef114cd
The fast scroller now always positions by index position.
Fixed a bug with always-show fast scrollers.
Change-Id: I08586ab2aae9733e78aa823aff711bcc14d2d44d
Fix bug 3321329 - Spinner dropdown does not match widget width
Fix a bug in ListPopupWindow where setContentWidth was misbehaving
Add gravity setting to Spinner. This controls the positioning of the
selected item view within the widget. Holo default is left, legacy
default is center.
In dropdown mode, Spinners now WRAP_CONTENT width based on a limited
set of dropdown content. This means the dropdown can display a
reasonable amount of its content without clipping, while matching
width with the Spinner widget itself.
Change-Id: Ia17fd5f71526548408f4ad3b16bde536b0d3b207
Unless it has a background, the TextView will be able to support
alpha (text, cursor and highlighted text colors).
Background colored spans should be detected and should also multiply
their alpha by mCurrentAlpha.
Bug 3144861
Change-Id: If640895b8c0b25dc00b909a0a118b68fac0cfd76
* changes:
Don't enable hardware acceleration when the app owns the surface. Bug #3323096
Make FrameLayout support mixed wrap_content/match_parent children. Bug #3259668
- Tweak Fragment docs to match new sample code.
- Make some new attributes public.
- Hide all of the XmlAdapter stuff, since it is not actually being used.
Change-Id: Iae2062f91d1ca0c6b1d656ae948417d3d048482f
Bug #3259668
If a FrameLayout is measured with an UNSPECIFIED or AT_MOST spec,
it cannot correctly define the size of its children set to
match_parent. This change adds a second measurement pass similar
to what LinearLayout does in the same situation.
Change-Id: I20ac5203c2efc2e559f88b2c9573d4ad7df488b4
Inspired by https://review.source.android.com/#change,16606
Test class has been revamped to mimic new behavior: selectCurrentWord
is no longer used to add words to the dictionary. We rely on the suggestion
bar in the IME for that.
Change-Id: I1cb88df54dffb166c75f75fefb743ff55a33519b
See change 86347 for Step 1.
New state_multiline state flag, handled in TextView drawable background drawables.
Change-Id: I230df16c7ddee3296da180fd80ef341a4ac17dc0
Note that this used to create problems with ExtractEditText. These potential issues
were not handled in that CL.
Bug 3236848
Change-Id: I4b83ce8f66eba04f34c2faa8e38b83eb992637f0
When IME is being moved as part of a window going away, it could flicker
as it immediately moves behind the window. Fix this.
Also make the default soft input mode for PopupWindow to be to not change
the IME visibility, since it is a rare pop-up window that should cause your
IME to close.
Change-Id: I0b43e080ad012739e9a3e5842794c778c859ac1a
...android.app.Fragment.startActivityForResult(Fragment.java)
Make sure to remove all pending messages when AbsListView is detached
from its window.
But... that's not enough.
It turns out that when a fragment's views are animating away, they of
course don't get detached until after the animation is done. However
the fragment itself is immediately destroyed, leaving its live views
still going after that.
Here's a possible solution: when fragment manager initiates an animation
on a fragment whose views are being removed, it makes note of that so
it can hold off on destroying the fragment until the animation is over.
There are a lot of interesting race conditions here, if further operations
happen on the fragment while it is being animated. I think the code here
does something sensible, and it does seem to work for the situations I
have tested, but it is hard to know all of the edge cases that may happen.
Change-Id: I4490ce8862a9bb714c7ea54baca3072c62126388
