mirror of
https://github.com/spr-networks/super.git
synced 2026-04-24 20:35:55 +03:00
[GH-ISSUE #269] ui: ios: Adding a device, pressing return submit the form / cannot scroll to expiry #110
Labels
No labels
blocked
bug
documentation
enhancement
fixed
fixed ✅
hardening
implemented
installer
multicast
p1
p2
pending
podman
pull-request
security
testing
v1
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/super#110
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @0vercl0k on GitHub (Jan 20, 2024).
Original GitHub issue: https://github.com/spr-networks/super/issues/269
Originally assigned to: @lts-po on GitHub.
There's a behavior that is a little bit annoying when adding a new device. Assigning the name pull the keyboard which hides and make it hard to configure other options, especially the ones that are at the bottom of the page as somehow you can't access them by scrolling down:
https://github.com/spr-networks/super/assets/1476421/ff8ead59-c914-47ab-b31e-4582af00de3b
If you press return on the keyboard it validates the form which generates the QR code and skip to the next UI. So I need to select into another edit box, and press return (in other edit box, pressing return just remove the keyboard without validating it) to then be able to scroll all the way down.
It's unclear if this behavior is meant to be able to add a device really fast by just assigning a name as it's probably what users do the most or if it's a bug, lemme know!
@lts-po commented on GitHub (Jan 24, 2024):
Got a fix for this now! :) Should be for add device view & also if other forms have the same issue.
Will push new app soon, Thanks again for your reports @0vercl0k
@0vercl0k commented on GitHub (Feb 7, 2024):
No worries at all @lts-po, thank you for all the fixes :) I believe this is fixed in the latest fwiw