)]}'
{
  "commit": "9b0fd452d75eed70ffdd8be1e863dfb46239e871",
  "tree": "0ecba8bda032e4e693dd9a344121e2c1ea4d485d",
  "parents": [
    "aec6d9da48917c21bbe6ca9b9cc9c9ff42760aeb"
  ],
  "author": {
    "name": "Alex Salo",
    "email": "asalo@google.com",
    "time": "Wed Aug 16 17:41:05 2023 -0700"
  },
  "committer": {
    "name": "Alex Salo",
    "email": "asalo@google.com",
    "time": "Wed Aug 30 18:20:11 2023 +0000"
  },
  "message": "Make disabled EditTexts fillable by Autofill\n\nSome app developers are trying to improve the UX of the sign in flow by disabling one of the fields (e.g. password field) until the input in the other field (e.g. username) is validated (e.g. length exceeds a threshold). This makes sense.\n\nHowever, such behavior presents a problem for Autofill: the fetched value currently can\u0027t be filled into a field that is disabled.\n\nOne approach can be to perform the fill of the fields sequentially, but there is no guarantee on which field the developer disables/enables. Also it\u0027s easy to come up with the examples of how this can quickly break.\n\nInstead, this change just allows Autofill to fill the fields that are disabled. Note that Autofill already ignores the fields that are invisible. Therefore, this only affects the fields that are: a) editable, and b) visible, and c) disabled. There should be no good reason to disable a visible field for any purpose other then the input validation, in which case Autofill is expected to work.\n\nBug: 296097301\nBug: 286515609\nBug: 292049995\nBug: 294074377\nTest: atest CtsAutoFillServiceTestCases\nChange-Id: I7e1f342ab30f309b419b68cc26868feaf5a53934\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "2ad3f74fcb7bec002726baf5d74934e6d21b0588",
      "old_mode": 33188,
      "old_path": "core/java/android/widget/TextView.java",
      "new_id": "63e882533a4cfd144cf9bafea3f090cc6648f81f",
      "new_mode": 33188,
      "new_path": "core/java/android/widget/TextView.java"
    }
  ]
}