My previous commit [1] introduced a new XML attribute "languageTag" for
subtypes but forgot to initialize InputMethodSubtype object with that
attribute. As a result, InputMethodSubtype#getLanguageTag() has always
returned null even if "languageTag" attribute is specified.
[1]: I77db5b99a7cf745d800db75baf135bb60ad04820
8d6eeb01df72891acd3aa75e64aa1595a41cc96e
With this CL, InputMethodSubtype#getLanguageTag() starts returning the
value specified in the XML resource.
Bug: 22859862
Change-Id: I251d3d999afd13c0d618f2cb59e8ed3d47f21c98
Since the calculation of the number of notifications is dynamic now
it strongly depends on the notification min heights which are only
calculated once it is laid out.
This is now properly done.
Bug: 26480961
Change-Id: Ic7b270af826c28b4a9d2c08021605a5c9ae78860
Content intent of children in groups can now
only be launched if the group is expanded.
Bug: 26582343
Change-Id: I5bf2c853d7659b4c764892409c6c7cc3fc647cc8
On the lockscreen we were unintentionally disabling single clicks
on the media buttons while we only wanted to disallow it for the
notification header. This is now fixed by explicitly checking if
we are clicking on the notification header.
Bug: 26325096
Change-Id: I044f25ac3216b98c7769c31d09d19f801a437194
The notification content visible is now based on the intrinsic
height of the view and not just the actual height anymore.
This allows notifications to switch earlier when clicking on
the collapse button.
Change-Id: Icdf4ea50a7b1bbb78bd57a9f1c3eea25cf9c8d7c
There where 2 different issues which could lead to the dozemode
not working correctly:
1. The new workarabout where we show the expanded notification
if it has the same size as the collapsed, requires that dozemode
is also called on the right notification
2. When the children were not layed out yet, this calculation could be
wrong and the wrong child was selected, leading to the same issue.
Bug: 26459664
Change-Id: Ib67dcaf2ba9b8b9a1bfa5ece5b7d6c4dff677939
The text was never set to GONE when it was invisible,
leading to weird cases when fading between notification contents.
Change-Id: I92825b6d5a417c968c734061e55553be314af2b8
Group children are now isolated into their own group for a few seconds
until it's merged into the group again when they are
heads upped. This makes notifications groups finally usable with
HUNs again.
Change-Id: I0cb5e4f7a70e09989030dfe70ddcbb50575c1c02
When pulling down on a heads up notification the scrim would
fade in from 0 instead of fading to the new position.
The old behavior didn't work if the heads up notifications were
big, so we had to change it in order to always have a scrim.
Change-Id: I9ae387b75136c9240d863e06a8649c85b3c6c9dc
Heads up notifications can now be expanded with the expand
button. The notification stays there until the user dismisses it
or collapses it again.
Change-Id: I0f1b729915317bbbd6f13c3d968c933ffbe6feeb
- Should be updating the app text color to match the activity text color
- Fixing issue with indicator showing when fast toggle is disabled but
the indicator flag is enabled
- Tweaking layout so that the buttons are flush with the borders so that
we capture the full area for press/long press
Change-Id: Ia9b081883562ef4fd1c01fd42bc786a1feeb0854
- Remove whitespace from the GridModel, which isn't set up to deal with
it.
- Use absolute column bounds whenever translating the band rectangle
into column indices. This necessitates additional binary searching,
but is necessary when columns aren't fully populated, which happens
with the new grid layout.
BUG=26512327
Change-Id: I5016d5de8f00c366f575f0722739007ac1612923
