Merge commit '4d3baaf5308ddee43c1cd742497a38806cec6320' into gingerbread-plus-aosp
* commit '4d3baaf5308ddee43c1cd742497a38806cec6320':
Bug fixes in Text selection.
PopupWindow now responds to the style attribute popupAnimationStyle
instead of windowAnimationStyle. The latter was being overridden with
undesired values. Animation.PopupWindow style added as a special
default sentinel value, which switches animation styles based on
whether the window is showing above or below an anchor.
Change-Id: Id7cc81f089b6053f2d3a495b1046002548ecf125
"Select word" is displayed only when the text field is not empty.
Paste is always displayed in first menu.
Bug #3001438
Cut/copy works
Bug #3052005 fixed in 3047653
Change-Id: I573f04818683f9b1c78ecb4613570b738d30ba09
Merge commit '106950f20bd352ed72ddf4490b2e19d305e36a74' into gingerbread-plus-aosp
* commit '106950f20bd352ed72ddf4490b2e19d305e36a74':
DO NOT MERGE. Fix logic for switching between overscroll and scroll modes.
The issue here was originally that webview was showing twice
as intense of an effect for edge glow as lists. The root cause
was that abslistview was calling onPull half as often as webview. This
occurred because every time an action_move came into the touch handler
for abslistview when it was in overscroll, the mode was ALWAYS changed
back to scroll mode. Therefore, half the action_move events were
essentially being eating by the abslistview state machine.
After fixing that issue, needed to decrease the intensity of the effect
for webview and abslistview by halving the PULL_DISTANCE_GLOW_FACTOR.
Change-Id: I5dbdf4f1219f3bb157a71d4fccf8fa42e2abe047
Merge commit '7e53f3d70994cfef255953e1df1881d057477d06'
* commit '7e53f3d70994cfef255953e1df1881d057477d06':
Fix bug 3047653 - Text select handles stick around when they shouldn't
Merge commit '624380a14def6c2acdb473e09c36139acbcefbf9' into gingerbread-plus-aosp
* commit '624380a14def6c2acdb473e09c36139acbcefbf9':
Fix bug 3047653 - Text select handles stick around when they shouldn't
Text select handles will now fade out on their own after a few seconds
since many apps expect a selection to be persistent while a text field
stays focused in touch mode. The user may tap within the selection to
bring the anchors back.
Text select handles will also disappear upon leaving touch mode.
Fix a bug that impaired cut/paste from the context menu.
Change-Id: I8f431e2d261aec02581150125d11324a3ee11656
Merge commit '53303da0a78da2042ec60226ee290d2c903e6023'
* commit '53303da0a78da2042ec60226ee290d2c903e6023':
Fix bug 3024080 - Date picker month field uses numeric text field
Merge commit '8bcbebd4178b2e9aca9ee3bd9e1e12c42e74c8db' into gingerbread-plus-aosp
* commit '8bcbebd4178b2e9aca9ee3bd9e1e12c42e74c8db':
Fix bug 3024080 - Date picker month field uses numeric text field
The new assets are just copies of old assets. However, now
the code is set up properly, and when we do get final
assets no new code needs to be written, and both TextView
and the select action mode for the browser will be updated.
Change-Id: I9a1461bf447f6bbc2782d8f948d873cbeeccbcb0
1. Don't bring up the keyboard if we're iconified by default
2. Also override onRequestFocusInDescendants to return false. This makes it so that we don't focus on the search edit text which is in the actionbar.
Change-Id: I345e9cd77f686f13762a20454a76ff1f7c4a5556
This feature is currently used to enable dragging the start and end
selection handles of a TextView at the same time. Could be used for
other things later.
Deleted some dead code in ArrowKeyMovementMethod and CursorControllers.
Change-Id: I930accd97ca1ca1917aab8a807db2c950fc7b409
- Respecting the AdapterView/Adapter contract using FrameLayout notification to update individual items
- Initial changes to allow for keeping (currently bitmap only) memory in check when loading numerous RemoteViews
- Fixing issue with leaking activities due to extra service connection references
- Fixing issue with multiple RemoteViewsAdapters being set on the same AdapterView
- Fixing small issue with StackView sometimes requesting indices out of bounds
- Removing background loading, reverting to previous message-queuing method (seems to be performant now)
Change-Id: I42313767aa791dfe35c247c97ae5d64389e6bb4c
Merge commit 'a24277977d597b88d3ccfed266e1803d3f7b20a2'
* commit 'a24277977d597b88d3ccfed266e1803d3f7b20a2':
docs: add more info about state list drawable and onclick attribute to Button
Merge commit '2dc43f3d4c721acf331d699e24d9aac4d4cc2f95' into gingerbread-plus-aosp
* commit '2dc43f3d4c721acf331d699e24d9aac4d4cc2f95':
docs: add more info about state list drawable and onclick attribute to Button
Merge commit '5b7328f257a76ff6b7b60872d6a106002ff1f679' into gingerbread
* commit '5b7328f257a76ff6b7b60872d6a106002ff1f679':
docs: add more info about state list drawable and onclick attribute to Button
- Change semantics if IDs associated with these fragments, to
work correctly when placed in a container. If the container
has an ID or you have supplied a tag, the fragment's ID is
optional.
- To do this, there is a new LayoutInflater API that allows code
creating views to access the parent container that view will
be in.
- Fix issues with state management around these fragments. Now
correctly retains state when switching to a layout that doesn't
include the fragment.
Also:
- Add new simple list layouts for items that want to show an
activated state.
- Add new Activity.dump() that can be invoked with adb shell
dumpsys; the default implementation dumps fragment state.
Change-Id: I192f35e3ea8c53fbd26cf909095f2a994abfc1b6
