There is no regular file representation for archive documents, so
the call to getFileForDocId(archivedDocId) was throwing an exception.
Bug: 27383423
Change-Id: Icbc1e8ecdddc7698cfdb79b41da6e1d3cecf11ae
Previously RootScanner is implemented by FutureTask, and if it is
cancelled before it starts running in background thread, the scan will
be never executed.
The CL stops using FutureTask and introduces CountDownLatch to control
UpdateRootsRunnable.
BUG=27369585
Change-Id: Ica8799faba0a8e5ca91a6b8be36dc4f5118d6333
Changes:
- Removed hints.
- Added TextViews for field labels.
- Added padding for inner dialog
- Adedd autoCorrect and capSentences to title and summary
- Changed strings.
- Set name to be selectAllOnFocus initially.
Also improved some logging statements.
BUG: 26324085
Change-Id: I32597a7c2839ca706dbbcf13660e976469ab8dd0
On the lockscreen, the minheight was always based on the intrinsic
height and not actually the minHeight of the children. Because
children were userlocked, they were now reporting their small size
instead of the single line size.
This meant that the expand motion on the lockscreen wasn't following
the finger at all.
Bug: 27418617
Change-Id: I81daaf87887de1adc014cb4c6d46f4ef118061e5
This CL makes the settings icon row invisible when it's not displaying,
this way it won't get the click event on the notification row before
the parent.
Bug: 27389571
Which are now supported by Jack.
Retain a few preconditions checks that enforce contract.
Disable the one assert we had...because it failed in tests.
Change-Id: I2f6cb01e1af1534be4428ce4a3ee625a163dd163
This CL updates the circular reveal animation to originate
from the gear and and done button in the inline controls.
Bug: 22451710
Change-Id: I050413c980a8c9e73fe2e9a789567051d3119373
Fixes a bug where RenderThread was constantly scheduling frames,
but didn't actually start the animation. Also fixes some jank
while the animation is playing.
Bug: 27396097
Change-Id: I353d60633eeef1a4f3bbfbeddb58f9703debe293
The registered shortcut will be called from PhoneWindowManager,
before dispatching
Change-Id: If26128939b45a639c8895719a7a23ca433f39fd9
(cherry picked from commit 4da863c5a8872dcabb179a978a2b2157d9081679)
The check whether dark changed was always done
on the notification itself, ignoring that the
contentviews actually also have a check whether it
changed, leading to potential problems that this state
became out of date. In addition did we assume that whenever
an update comes in the text becomes normal, which is
not true for an inline update. This hopefully fixes things once
and for all! I said once and for all!
Bug: 27147160
Change-Id: Idd68be8da0f648cf79102544b038065618c1d0ff
