You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 12, 2023. It is now read-only.
Go to Settings -> Privacy & Security -> Switching Apps.
Switch the "Use fingerprint to unlock app" toggle ON.
Exit Settings menu and open a webpage.
Tap on the 3-dot menu to invoke menu contents.
Minimize and restore the app.
Touch fingerprint sensor.
Observe if the 3-dot menu remains displayed.
Expected behavior
After dismissing the fingerprint verification window with the fingerprint, the 3-dot menu stays open on restore.
Actual behavior
After restoring the app, the webpage and the 3-dot menu can be seen for a slip second before the fingerprint verification window is invoked. Upon dismissing the window, the 3-dot menu is no longer displayed.
Device information
Android device: Xiaomi Redmi Note 8T (Android 9).
Focus version: 96.0.0-beta.1 (Build 353412232 GV 96.0-20211206194555), RC 95.1.0, latest debug build from main 12/09.
20211209_114012.mp4
The text was updated successfully, but these errors were encountered:
In my opinion this is not necessarily a bug, is not something we really should restore. @jeffreygee What do you think?
I agree. It's not the smoothest transition, but it looks like it's just opening the last state/cached state of the app before switching but then triggering the fingerprint as expected. After you use the fingerprint, the menu goes away, right?
Steps to reproduce
Expected behavior
After dismissing the fingerprint verification window with the fingerprint, the 3-dot menu stays open on restore.
Actual behavior
After restoring the app, the webpage and the 3-dot menu can be seen for a slip second before the fingerprint verification window is invoked. Upon dismissing the window, the 3-dot menu is no longer displayed.
Device information
20211209_114012.mp4
The text was updated successfully, but these errors were encountered: