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

[Select] Menu goes off the screen with asynchronously loaded options #13748

Closed
2 tasks done
Filson14 opened this issue Nov 30, 2018 · 2 comments
Closed
2 tasks done

[Select] Menu goes off the screen with asynchronously loaded options #13748

Filson14 opened this issue Nov 30, 2018 · 2 comments
Labels
duplicate This issue or pull request already exists

Comments

@Filson14
Copy link

I've developed a component based on <Select /> where options are loaded dynamically based on string query from the menu search input. Because of that async load, the menu is initially smaller and fits to the viewport with that state. After options are loaded, list gets bigger and goes off the screen (if component is rendered near an edge).

  • This is not a v0.x issue.
  • I have searched the issues of this repository and believe that this is not a duplicate.

Expected Behavior 🤔

The menu being repositioned after its content changes. If it is not enough space below, it (or Popover?) should grow up instead of down. I need to stressed that it is repositioned after manually resized screen.

I was thinking about forcing resize or something like that. Maybe I can get any suggestion how to handle this kind of problem the right way?!

Current Behavior 😯

Mentioned above, examples below.

Examples 🌈

It is ok, when there is enough space.
image

As the component is rendered at the bottom of the page, there is the problem.
image
The black part is the desktop 😉

@oliviertassinari oliviertassinari added the duplicate This issue or pull request already exists label Dec 6, 2018
@oliviertassinari
Copy link
Member

@Filson14 I'm closing as a duplicate of #10595.

@Filson14
Copy link
Author

Filson14 commented Dec 6, 2018

Thank You! I've missed that issue. Will follow it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
duplicate This issue or pull request already exists
Projects
None yet
Development

No branches or pull requests

2 participants