> Copying my comments from bug #1248487:
>
> « I’m not proposing that open_toolbar close it first, I’m proposing that if
> it’s already open the emulator does some sort of interaction with it (details
> to be figured out) to ensure it won’t autohide.
>
> Your proposal works for click_button(), but what if I want to interact
> differently with the toolbar. E.g., what if the toolbar contains a TextField,
> or some other widget? I will still want to ensure that when I call
> open_toolbar(), it remains open. »
The current design specs say that if it is not interacted with for 5 seconds it should close. So I don't know how to incorporate that with your requirement.
> Copying my comments from bug #1248487:
>
> « I’m not proposing that open_toolbar close it first, I’m proposing that if
> it’s already open the emulator does some sort of interaction with it (details
> to be figured out) to ensure it won’t autohide.
>
> Your proposal works for click_button(), but what if I want to interact
> differently with the toolbar. E.g., what if the toolbar contains a TextField,
> or some other widget? I will still want to ensure that when I call
> open_toolbar(), it remains open. »
The current design specs say that if it is not interacted with for 5 seconds it should close. So I don't know how to incorporate that with your requirement.
Do you currently have a use case?