oj-select-single dropdown issue

frankiewilko

Hi all,

Not too long ago we upgraded from JET 7 to JET 8.3, and started using the new oj-select-single component. However, an issue has arose with the dropdown - if the component inside an oj-table, and is at or near the bottom of the screen, the dropdown opens below the input and and the lower part of the dropdown appears off the screen. The user then has to scroll down off the screen to see the remaining options.

Is there a way to manually tell the component to render the dropdown above the input? Or is there any other solution to this?

We use the row-renderer attribute on oj-table to render editable/read only rows.

John 'JB' Brock-Oracle

This sounds familiar and I believe it was fixed in a more recent release. You can test it out in the JET Cookbook pretty quickly to confirm that it's working.

frankiewilko

Thanks for the reply John.

We are currently in the process of upgrading to JET 9.2, and it looks to have solved the original issue. However a different issue has appeared, where the dropdown now disappears when there are no results.

Behavior before (8.3):

Behavior after (9.2):

Any idea what might be causing this issue? Or is this the new expected behavior

Cheers

Frankie

John 'JB' Brock-Oracle

Hi Frankie, sorry for the delayed reply. Yes, this is the new expected behavior. If you look at the JET Cookbook, you can see the differences between when you type a value that filters to nothing in the different versions.

If you absolutely want this old type of behavior, you could consider using a collectionTemplate with select-single and then using ListView inside that template, which has a feature called NoData where you can provide your own content to display when there isn't any data found.