Age | Commit message (Collapse) | Author |
|
Co-authored-by: GitHub Actions <noreply@github.com>
(cherry picked from commit e54955dd5e6b97679ba723ef20ec965895c297b4)
|
|
(cherry picked from commit 73648b39d02086d1b964a89e049fe2c4ae3c33fc)
|
|
Co-authored-by: GitHub Actions <noreply@github.com>
(cherry picked from commit 07b8505fe08c4cb33a8f3f72617cc932405cdb81)
|
|
Co-authored-by: GitHub Actions <noreply@github.com>
(cherry picked from commit e124dcbd595464e2c4c45c1d160e30972740c492)
|
|
* Mark Chrome as reliably fillable and saveable
* Mention Autofill improvements in CHANGELOG
(cherry picked from commit 6206850eb298f554b7ce9a1cd9adb6a392ff1e54)
|
|
https://chromereleases.googleblog.com/2021/01/chrome-beta-for-android-update_28.html
(cherry picked from commit fe29aa0cb0900683b83f47e70e1ba3967f32d560)
|
|
(cherry picked from commit 5a3395040cab74903c95eb5d97308451d051ac96)
Signed-off-by: Harsh Shandilya <me@msfjarvis.dev>
|
|
* Mark Chrome Canary as non-flaky and allowing save
* autofill-parser: update API dump
Signed-off-by: Harsh Shandilya <me@msfjarvis.dev>
* autofill-parser: bump snapshot version
Signed-off-by: Harsh Shandilya <me@msfjarvis.dev>
Co-authored-by: Harsh Shandilya <me@msfjarvis.dev>
(cherry picked from commit 2e43d77c5c72a0111445317a3d88e53a8b4b6782)
Signed-off-by: Harsh Shandilya <me@msfjarvis.dev>
|
|
Signed-off-by: Harsh Shandilya <me@msfjarvis.dev>
(cherry picked from commit 8eec5cc6c7dc6d4c50dadf78e6cdc948c19486a5)
|
|
Signed-off-by: Harsh Shandilya <me@msfjarvis.dev>
(cherry picked from commit 0480b759527420be754f0a2720bccf4a46d06304)
|
|
Co-authored-by: FabianHenneke <FabianHenneke@users.noreply.github.com>
|
|
|
|
Co-authored-by: FabianHenneke <FabianHenneke@users.noreply.github.com>
|
|
Filling passwords is usually only offered for fields with a password
input type, which ensures that they are always properly masked. Certain
custom views (e.g., the Termux terminal view), may apply their own
masking that is not based on the standard views.
With this commit, we allow filling passwords into arbitrary fields as
long as they have an Autofill hint that indicates a password.
|
|
Tie breakers for Autofill fields should only be evaluated if there is
a need to, in particular not if only a single or no field is matched.
Apart from a potential minor performance improvement, this should not
cause any user-visible changes, but does simplify the log output
considerably.
|
|
Co-authored-by: FabianHenneke <FabianHenneke@users.noreply.github.com>
|
|
We use an alpha version of core-ktx that might be undesirable for projects including the library
Signed-off-by: Harsh Shandilya <me@msfjarvis.dev>
|
|
Co-authored-by: Harsh Shandilya <me@msfjarvis.dev>
Co-authored-by: Fabian Henneke <fabian@henneke.me>
|