-
Notifications
You must be signed in to change notification settings - Fork 209
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
Comments
Hey @yogeshapps can you create a reproduction of this here so that we can triage it better. |
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! |
Hi @Rajdeepc I have created a story https://studio.webcomponents.dev/edit/eBpFzyndu07XRztVOozf/src/index.ts?p=stories and added steps around this. |
Hello @yogeshapps using |
@TarunAdobe I don't think using a modal overlay is the proper solution here... The |
@Rocss Rightly siad. ColorPicker in Express is of popover type where user can continuously preview there changes without closing it. Popover is the right choice here and not modal. |
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?
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
The text was updated successfully, but these errors were encountered: