iced::widget::tooltip + iced::widget::focus_next -> unexpected behavior

[g-braeunlich]

Is your issue REALLY a bug?

• My issue is indeed a bug!
• I am not crazy! I will not fill out this form just to ask a question or request a feature. Pinky promise.

Is there an existing issue for this?

• I have searched the existing issues.

Is this issue related to iced?

• My hardware is compatible and my graphics drivers are up-to-date.

What happened?

Putting a text_input inside a tooltip seems to remove the text_input from the focus chain traversed by focus_next.
I guess that happens because tooltip has a blank operate in the Widget impl.

It is still possible to set the focus on the text_input by clicking on it. Using focus_next when text_input (still inside tooltop) has focus results in a state where 2 widgets have focus at the same time (typing on the keyboard enters text in both inputs at the same time).

What is the expected behavior?

The text_input should be focussable via focus_next if it is placed inside a tooltip.

Example:
iced-tooltip-focus-bug.zip

Version

crates.io release

Operating System

Linux

Do you have any log output?

[mfreeborn]

The tooltip widget appears to be missing a Widget::operate implementation, which is why the wrapped text_input isn't seeing the focus operation.

I've just tried a naive implementation for tooltip that looks like this:

fn operate(
    &mut self,
    tree: &mut widget::Tree,
    layout: Layout<'_>,
    renderer: &Renderer,
    operation: &mut dyn widget::Operation,
) {
    operation.container(None, layout.bounds());
    operation.traverse(&mut |operation| {
        self.content.as_widget_mut().operate(
            &mut tree.children[0],
            layout.children().next().unwrap(),
            renderer,
            operation,
        );
    });
}

...and whilst that fixed it for me for text_inputs, I'm now getting a panic when I wrap a button in a tooltip:

thread 'main' (101393) panicked at /home/michael/.cargo/git/checkouts/iced-67f36dcf1810c33e/0ae6ce4/widget/src/button.rs:268:42:
called `Option::unwrap()` on a `None` value

which is this line here.

I'm not 100% sure what I'm missing...

[edwloef]

It needs to be

fn operate(
    &mut self,
    tree: &mut widget::Tree,
    layout: Layout<'_>,
    renderer: &Renderer,
    operation: &mut dyn widget::Operation,
) {
    operation.container(None, layout.bounds());
    operation.traverse(&mut |operation| {
        self.content.as_widget_mut().operate(
            &mut tree.children[0],
            layout,
            renderer,
            operation,
        );
    });
}