-
Notifications
You must be signed in to change notification settings - Fork 2k
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
Help: Fix contact form tool tips #1456
Conversation
50304ac
to
f7ee720
Compare
@@ -108,6 +108,10 @@ Boolean representing the selected visual state. `selected={ true }` creates a bl | |||
|
|||
Optional URL to navigate to when option is clicked. | |||
|
|||
`title` | |||
|
|||
Optional title to show when hovering over segmented control options. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Might be good to mention that the child content of the item will be displayed unless this is specified.
I wonder if we need titles at all here, considering the content is already text. Visually it seems distracting and kinda pointless to just see repetition of the same text when you hover over an item. So I'd say 🚢 this to get the production issue fixed, but we should spend a little time to look into the repercussions of removing the title attribute entirely. |
…lp contact form. The titles will be the same as the labels.
f7ee720
to
5d01f1e
Compare
Help: Fix contact form tool tips
This pull request fixes #1433 by allowing
SegmentedControls
to use a custom title instead of the defaulttoString
that is implicitly called on the child nodes for each option.How to test:
This requires you be in a group that has no available operators so that you can see the kayako ticket form
What to expect
Fixes #1433