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
Swip up the navigation bar to the multi-task center, you can notice the transition animination has a short stuck everytime if you repeate the swip-up action.
Turn off autofill accessability service
Swip up the navigation bar AGAIN to the multi-task center, no longer animination stuck. It's quite smooth.
Expected Result
System UI smoothability not affected.
Actual Result
The transition animination to multi-task center has a short stuck everytime when you repeate the swip-up action.
Screenshots or Videos
No response
Additional Context
The problem is quite severe in the earily version of Native Bitwarden, and was great improved later since a version (I don't really remember the version code).
Now it still has a little bit impact, so I hope it can be fixed completedly.
Build Version
2024.11.7 (19528)
What server are you connecting to?
US
Self-host Server Version
No response
Environment Details
No response
Issue Tracking Info
I understand that work is tracked outside of Github. A PR will be linked to this issue should one be opened to address it, but Bitwarden doesn't use fields like "assigned", "milestone", or "project" to track progress.
The text was updated successfully, but these errors were encountered:
Steps To Reproduce
Expected Result
System UI smoothability not affected.
Actual Result
The transition animination to multi-task center has a short stuck everytime when you repeate the swip-up action.
Screenshots or Videos
No response
Additional Context
The problem is quite severe in the earily version of Native Bitwarden, and was great improved later since a version (I don't really remember the version code).
Now it still has a little bit impact, so I hope it can be fixed completedly.
Build Version
2024.11.7 (19528)
What server are you connecting to?
US
Self-host Server Version
No response
Environment Details
No response
Issue Tracking Info
The text was updated successfully, but these errors were encountered: