Skip to content

Conversation

@LaansDole
Copy link
Contributor

This will resolve #520

Key Changes:

  • New RichTooltip.vue component with keyboard navigation, hover persistence, and smart positioning
  • Centralized help content system in helpContent.js for all node types, edges, and UI actions
  • Enhanced form fields with contextual help tooltips (DynamicFormField, FormGenerator)
  • Improved workflow editor UX with tooltips on nodes, edges, and context menu actions
  • Updated tutorial content and routing

@zxrys zxrys self-requested a review February 9, 2026 09:15
@zxrys zxrys assigned zxrys and LaansDole and unassigned zxrys Feb 9, 2026
@zxrys
Copy link
Collaborator

zxrys commented Feb 9, 2026

Thanks for the solid implementation here — this is a meaningful UX improvement and very close to merge-ready! Here are two small follow-ups before merge:

  1. For user-defined/custom node types, the current tooltip fallback (“Help content coming soon.”) is not ideal.
    I suggest either:
  • no tooltip for unknown/custom types, or
  • explicitly limiting built-in help content to built-in node types only.
  1. The Python node help text says: “Executes Python code in a sandboxed environment.”
    That is inaccurate for this project’s local deployment model. Python runs directly on the local environment (not sandboxed), so this wording should be updated to reflect actual behavior and avoid giving a false security impression.

@LaansDole
Copy link
Contributor Author

Thanks for the solid implementation here — this is a meaningful UX improvement and very close to merge-ready! Here are two small follow-ups before merge:

  1. For user-defined/custom node types, the current tooltip fallback (“Help content coming soon.”) is not ideal.
    I suggest either:
  • no tooltip for unknown/custom types, or
  • explicitly limiting built-in help content to built-in node types only.
  1. The Python node help text says: “Executes Python code in a sandboxed environment.”
    That is inaccurate for this project’s local deployment model. Python runs directly on the local environment (not sandboxed), so this wording should be updated to reflect actual behavior and avoid giving a false security impression.

I have udpated accordingly

@zxrys
Copy link
Collaborator

zxrys commented Feb 10, 2026

Thanks for addressing the previous round of feedback so quickly — the updates are appreciated! One more UX request before merge:

Could we add a user setting to globally enable/disable help tooltips?

  • Default: ON (good for onboarding)
  • Option: users can turn it OFF (for experienced users / less visual noise)

This should live in Settings (same place as AUTO_SHOW_ADVANCED / AUTO_EXPAND_MESSAGES) and be persisted in configStore/localStorage.
(Existing settings files: frontend/src/utils/configStore.js and frontend/src/components/SettingsModal.vue.)

Suggested key name: ENABLE_HELP_TOOLTIPS (default true).

When disabled, we should bypass RichTooltip rendering across workflow UI (node tooltips, edge tooltip trigger, context-menu/action button tooltips), while keeping all existing behavior unchanged when enabled.

Also, I noticed the edge tooltip position seems incorrect right now (it’s not rendering at the edge/midpoint as expected). Could you take a look at that in this PR as well?

@LaansDole
Copy link
Contributor Author

I have moved it to config options in settings, and the tooltip should be more in the middle now

Copy link
Collaborator

@zxrys zxrys left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

looks good to me

@zxrys zxrys merged commit 4a6ee25 into OpenBMB:main Feb 11, 2026
@LaansDole LaansDole deleted the feat/tooltip-enhancement branch February 11, 2026 11:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Feature Request: Interactive Component Tooltips

2 participants