Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Option to disable the edit button on the lock screen #1857

Open
ikanakova opened this issue Apr 24, 2024 · 3 comments
Open

Option to disable the edit button on the lock screen #1857

ikanakova opened this issue Apr 24, 2024 · 3 comments
Labels
common: occasional Affects or can be seen by some users regularly or most users rarely severity: minor Impairs non-critical functionality or suitable workarounds exist type: enhancement New feature or request

Comments

@ikanakova
Copy link

It would be great if there was an option to hide the edit button on the lock screen, as I often inadvertently press it because it's where my phone has fingerprint unlock.

@TheLastProject
Copy link
Member

I suppose you mean when "Prevent screen lock" is enabled in Catima settings and you turned off and on your screen again?

Probably not that hard to implement. I'm not quite sure about it. I see your point (accidental press), but I also see how other users could be confused that "the edit button disappeared". Having more opinions and pros and cons here would be useful :)

@TheLastProject TheLastProject added the state: consensus-needed A consensus needs to be reached before this can be implemented label Apr 24, 2024
@ikanakova
Copy link
Author

ikanakova commented Apr 24, 2024

I have Keep screen on and Prevent screen lock enabled. But I like the option to lock the phone with the screen on and the code, but the edit button bothers me. An "edit button on locked screen" with a disable / enable option would be a cool feature.
Edit: If I accidentally press the edit button when the screen is locked then after unlocking I'm in the Edit Card and I don't want that.

@TheLastProject
Copy link
Member

I'm definitely not interested in adding another setting. I strongly watch out to try to have as little settings as possible in Catima to keep it easy to find the settings that matter, keep the amount of code paths down (every extra code path introduces a chance for extra bugs).

I've been thinking of this issue a bit more and I think the general issue here is not so much the edit button specifically, but the fact that drawing over the lock screen means the UI could be interacted with when people expect the device to be locked. This could either be accidental UI presses in someone's pants, but also a clumsy handover to a cashier causing a card to be unfavourited or left.

Because of this, I think it may be worth considering to, instead of just hiding the edit button, do the following:

  1. Hide all the UI elements that would change the state of the card or activate activity switches ("Edit", "Quick spend/receive", "Share", "Star", "Duplicate", "Archive", "Delete")
  2. Show some kind of message (maybe a Snackbar? Not sure) that says that some options are hidden because the device is locked and to unlock the device to get access to all options, that can be tapped to unlock. I haven't tested it, but it seems like isKeyguardLocked and requestDismissKeyguard functions should make this possible to do.

@TheLastProject TheLastProject added type: enhancement New feature or request severity: minor Impairs non-critical functionality or suitable workarounds exist common: occasional Affects or can be seen by some users regularly or most users rarely and removed state: consensus-needed A consensus needs to be reached before this can be implemented labels Apr 25, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
common: occasional Affects or can be seen by some users regularly or most users rarely severity: minor Impairs non-critical functionality or suitable workarounds exist type: enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants