Pekka Klärck

Can already tell at this point that there's not enough time for this kind of cleanup in RF 3.1. Descoping.

Issues #3025 and #3062 demonstrate that a cleaner API to register "run keywords" is definitely needed. It needs to be mentioned in the User Guide as well.

RF 3.2 is so long overdue that this is unfortunately descoped. If someone would really like this in, please comment here.

Issue #3859 demonstrates that using `BuiltIn.run_keyword` without telling Robot about it causes problems with logging when using timeouts. Yet another reason to get this issue done at some point.

Information about keywords running other keywords would be also valuable outside the core framework. For example, LSP plugin would then recognize keyword names in arguments of other keywords and provide...

This feature won't make it to RF 5.0. It's annoying to descope this again, but we both want to get that release out soon and it's still a bit unclear...

Keywords registered to Robot's current "run keyword register" have some special features explained below. 1. These keywords won't be stopped by timeouts. The reason is that we only want to...

This looks pretty strange. I cannot run the example without modifications myself and don't have time to create a simpler example myself now. I'll look at this again after my...

I tested this with the following very simple library and couldn't reproduce the problem. Element `css:h1` used below existed but I also tested with `css:h5` that doesn't and in both...

I couldn't reproduce the issue and there hasn't been new info in a week. Closing now. Can be reopened if there's new info that indicates there's a bug on Robot...