-
-
Notifications
You must be signed in to change notification settings - Fork 531
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Tooltip issues #4887
Comments
Most of this is a request for Bokeh. I certainly agree that the timeout is too long and clicking shouldn't have any effect. |
Note that plain text (string) description uses HTML's input_widget.description = "string" and input_widget.description = Tooltip(content="string") are not equivalent. |
Maybe I don't know how to use it correctly, but this doesn't work for me at all:
No tooltip is ever shown. |
Nevermind, had to provide a position. I'll probably switch to explicit tooltips immediately. |
Much better: ![]() That said, when used on a server this causes serialization errors:
Seems to originate here, where you're setting the actual DOM element as an attribute of the Model: https://github.com/bokeh/bokeh/blob/branch-3.2/bokehjs/src/lib/models/widgets/input_widget.ts#L78 |
Was able to resolve that by setting |
Setting |
The API of tooltips is not well refined. Setting |
I have a complicated app with one
and then the app would become inoperable (as if the front end was no longer connected to the backend, buttons no longer triggered callbacks, etc). After seeing the discussion above, I removed the instance of Panel v1.4.5 |
The new tooltips on widgets in Panel 1.0 are great! However, the UX isn't quite right, because hovering over the (?) takes so long that I reflexively click on the (?), which then stops the hover text from appearing. I think the delay should be maybe half what it is, and clicking on it should make the tooltip first appear, then (if clicked again) disappear, rather than suppress it silently without ever having shown it. That's probably a Bokeh issue rather than Panel, but maybe Panel sets the defaults.
Also, I think Panel or Param should strip out leading spaces that appear either on all lines of the doc or on all but the first line, so that docstrings can be formatted naturally in the code but also display naturally in the UI:
The text was updated successfully, but these errors were encountered: