# Possible focus issue with relatively light dropdown **URL:** \ **Category:** Ignition\ **Tags:** ignition81, perspective\ **Created:** [June 6, 2023, 5:37pm UTC](https://forum.inductiveautomation.com/t/possible-focus-issue-with-relatively-light-dropdown/74651 "2023-06-06T17:37:46Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![user69](https://avatars.discourse-cdn.com/v4/letter/u/58f4c7/32.png) [@user69](https://forum.inductiveautomation.com/u/user69)\ **Post date:** [June 6, 2023, 5:37pm UTC](https://forum.inductiveautomation.com/t/possible-focus-issue-with-relatively-light-dropdown/74651/1 "2023-06-06T17:37:46Z")
Ignition version: 8.1.28 Perspective version: 2.1.28 I have a view with a dropdown component that appears to misbehave. The component has bindings on `props.options` (a script transform to fetch and format data based on a view parameter), and `position.display` (to show the component if there is a particular view parameter). The component has an "on action performed" event script that runs an update query to a database. Here is `props.search`: ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/e/8/e8a2a1a3dcae608edefebe27915f0a2f916ed9e3.png) This dropdown component appears with the correct options as desired when the view is rendered, but searching the options when the dropdown is expanded via mouse click is not possible. It's almost like the mouse click effects loss of focus on the dropdown. The search feature functions as desired when tabbing into the dropdown. Has anybody experienced this before? Indications from my project's affected users are that mouse-clicking into the dropdown has worked in the past, which suggests that a recent upgrade to 8.1.28 may be involved. Thanks in advance for your help. **Edit: the view is rendered in a Carousel embedding component.** ---
**Author:** ![amy.sudibyo](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/amy.sudibyo/32/38659_2.png) [@amy.sudibyo](https://forum.inductiveautomation.com/u/amy.sudibyo)\ **Post date:** [June 6, 2023, 11:41pm UTC](https://forum.inductiveautomation.com/t/possible-focus-issue-with-relatively-light-dropdown/74651/2 "2023-06-06T23:41:54Z")
I have just tested this in 8.1.27 and found the same behaviour as what you have described. If you click on the dropdown you cannot enter search text, you can only enter search text when tabbing into the dropdown. What's the reasoning for embedding in a carousel component? Is there another way you can display the dropdown? ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/d/7/d7e5e9fd7dc12a6e98eec6b3fddfc9f15c603f9b.png) ---
**Author:** ![user69](https://avatars.discourse-cdn.com/v4/letter/u/58f4c7/32.png) [@user69](https://forum.inductiveautomation.com/u/user69)\ **Post date:** [June 7, 2023, 12:24am UTC](https://forum.inductiveautomation.com/t/possible-focus-issue-with-relatively-light-dropdown/74651/3 "2023-06-07T00:24:31Z")
Thanks for confirmation. The containing view displays what can be thought of as "global" data and "specific" data groupings, where each "specific" data grouping is best viewed with the "global" data. The carousel's "swipability" and spatial tidiness seemed at development time like optimal features to handle rapid user transitions between "specific" data. There may be other acceptable ways to display the data. ---
**Author:** ![amy.sudibyo](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/amy.sudibyo/32/38659_2.png) [@amy.sudibyo](https://forum.inductiveautomation.com/u/amy.sudibyo)\ **Post date:** [June 7, 2023, 1:31am UTC](https://forum.inductiveautomation.com/t/possible-focus-issue-with-relatively-light-dropdown/74651/4 "2023-06-07T01:31:02Z")
If I am understanding correctly, your carousel contains multiple instances of the dropdown view, it is just the data that differs between views? If that's the case, there is no need to use a carousel. Put your dropdown on the main view and bind its options property to another component used to select which 'group' of data is required. Perhaps that component could be another dropdown. ---
**Author:** ![pascal.fragnoud](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pascal.fragnoud/32/24728_2.png) [@pascal.fragnoud](https://forum.inductiveautomation.com/u/pascal.fragnoud)\ **Post date:** [June 7, 2023, 8:58am UTC](https://forum.inductiveautomation.com/t/possible-focus-issue-with-relatively-light-dropdown/74651/5 "2023-06-07T08:58:52Z")
> [@user69](#): > > The component has an "on action performed" event script that runs an update query to a database. That seems risky. It's very easy to select the wrong option in a dropdown, maybe because of a mis click, or a wrong maneuver with a keyboard.