)]}'
{
  "commit": "20c4aadefd056c26fecba4bed4951349ee12a5a5",
  "tree": "e97b9519d7b517529a6fd635457556b89689772a",
  "parents": [
    "d95e64e373321cea33d572b36048c3e4e0436a94"
  ],
  "author": {
    "name": "Ian Kilpatrick",
    "email": "ikilpatrick@chromium.org",
    "time": "Fri Jun 10 18:14:08 2022"
  },
  "committer": {
    "name": "Chromium WPT Sync",
    "email": "blink-w3c-test-autoroller@chromium.org",
    "time": "Fri Jun 10 18:14:08 2022"
  },
  "message": "[layout] Fix min/max content sizes with %-padding.\n\nAnother thing I just noticed. See test-case. Its possible for the \"root\"\nwhich is haaving its min/max content size being computed to resolve\n%-padding block-start/end. We were doing this, however our cache was\ninvalid when the width of our containing-block changed.\n\nThis bails on the min/max sizes cache if any %-padding is present.\n\nWe\u0027ll be able to add an additional check here soon to reclaim a little\nbit of the cache hits for this case.\n\nChange-Id: I78fb85a2f3e4a347a27ca30c49cc5ee12221c063\n",
  "tree_diff": [
    {
      "type": "add",
      "old_id": "0000000000000000000000000000000000000000",
      "old_mode": 0,
      "old_path": "/dev/null",
      "new_id": "14d504406fe22b5f2bef8bb8f93365045b33bb1f",
      "new_mode": 33188,
      "new_path": "css/css-sizing/intrinsic-percent-replaced-dynamic-011.html"
    }
  ]
}