issue: Tooltips are clipped on constrained containers and ExternalLink tooltip disappears when hovering over it

[tigerros]

• Tooltip component overflow is clipped, which is unwanted behavior when it comes to tooltips. Bug in question:

  

  The red lines are the padding of the black rectangle, inside of which is the ExternalLink (which uses tooltips).

• The ExternalLink tooltips disappear when user moves their mouse to the tooltip. Very annoying. Also present in feat: Add Link component back #411

[marc2332]

Weird, I thought I already fixed that, I'll take a look asap!

[marc2332]

Tooltip component overflow is clipped, which is unwanted behavior when it comes to tooltips. Bug in question:

Mmm, I am sorry but, what is the bug? I don't understand what exactly is being clipped

[marc2332]

Tooltip component overflow is clipped, which is unwanted behavior when it comes to tooltips. Bug in question:

Mmm, I am sorry but, what is the bug? I don't understand what exactly is being clipped

Seems to work just fine:

[tigerros]

@marc2332 This code:

fn app(cx: Scope) -> Element {
    render! {
        rect {
            width: "100",
            padding: "30",
            background: "yellow",
            ExternalLink {
                url: "https://github.com/marc2332/freya/",
                label {
                    "Freya"
                }
            }
        }
    }
}

Produces this:

[marc2332]

Ahh, I see, well, I guess that's a case I did not test.

The problem is that the tooltip doesn't have any space left. I think I could fix this by implementing viewport size units, this way I could use e.g 100vw (100% of the window width) in here, this way the Tooltip would have available space to render (It would still just take whatever size it needs, not the whole window width)

[tigerros]

Could the position be absolute and be set to the cursor's position? Wouldn't the tooltip ignore constraints that way?

[marc2332]

Could the position be absolute and be set to the cursor's position? Wouldn't the tooltip ignore constraints that way?

Nope, Skia requires you to pass always a width when creating text (it makes sense, it needs to know whether to break line, where to render, etc), and Freya, even when using absolute mode, you are still constrained by your parent sizing