There are cases when the agent decides to type in an "input" on a page, but it turns out to be a fake one. For example, on expedia, this "Date" label looks very much like an input
However, no input is focused after clicking it. Instead, it opens up a dialog expecting button clicking.
Typing in this case is tricky because it can trigger keyboard shortcut websites, or at least "space" would cause browser to scroll to next screen in Chrome.
There are cases when the agent decides to type in an "input" on a page, but it turns out to be a fake one. For example, on expedia, this "Date" label looks very much like an input![image](https://github.com/normal-computing/web-wand/assets/1001890/39e53d7e-0347-4ad4-837b-fbe4d6195450)
However, no input is focused after clicking it. Instead, it opens up a dialog expecting button clicking.
Typing in this case is tricky because it can trigger keyboard shortcut websites, or at least "space" would cause browser to scroll to next screen in Chrome.
We need to think of a way to handle this problem