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

Block inserter menu jumps when interacted with on small screens #19758

Closed
tellthemachines opened this issue Jan 20, 2020 · 0 comments · Fixed by #19771
Closed

Block inserter menu jumps when interacted with on small screens #19758

tellthemachines opened this issue Jan 20, 2020 · 0 comments · Fixed by #19771
Assignees
Labels
[Status] In Progress Tracking issues with work in progress

Comments

@tellthemachines
Copy link
Contributor

Describe the bug

When opening the block inserter menu on small screens (< 782px), it occupies the whole screen. However, trying to interact with it in by focusing the search field or opening a section causes it to be pushed to the location of the clicked inserter .

I also checked on the xcode simulator (iphone 11) and the menu is opening directly from the inserter, instead of taking up the whole screen.

To reproduce
Steps to reproduce the behavior:

  1. Using a phone or tablet in portrait mode, click the block inserter on a post or page.
  2. Click on the search field.
  3. Verify inserter menu jumps to bottom of page

Expected behavior

Expect menu to expand to fill the screen on open and stay in place when interacted with.

Screenshots

Android (Samsung Galaxy S5):
Screen Shot 2020-01-20 at 4 46 00 pm

iOS simulator (iphone 11):

Screen Shot 2020-01-20 at 4 46 27 pm

Smartphone (please complete the following information):

  • Device: All devices

Additional context
Latest master, and plugin version 7.2. Doesn't happen in core version.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
[Status] In Progress Tracking issues with work in progress
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants