Improve "Record Selector" keyword and docs

[brazdauskasv]

• "box" word in the docs is not super clear, we might want to change it to "dialog" or "interface"

• Keyword is is not intended to work in headless=True mode (results in an error, which tells exactly that) - we could write it in the docs)

• "Cancel" button resets the timer, so you can hover on the element again if you were not quick enough. - (again, maybe we should put that info in the docs?)

• "Select" button picks the selector and returns it - maybe should be mentioned in the docs as well

• Adjustable timer (maybe with an argument) would be a great addition to the keyword as well (with the current timer you kinda have to be quick, so this results in more retries and time wasted)

Some images for reference:

[brazdauskasv]

URL to documentation - https://marketsquare.github.io/robotframework-browser/Browser.html#Record%20Selector

[brazdauskasv]

Note: I plan to work on this myself. Haven't figured out how to assign myself to it yet (maybe lack of permissions??)

[aaltat]

I assigned the issue for you, please note that keyword documentation is created from source and in Record Selector case, you should change it in here:

robotframework-browser/Browser/keywords/interaction.py

Line 453 in 9f85a4f

def record_selector(

@allcontributors please add @brazdauskasv for bugs.

[allcontributors]

@aaltat

I've put up a pull request to add @issue! 🎉

[aaltat]

"box" word in the docs is not super clear, we might want to change it to "dialog" or "interface"

I do agree, box is wrong word.

* Keyword is is not intended to work in headless=True mode (results in an error, which tells exactly that) - we could write it in the docs)

We should say it.

* "Cancel" button resets the timer, so you can hover on the element again if you were not quick enough. - (again, maybe we should put that info in the docs?)

This is an new implementation or what you mean? Could you clarify?

* "Select" button picks the selector and returns it - maybe should be mentioned in the docs as well

We should tell this one too

* Adjustable timer (maybe with an argument) would be a great addition to the keyword as well (with the current timer you kinda have to be quick, so this results in more retries and time wasted)

Yes, changing the timeout could be good idea. As an argument to keyword.

Feel free to make the changes.

[brazdauskasv]

• "Cancel" button resets the timer, so you can hover on the element again if you were not quick enough. - (again, maybe we should put that info in the docs?)

@aaltat Currently cancel simply restarts the timer and you can try to hover on the element again.
Now that I think about it "Cancel" should probably be renamed to "Retry".

[aaltat]

Next sounds more logical name to me too, let’s take that one too

[brazdauskasv]

@aaltat I think it depends on how you use it.
If you just keep reusing it during keyword execution and copy paste selectors elsewhere, then "Next" makes sense.
Personally that is how I would use it.

But originally keyword returns only one selector which is selected.
Having "Next" button might suggest that a list of selectors will be returned - It's not how it currently works.

I've added a recording to show how it currently works.
https://github.com/user-attachments/assets/afe5b9f7-b22c-4721-aba2-610c854f5909

[brazdauskasv]

Or we could change "Cancel" to "Next" and then write in the docs something like:
"Only a last recorded selector will be returned after "TAKE IT" button is clicked."

[aaltat]

Sounds like a good idea for me.