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]: Overlay is raised too high on the screen when keyboard is open for tablet device #4936

Open
1 task done
yogeshapps opened this issue Nov 14, 2024 · 3 comments
Open
1 task done
Assignees
Labels
bug Something isn't working needs jira ticket triage An issue needing triage

Comments

@yogeshapps
Copy link

yogeshapps commented Nov 14, 2024

Code of conduct

  • I agree to follow this project's code of conduct.

Impacted component(s)

sp-overlay, sp-popover

Expected behavior

The panel should remain visible to the user and reposition itself based on trigger element position.

Actual behavior

When keyboard is open, overlay is raised too high and user is unable to use the panel

Screenshots

Overlay.Out.of.Viewport.Issue.mov

What browsers are you seeing the problem in?

Firefox, Chrome, Safari, Microsoft Edge

How can we reproduce this issue?

  1. Go to https://studio.webcomponents.dev/edit/eBpFzyndu07XRztVOozf/src/index.ts?p=stories in iPad. I used iPad Air.
  2. Click on Click on Button Popover
  3. Click on Example Textfield
  4. Popover is closed on open of soft keyboard of iPad.

Sample code or abstract reproduction which illustrates the problem

https://studio.webcomponents.dev/edit/eBpFzyndu07XRztVOozf/src/index.ts?p=stories
Created a story of the sample code.

No response

Severity

SEV 1

Logs taken while reproducing problem

No response

@yogeshapps yogeshapps added bug Something isn't working needs jira ticket triage An issue needing triage labels Nov 14, 2024
@TarunAdobe TarunAdobe self-assigned this Nov 20, 2024
@TarunAdobe
Copy link
Contributor

Hey @yogeshapps can you create a reproduction of this here so that we can triage it better.

@Rajdeepc
Copy link
Contributor

Hi @yogeshapps Just a friendly reminder: before we begin investigating reported issues, it's essential that the bug reporter follows the bug reporting guidelines. The current ticket is missing important details like repro steps and device diagnostics, which are crucial for efficient triage. Appreciate everyone's effort in keeping the process smooth and efficient!

@yogeshapps
Copy link
Author

Hi @Rajdeepc I have created a story https://studio.webcomponents.dev/edit/eBpFzyndu07XRztVOozf/src/index.ts?p=stories and added steps around this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working needs jira ticket triage An issue needing triage
Projects
None yet
Development

No branches or pull requests

3 participants