How to Handle "Non-Standard Dropdown Selection" Components?

[wuh-watson]

In actual websites, there may be components that appear to be select options but are actually custom implementations of input fields, dropdown lists formed with ul+li or div elements, and even multiple linked selections for organizations/addresses, where the structure might even take the form of a tree.

[suchintan]

are they represented as clickable elements at all? Do they change on hover?

Do you have a live website example?

[wuh-watson]

are they represented as clickable elements at all? Do they change on hover?

Do you have a live website example?

Thanks for your replying
I'm sorry, but I can't provide a website right now. However, I have a screenshot that can help understand the interactions of this complex custom component.
When you click a button or some input fields, a popup window may appear, within a Single Page. Inside this window, there are multiple elements of a form, such as the Department and Role shown in the screenshot, which have a relational connection.
My question is, how should I describe this in prompt so that the AI can finish these forms? Or, is it currently possible to support such complex interactions?

[wintonzheng]

@wuh-watson are you running your prompt with a single task? have you tried building a workflow for it?

[wuh-watson]

@wuh-watson are you running your prompt with a single task? have you tried building a workflow for it?
run with workflow.
Because it is an internal page, I cannot share it. Through debugging, I found two issues:

1. When using front-end frameworks like React/Vue, there will be many non-standard input elements, meaning it looks like an input or select, but the actually interactive elements are div/li/label, etc.
2. Skyvern did not fully recognize the operation steps of the pop-up dialog triggered by an input. For example, if the dialog has multi-step related operations, such as input search or tree selector, selecting one option could reveal additional choices, possibly 3 to 5 selections, like filling out an address.

[chloecd]

In actual websites, there may be components that appear to be select options but are actually custom implementations of input fields, dropdown lists formed with ul+li or div elements, and even multiple linked selections for organizations/addresses, where the structure might even take the form of a tree.

same situation here. Dropdown lists show after click the dropdown button, and there is no "father-and-son" relationship between them. Dropdown lists are arranged in the same frame as "li" or "div" elements.