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
For selection controls, new help/hint on items – In the XForms engine, we will add the support for help and hint on items (xf:item for selection controls). The help or hint on an item will only be visible for appearance="full" selection controls (radio buttons and checkboxes) for instance as shown below, and only the tooltip and popover appearances will be supported.
Help/hint attached to part of the label – Allowing the message to be specific to a part of the label. This will be supported only if the label is in HTML. This will be supported only for the tooltip and popover appearances, as in that case, the tooltip or popover will show when the mouse is over that specific part of the message, by default highlighted with dotted underlining, as shown below. Issue Hints for radio buttons and checkboxes attached to only part of the label #1522 now covers this item.
FB: ability to enter a message for items – The itemset editor will allow form authors to capture a message for items, which will be mapped to either a hint or a help in the edited XForms (maybe configurable, TBD).
After 2010-10-07 brainstorm, we have decided that tooltips on items should look ok as long as the arrow points to the text. This involves:
hint has added <span> around label text
this is necessary because <label> is display: block and takes the whole cell width
with this, the tooltip can point properly to the text and not empty space
if only subset of item to hint, then <span> is around that
items with tooltips are underlined by default
server and client must put class to indicate "non-empty hint" condition
Non-requirements
This RFE does not cover the following cases, not because they don't make sense but because implementing them would add a significant amount of complexity. This of course doesn't close the door to also supporting those use cases in the future.
We won't have the ability to have multiple (different) messages attached to different words of the same label or item.
This feature is split out of #1081.
For selection controls, new help/hint on items – In the XForms engine, we will add the support for help and hint on items (
xf:item
for selection controls). The help or hint on an item will only be visible forappearance="full"
selection controls (radio buttons and checkboxes) for instance as shown below, and only the tooltip and popover appearances will be supported.Help/hint attached to part of the label – Allowing the message to be specific to a part of the label. This will be supported only if the label is in HTML. This will be supported only for the tooltip and popover appearances, as in that case, the tooltip or popover will show when the mouse is over that specific part of the message, by default highlighted with dotted underlining, as shown below. Issue Hints for radio buttons and checkboxes attached to only part of the label #1522 now covers this item.
FB: ability to enter a message for items – The itemset editor will allow form authors to capture a message for items, which will be mapped to either a hint or a help in the edited XForms (maybe configurable, TBD).
After 2010-10-07 brainstorm, we have decided that tooltips on items should look ok as long as the arrow points to the text. This involves:
<span>
around label text<label>
isdisplay: block
and takes the whole cell width<span>
is around thatNon-requirements
This RFE does not cover the following cases, not because they don't make sense but because implementing them would add a significant amount of complexity. This of course doesn't close the door to also supporting those use cases in the future.
Implementation tasks
XForms engine:
Form Builder:
The text was updated successfully, but these errors were encountered: