-
Notifications
You must be signed in to change notification settings - Fork 2k
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
UI Breaks on Add New API Key
Drawer with Restricted
Permissions on Mobile
#1609
Comments
Good find! I have assigned the issue to you @unrenamed, feel free to PR! |
/assign |
This issue is already assigned to another person. Please find more issues here. |
@steven-tey please have a look at my PR and suggest if any further changes is needed! Thanks! |
@aritradevelops I see you've submitted a PR for this bug. However, this bug was assigned to me, and I'm actively working on a fix. According to the |
Hey @unrenamed I'm really sorry 🙏🏽, I was unaware that |
Appreciate your PR @aritradevelops but yes, this issue was assigned to @unrenamed so I'll default to him to create a PR within 48 hours before reviewing other submissions 🙏 |
/assign |
This issue is already assigned to another person. Please find more issues here. |
Issue Summary
When accessing the
Settings > API Keys
page on mobile, opening theAdd new API Key
drawer and selecting theRestricted
permissions option causes UI issues. TheCreate API key
button becomes unclickable, and the animated list of restricted permissions appears incomplete, as it is cut off at the bottom. This issue prevents users from completing the process of adding a new API key with restricted permissions.Steps to Reproduce
Settings > API Keys
.Create
button to open the drawer.Restricted
permissions option from the available options.Expected behavior
Create API Key
button should remain clickable and functional, allowing the user to proceed with adding a new API key.Screenshots/Videos
Screen.Recording.2024-10-22.at.18.08.41.mov
Version info
Tested on both:
The video was recorded using Brave browser. The issue is the same on iOS, although looks just a bit different (the scroll does not work at all, i.e. there is no empty white space at the bottom)
The text was updated successfully, but these errors were encountered: