)]}'
{
  "commit": "427778b0200893a773c45b5a172ee7ae01bd74f6",
  "tree": "874580f9fc7b7ebd74ef4f4a4159ed2e286750a9",
  "parents": [
    "b0f4faad9a79634c46d9dab6ad6f535a66d0774e"
  ],
  "author": {
    "name": "Riddle Hsu",
    "email": "riddlehsu@google.com",
    "time": "Mon May 27 17:57:20 2024 +0800"
  },
  "committer": {
    "name": "Riddle Hsu",
    "email": "riddlehsu@google.com",
    "time": "Tue May 28 10:45:56 2024 +0800"
  },
  "message": "Show pip until drawn with entering bounds if rotation changes\n\nThe request transition may be a CHANGE type for display rotation,\nSo augmentRequest is unable to set the entering bounds at the\nrequest stage. And when the CHANGE transition is ready, it includes\nthe entering pip info. Then the entering bounds will be applied at\nthe end of enter animation, which could cause to flicker because\nthe redraw of app configuration. The case only happens with type\nANIM_TYPE_ALPHA (i.e. swipe enter non-auto pip) because there\nwon\u0027t have pip overlay. Note that pip overlay is not a good option\nfor ANIM_TYPE_ALPHA because the non-opaque alpha is applied on task,\nit will be ugly that both overlay and app content are visible.\n\nSo just simply keep the pip task invisible until it is redraw with\nthe entering bounds, and then play fade-in animation when the\ndrawn transaction is committed.\n\nBug: 342071665\nTest: Swipe entering a non-auto pip activity.\n      The pip activity should not flicker during the\n      fade-in animation.\n\nChange-Id: Idd6a7f8b70c0e28cc570af77c72f3b9e1a997f72\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "3c7713d30714f5b3865042652c8dd938a3a0cc96",
      "old_mode": 33188,
      "old_path": "libs/WindowManager/Shell/src/com/android/wm/shell/pip/PipTransition.java",
      "new_id": "a9a72df78063b61187b21f8ea81aaf3af032ec2c",
      "new_mode": 33188,
      "new_path": "libs/WindowManager/Shell/src/com/android/wm/shell/pip/PipTransition.java"
    }
  ]
}