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
I am building a demo around an ML model, and need to explain the features I use to a broad audience. This means that ideally, I need a dedicated place to describe what each feature means.
I really like the tooltip option for streamlit input widgets, so I’d love to use the same widget within my markdown and elsewhere (e.g. in the dataframe header) - I have a list of feature names and be able to set a tooltip question mark with an explanation on hover near it. I know there are a few ways different markdown flavors do something like that. The way I see it it could be something like that:
st.markdown('''
- first feature ?[:question:](Tooltip text for the first feature)
- second feature ?[:exclamation:](Tooltip text for the Second feature)
''')
Hey @Casyfill, thanks for sharing this! I'm going to close this as a duplicate of #5355, but I've copied your thoughts above and added them to that thread. Please upvote #5355 so we know to prioritize it. Thanks!
I am building a demo around an ML model, and need to explain the features I use to a broad audience. This means that ideally, I need a dedicated place to describe what each feature means.
I really like the tooltip option for streamlit input widgets, so I’d love to use the same widget within my markdown and elsewhere (e.g. in the dataframe header) - I have a list of feature names and be able to set a tooltip question mark with an explanation on hover near it. I know there are a few ways different markdown flavors do something like that. The way I see it it could be something like that:
The text was updated successfully, but these errors were encountered: