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
This was something brought up in the RHOAI PF v6 migration UI review, but looks like it's also something that was present in v5 as well. Basically a tooltip seems to only get triggered when the text of a node itself is hovered, rather than when the node is hovered. Note in the video below the tooltip for a truncated node triggers only when the cursor hovers the text; there's the area around the text (but within the node outline) where the tooltip is not triggered (recording is from a cluster using PF v5, but this is present in the v6 migration, too):
Screen.Recording.2024-11-22.at.2.56.16.PM.mov
The text was updated successfully, but these errors were encountered:
@thatblindgeye I believe this is intentional. It has been this way for a long time anyhow. @andrew-ronaldson Any thoughts? Badges have their own tooltip so I'm not sure we want the tooltip on the entirety of the node.
We did design it the way Jeff described so the badges could show their own info. I believe it was RHTAP that showed the results of vulnerability scans.
This was something brought up in the RHOAI PF v6 migration UI review, but looks like it's also something that was present in v5 as well. Basically a tooltip seems to only get triggered when the text of a node itself is hovered, rather than when the node is hovered. Note in the video below the tooltip for a truncated node triggers only when the cursor hovers the text; there's the area around the text (but within the node outline) where the tooltip is not triggered (recording is from a cluster using PF v5, but this is present in the v6 migration, too):
Screen.Recording.2024-11-22.at.2.56.16.PM.mov
The text was updated successfully, but these errors were encountered: