I would benefit from allowing users to interact with my custom tooltips directly. Currently, as a user mouses around an area with custom tooltips available, if they move the mouse over a tooltip, it doesn't persist and will either redraw at the new mouse location or show the tooltip for a new parent visual filter context. I would like to see this behavior change to prevent additional updates until the user mouses out of the tooltip. By persisting the tooltip, it would allow me to add interactive elements to the tooltip (inspecting tooltip visuals, clicking bespoke navigational buttons).
Similarly, with this ability, it would seem natural to offer the ability to pin an open tooltip to prevent closing it, and allow the user to possibly move it to a specific portion of the window.
1 Comment
- fbcideas_migusrNew MemberStatus added:New
Recent ideas
Allow NotebookUtils getSecret() to authenticate with Workspace Identity
Current behavior In Microsoft Fabric, notebookutils.credentials.getSecret() authenticates against Azure Key Vault using the identity of the user who executes the notebook. This behavior appli...tmihara24 minutes agoNew MemberNew15Views1like1CommentAllow us to rename fabric data agents published to m365
If we use deployment pipelines to promote fabric data agents between dev, test/UAT, and prod fabric workspaces, we need to keep the name of the fabric agent the same in each workspace. If we want to ...PeterDaniels7 hours agoAdvocate IIINew184Views0likes2CommentsMake workspace and item session persistence optional
Description The new persistent session behavior in Microsoft Fabric should be optional rather than forced. Currently, Fabric remembers the workspaces and items that were open in my previous session...TeemuMultanen8 hours agoAdvocate INew296Views47likes2Comments