)]}'
{
  "commit": "a23231ea7d9174adf545b803a57835e1a2ff8ed0",
  "tree": "8e1555e5465478a4c939ace22d761213d0e1a2d0",
  "parents": [
    "04bd4d8e4ece08cc4efbb4754665f46ec42eff79"
  ],
  "author": {
    "name": "Corentin Wallez",
    "email": "cwallez@chromium.org",
    "time": "Fri Oct 16 01:39:05 2020 +0200"
  },
  "committer": {
    "name": "Alexis Hétu",
    "email": "sugoi@google.com",
    "time": "Fri Oct 16 15:16:08 2020 +0000"
  },
  "message": "MetalSurface: correctly handle the window resizing.\n\nIn metal the size of the drawable (the texture use to render to the\nwindow) is decoupled from the window\u0027s size:\n\n - When the first drawable is created, its size is given by\n   layer.bounds.size * layer.contentsScale.\n - Once set the drawableSize never changes without the user setting the\n   layer.drawableSize explicitly.\n\nThis means that the code checking for OUT_OF_DATE_KHR needs to be\nupdated to check the texture size against the drawable\u0027s size (and not\nthe current scaled window size).\n\nAlso Swiftshader needs to set the drawableSize to the correct value when\nthe window is resized. The best moment to do this is when querying the\ncapabilities as that\u0027s done when a new swapchain is created (which\nhappens when the application is handling the window\u0027s resize).\n\nBug: dawn:269\nChange-Id: Icf1c3df63d42e0fa9211893f6b89d8709dfd942e\nReviewed-on: https://swiftshader-review.googlesource.com/c/SwiftShader/+/49328\nTested-by: Corentin Wallez \u003ccwallez@google.com\u003e\nReviewed-by: Alexis Hétu \u003csugoi@google.com\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "af5a4aed0681bb18152884b505a8b0722b461fb4",
      "old_mode": 33188,
      "old_path": "src/WSI/MetalSurface.mm",
      "new_id": "d4a44481accb9ad69d8c45af32857aec9feb7a87",
      "new_mode": 33188,
      "new_path": "src/WSI/MetalSurface.mm"
    }
  ]
}