Age | Commit message (Collapse) | Author |
|
Signed-off-by: Harsh Shandilya <me@msfjarvis.dev>
|
|
Android Oreo lacks the Autofill compatibility mode for browsers, which
means that browsers without explicit Android support will not trigger
Autofill events on web sites.
|
|
* Mark Bromite as non-flaky
* Mark Ungoogled as non-flaky
|
|
* build: update all dependencies
Signed-off-by: Harsh Shandilya <me@msfjarvis.dev>
* autofill-parser: add new hints
Signed-off-by: Harsh Shandilya <me@msfjarvis.dev>
* build: force the right annotation version manually
Signed-off-by: Harsh Shandilya <me@msfjarvis.dev>
Co-authored-by: Fabian Meumertzheim <fabian@meumertzhe.im>
|
|
Signed-off-by: Harsh Shandilya <me@msfjarvis.dev>
|
|
Signed-off-by: Harsh Shandilya <me@msfjarvis.dev>
|
|
Signed-off-by: Harsh Shandilya <me@msfjarvis.dev>
|
|
Signed-off-by: Harsh Shandilya <me@msfjarvis.dev>
|
|
* Mark Chrome as reliably fillable and saveable
* Mention Autofill improvements in CHANGELOG
|
|
https://chromereleases.googleblog.com/2021/01/chrome-beta-for-android-update_28.html
|
|
* editorconfig: delete
Signed-off-by: Harsh Shandilya <me@msfjarvis.dev>
* idea: adjust codestyle
Signed-off-by: Harsh Shandilya <me@msfjarvis.dev>
* all: reformat with simplified import ordering rules
Signed-off-by: Harsh Shandilya <me@msfjarvis.dev>
|
|
Unfocused single password fields in forms with no other recognized
fields must be marked as fillable or the Autofill service will no
longer be invoked on that form.
This is compatible with the restrictions of single-origin mode as
filling only takes place after the password field has gained focus and
the user has tapped the fill UI.
For an example website where fill UI is not shown without this commit,
open https://amazon.lbb.de and tab the user name field ("Benutzername")
first before focusing the password field.
|
|
|
|
|
|
* 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>
|
|
|
|
Co-authored-by: GitHub Actions <noreply@github.com>
|
|
Co-authored-by: GitHub Actions <noreply@github.com>
|
|
Co-authored-by: GitHub Actions <noreply@github.com>
|
|
Co-authored-by: GitHub Actions <noreply@github.com>
|
|
|
|
Co-authored-by: GitHub Actions <noreply@github.com>
|
|
Co-authored-by: GitHub Actions <noreply@github.com>
|
|
Signed-off-by: Harsh Shandilya <me@msfjarvis.dev>
|
|
Signed-off-by: Harsh Shandilya <me@msfjarvis.dev>
|
|
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>
|