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

Making a selection from a multiselect dropdown brings you back to the beginning of the list #7010

Closed
dmetzger57 opened this issue Apr 29, 2020 · 4 comments · Fixed by ManageIQ/ui-components#438
Assignees

Comments

@dmetzger57
Copy link

Original BZ: https://bugzilla.redhat.com/show_bug.cgi?id=1741254

Description of problem:

If you have a multiselect dropdown with a large number of elements and you scroll down to make your choice, you will always be brought back to the start of the list after you make a selection rather than staying where you are.

Version-Release number of selected component (if applicable):
5.11.0.18.20190806180636_1dd6378

How reproducible:
always

Steps to Reproduce:

  1. Create a Service Dialog with a drop-down that has a large number of element (e.g. 100 items)
  2. Create a Service Catalog Item that uses the Service Dialog created in step 1
  3. Order the Service Catalog Item created in step 2
  4. Click the drop-down and scroll down (eg around item 50) and select the item

Actual results:
The item is selected and the drop-down list scrolls back to the top

Expected results:
The item is selected and the drop-down list does not scroll back to the top

@h-kataria
Copy link
Contributor

@himdel do you know if this has already been fixed

@himdel
Copy link
Contributor

himdel commented May 18, 2020

This was fixed in himdel/bootstrap-select#1 , UI PR #5029 .

@himdel
Copy link
Contributor

himdel commented May 18, 2020

But given hammer != 5.11 and this is angular code from ui-components, looking into whether ui-components code may still be using the old bootstrap-select via angular-patternfly.

@himdel
Copy link
Contributor

himdel commented May 18, 2020

Ah, no, turns out we are using the right @pf3/select,
but the issues was only fixed for the Report editor.

In other places, there's no data-live-search-focus="false" on the selects, so they still default to focusing live search when enabled.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants