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

[BUG] Drawer modal height changes when focus switches between input fields on mobile device #3730

Open
1 of 9 tasks
KemalPajevic opened this issue Dec 4, 2024 · 0 comments
Labels
bug 👶🏻 New For new issues before prioritisation and refinement NOT Prioritized Issue not yet prioritized and added to a Milestone NOT Verified Applied to bug reports that have not been verified by a member of @kirbydesign/kirby-guild

Comments

@KemalPajevic
Copy link
Collaborator

Describe the bug

If you have a drawer modal with multiple input fields, switching between the fields changes the height of the drawer on a mobile device (tested on iOS and Android).

In an Capacitor iOS app, it seems to loose the additional height it needs to offset the keyboard.
In a web page opened in iOS Safari or Android Chrome the behavior seems more erratic (se the screen recording below).

Describe how to reproduce the bug

  1. Add a component with multiple input fields.
  2. Open a drawer with that component.
  3. Switch focus between the input fields.
  4. See that the drawer height changes.

A demo of the issue can be seen on this Stackblitz (open it in a mobile browser).

Which Kirby version was used?

9.7.2 and 10.0.0.

What was the expected behavior?

The height remains the same.

Add any screenshots

Capacitor app in iOS:

RPReplay_Final1731507653.mov

In a web page in iOS Safari:

ScreenRecording_12-03-2024.20-17-03_1.mov

Please complete the following information:

  • OS: iOS, Android
  • Browser: Safari, Chrome

Checklist:

The following tasks should be carried out in sequence in order to follow the process of contributing correctly.

Verification

To make sure the bug is not intended behaviour; it should be verified by a member of team Kirby before moving on to implementation.

  • Make sure the NOT verified label has been removed by a member of team Kirby; do not proceed until this is done.

Implementation

The contributor who wants to implement this issue should:

Review

Once the issue has been implemented and is ready for review:

@KemalPajevic KemalPajevic added bug NOT Prioritized Issue not yet prioritized and added to a Milestone 👶🏻 New For new issues before prioritisation and refinement NOT Verified Applied to bug reports that have not been verified by a member of @kirbydesign/kirby-guild labels Dec 4, 2024
@github-project-automation github-project-automation bot moved this to 💌 Inbox in Kirby Dec 4, 2024
@alxzak alxzak moved this from 💌 Inbox to 📙 Backlog in Kirby Dec 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug 👶🏻 New For new issues before prioritisation and refinement NOT Prioritized Issue not yet prioritized and added to a Milestone NOT Verified Applied to bug reports that have not been verified by a member of @kirbydesign/kirby-guild
Projects
Status: 📙 Backlog
Development

No branches or pull requests

1 participant