I was showing a page to a person.
They scrolled in a way I had not.
They clicked a dropdown, and it went upwards which I did not realize it could do.
Then when they clicked a selection, the page switched because the dropdown was over navigation behind it when opened upwards.
Is there a way to force the dropdown to only drop downwards?
Is there a way to block events behind a dropdown menu easily?
v8.1.19
Regardless of which way the Dropdown opened, click events should not have propagated into components behind the options modal. What was the "navigation" behind the options modal?
Yes - place the Dropdown at the top of the page. Beyond that, no. You're dealing with the behaviors of a responsive component, where the session determined there was not enough space below the Dropdown to display the options, and the session therefore responded to the available space and opened the options above the Dropdown.
Hi,
I encountered similar issue - clicking a dropdown option also triggers a script bound to the component behind.
In my tests, the issue occurred when the script was configured for onPointerUp event.
That issue did not occur when the script was configured for onPointerDown or onActionPerformed (and probably other) events.
I was testing in version 8.1.43.
Thank you for the wonderful video of the issue. I've opened an internal ticket to see what we can do about fixing this behavior.
@cmallonee is there any update on the internal ticket? Our team has encountered the same issue on version 8.1.53
@Eric.Nielsen No movement on the ticket; it has a relatively low priority because it only happens for a small subset of events.
Also, this thread has two issues, and the ticket is only for one of them because ( Dropdown option selection can trigger events for components under the option)
Can you please confirm which events are tied to the component behind the dropdown options which is registering user interaction when an option is clicked? If your issue is instead with the Dropdown displaying its options above the dropdown, there is only one way to mitigate that, and it is to force space always be available below your Dropdown.
@cmallonee Regarding the priority level, I understand. I can also confirm that our issue is that Dropdown option selection can trigger events for components under the option. The objects behind the dropdowns use onPointerUp most often, with a couple using onPointerDown. We have determined that for our hardware and need to support desktop with mouse and touch panel environments, pointer events are the most reliable vs click, touch, mouse events.
We do not care if the dropdown opens up or opens down, we appreciate the responsiveness of this functionality.
Good to know. I suspect we can prevent the events in question from triggering beyond the bounds of the Dropdown options when the ticket gets picked up - it's just a matter of when. I'll update the ticket to reflect additional interest.