You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Alright, I've done some digging and this appears to be... intentional?
Surely this is leftover code, right? Captured this and tracking which span is pressed doesn't seem to be used at all. It's not even available to the user. Maybe I'm missing something?
Rich text can include links, which is handled as part of the widget (you missed this, the selected span is used just a few blocks beneath your link).
Indeed, a better solution would be to only intercept the input if the selected span is a link.
Is your issue REALLY a bug?
Is there an existing issue for this?
Is this issue related to iced?
What happened?
I've noticed that clicking a rich-text element embedded inside a button does not trigger the
on_press
.MRE (forgive unnecessary use of
daemon
):In the above example, clicking on the first text element causes the button to be clicked, but clicking the spans does not.
What is the expected behavior?
Clicking any area of the button should yield the appropriate event.
Version
crates.io release
Operating System
Both Windows and Linux (X11) were tested.
Do you have any log output?
No response
The text was updated successfully, but these errors were encountered: