Fixed a bug where a notification was incorrectly marked as removed
When unauto-bundled, it could lead to serious bugs on the lockscreen and the header not being restored. Change-Id: I2d6310a2bcb2f3a60402db5f1e522954f8bd0389 Fixes: 29463339
This commit is contained in:
@@ -761,9 +761,6 @@ public class ExpandableNotificationRow extends ActivatableNotificationView {
|
||||
mRemoved = true;
|
||||
|
||||
mPrivateLayout.setRemoved();
|
||||
if (mChildrenContainer != null) {
|
||||
mChildrenContainer.setRemoved();
|
||||
}
|
||||
}
|
||||
|
||||
public NotificationChildrenContainer getChildrenContainer() {
|
||||
|
||||
@@ -856,14 +856,6 @@ public class NotificationChildrenContainer extends ViewGroup {
|
||||
mNotificationParent.getNotificationColor());
|
||||
}
|
||||
|
||||
public void setRemoved() {
|
||||
int childCount = mChildren.size();
|
||||
for (int i = 0; i < childCount; i++) {
|
||||
ExpandableNotificationRow child = mChildren.get(i);
|
||||
child.setRemoved();
|
||||
}
|
||||
}
|
||||
|
||||
public int getPositionInLinearLayout(View childInGroup) {
|
||||
int position = mNotificationHeaderMargin + mNotificatonTopPadding;
|
||||
|
||||
|
||||
Reference in New Issue
Block a user