PhilippC / PhilippC/keepass2android

[BUG] Username-only not filled

Open
#2,731 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug
Dominant language
C#
Stars
6.2k
Forks
478
Avg merge
1h 4m
Merged PRs (30d)
2

Description

Checks
  • I have read the FAQ section, searched the open issues, and still think this is a new bug.
Describe the bug you encountered:

A website in Chrome has a separate Username-only and Password-only entry. The User name does not work.
in Gboard it does not provide the K2A completion, I always need to switch to the K2A Keyboard and back.
On Linux using KeepassXC-Browser the completion works.

What does a website need to trigger the K2A completion offer in Gboard?

The page body looks like this:

<body class="login-background">
   <div class="login-page" id="login-page-id">
      <div class='form form-login'>
            <img style = 'float:right;width:145px;height:20px;margin-bottom:100px' class='img-fluid' alt='FOO BAR' src='[data:image/png;base64...==)' />
            <p align = "left" style="font-size:32pt;">
                time<strong><i>Card</i></strong>
            </p>
            <form action = "[/Home/CheckLoginByUsername?ReturnUrl=/Home/Homepage](view-source:https://foo)" method="post"><input type = "text" name="Username" placeholder="Benutzername" autocomplete="on" id="user-name-input" autofocus />
                <button type = "submit" id="login-button">Weiter</button>
           </form>
         <br/>
      </div>
   </div>
   <div class='text-muted' style='position:fixed;text-align:right;bottom:0px;width: 100 %'>cdcdsfgtr</div>
   <style>
      .login-background {
         background-image:url('/Content/images/login02.jpg');
         background-size:cover;
         min-height:100 %;
         height:100 %;
      }
   </style>
   <script>
      function login(usern, pasw)
      {
         var user = document.getElementsByName('Username');
         if (user != null)
         {
           user[0].value = usern;
         };
         var pwd = document.getElementsByName('Password');
         if (pwd != null)
         {
            pwd[0].value = pasw;
         };
         document.getElementById('login-button').click();
      };
   </script>
</body>
Describe what you expected to happen:

No response

What version of Keepass2Android are you using?

1.11-r0

Which version of Android are you on?

14

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the username-only login page in Keepass2Android 1.11-r0 on Android 14 with Chrome and Gboard, using the HTML and field attributes in the report. Compare the completion behavior with KeepassXC-Browser on Linux; done means the username-only field receives the expected K2A completion without switching keyboards.

Written by the indexing model from the issue text.

Assessment

Tech stack
android
Domain
mobile-dev
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
28/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.