Autofill opening in Snapchat

[Timon-D3v]

Hey there

A lot of the times, especially when I have the Passbolt app running in the background, it tries to autofill my snapchat texts. There is nothing to autofill there and it overlaps my keyboard which is a little annoying. (It's right over my emojis)

Here is a picture:

Some extra context:
While I could just click the close button, that is annoying and I found that clicking the close button is easy to miss (and then the Passbolt app opens).

My suggestions:
One way would be to only fix the issue from above: You check if the field is a snapchat message box and if true don't show the autofill message. I don't know how hard that is, but I could imagine it's not the easiest thing to to while still having autofill on the login Page.

Another solition that came in my mind would be to have the option in the app to choose apps you don't want to use autofill in. That would solve my issue since you have to log in to your snapchat account once and after that I could disable autofill for snapchat.
I think this solution is not only easyier to implement, but would also add a great feature to the app and other users with similar issues in other apps could benefit from it. (If this feature already exists please let me know, I could not find it)

Anyways, thanks a lot for your work, I really love the app and passbolt as a whole. I am also happy to contribute if you want. (I have a lot of webdev experience, but I never built an Android app. But I always like a little challange and think it's not do different.)

Best regards
Timon

[marc1nm]

hello @Timon-D3v ,

Thanks for the report. You brought up some points that I'd like to address:

1. Autofill service - by the look of the autofill UI, I see that you are using the legacy accessibility autofill service, not the native autofill service. You can find more information inside the Passbolt app in the settings -> app settings -> autofill. The recommended approach is to use the native autofill (and turn on Chrome native autofill if you are using it - also details are in the settings). Note: only one service at a time should be turned on, so if you decide to change, please also turn off the accessibility service. Most likely, it's best to restart the Android device after the change.
2. Accessibility service dialog - as for the dialog of this service, as developers we can control its behavior (opposite to the native autofill dropdown, which the Android OS controls). After your suggestions, I think it makes sense to enlarge the clickable area on the "close", and we could also make it draggable, so the users can drag it to another place on the screen, so it does not overlap the content. This should fix the current issue and improve the experience.
3. We discussed briefly the possibility of implementing a settings screen on which you could disable autofill for a specified application or URL. This requires some analysis; we will work on the documentation first.

Best

[Timon-D3v]

Oh ok, got it. So I already had the autofill service turned on, but I didn't know I had to disable the legacy one (Thought double would be double the power :).

That already "solved" my issue in that sense that the new autofill box is smaller and I could click the emoji tab, but the autofill service doesn't try to recommend any passwords while typing on a snap anyways.

However I still think the issue is not really solved, since someone that cannot use the autofill service and thus uses the legacy option, would be facing the problem.

My conclusions:

1. Maybe it would be a good idea to have a infobox that tells users to turn off the legacy one (I don't know if there is a popup while you activate it, but I think a permanent hint would be beneficial)

2. I am happy you'll work on the option to disable some apps and open to help if needed. Having thougt a little more about the problem though, I could not come up with another usecase for disabling an app other than the autofill in that app not working, so maybe it is wise to put the menu in the "expert settings", "developer mode" or "debug, logs" tab.

3. While I think making the close button bigger is a good idea, I don't agree with the option to drag it around. Because if I don't want to use the autofill box, i can just close it. My personal issue was that it annoyed me to be there in the first place. If I drag it away or close it does not really matter, since I still am annoyed by the box going in my way. I also think that it would annoy more people that accidently move the box around than people using it. (And if you were to add a button/field to drag the box, you would have to make the box even bigger, which would be more annoying again)

Also please keep me updated, thanks :)

[marc1nm]

Hello,

One of the points has been addressed in the 2.5.0 release — specifically, enlarging the accessibility autofill close icon.

We plan to address the second point — displaying information about autofill services — in the next release.

As for the option to disable autofill for selected apps, this feature is currently on hold. A feature request can be created on the community forum to gather votes and feedback from the community.