shodai80

3 ms·

1.
by shodai80 2y ago
#4 and #5 are using placeholder attributes, and the text itself is contained within the node. Show me a simple form with labels external of an input node, then rearrange the labels to be some above and some below, and I will be shocked! No
2.
by shodai80 2y ago
Yes if they are associated with accessibility attributes (Aria). Many, many sites including massive B2B do not do this (a shame). So no, you are seriously minimizing the problem. This approach would also be architecturally poorly thought ou
3.
by shodai80 2y ago
Provided screenshots below do not show textboxes, selects, or other input nodes with labels. Show me text output with associated labels for inputs being correct and I will be shocked.
4.
by shodai80 2y ago
My point still stands. How do you augment data for an LLM when you know the context of a page? Do you go through every element and setup the data for an associated label? Do you use div scoping via offset parent through a script to generate
5.
by shodai80 2y ago
I understand that, I assume you are tagging the node and making a basic xpath to the node/attribute with your tag id. Understood. But how relevant is tagging a node when I have no idea what the node is actually for? EX: Given a simple
6.
by shodai80 2y ago
How do you know, for a specific webelement, what label it is associated with for a textbox or select? For instance, I might want to tag as you did where elements are, but I still need an association with a label, quite often, to determine w