Hints - difference from version 3.9 to 2018.1

One of our customers has noted a difference between our old system based on
version 3.9 of orbeon and the current one.

When you have a hint on a control in version 3.9, it was seen as a hover
over the control in both edit and view modes but in version 2018.1 the hints
are seen below the control in edit mode and are not seen at all in view
mode.

I'm assuming that this was an intentional design decision based on the UX
Collective's design better forms article recommendation to not hide basic
helper text (which think makes perfect sense).

The customer is complaining that the hint text needs to be seen by viewers
of the form as well as editors. I disagree for a couple of reasons

1) that is not the purpose of the hint text, it is help for a form
creator/editor
2) it won't appear in the pdf and so won't export or print causing a loss of
information for a user who has a pdf version of the form.

I need to convince them of this. My take on it is that if they want
additional information in the viewed/printed form then they should be using
an explanatory text field.

Do you have any other points that could help my argument?

And since I will be asked, would you consider changing the behaviour so
hints are visible in view mode?

thanks
brian...

brian...


--
Sent from: http://discuss.orbeon.com/

--
You received this message because you are subscribed to the Google Groups "Orbeon Forms" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To post to this group, send email to [hidden email].

I've noticed an inconsistency here as well. When you have hints on checkbox
and radiobutton items they do display when viewing the form if you hover of
the options but the hints for the control are not displayed at all.

--
Sent from: http://discuss.orbeon.com/

--
You received this message because you are subscribed to the Google Groups "Orbeon Forms" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To post to this group, send email to [hidden email].

and another. When an option has a hint it also gets a dotted underline. This
underline is also present in view mode and in the PDF but the hint text
itself is not in the PDF.


--
Sent from: http://discuss.orbeon.com/

--
You received this message because you are subscribed to the Google Groups "Orbeon Forms" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To post to this group, send email to [hidden email].

Hi Brian,

Hopefully how things work out-of-the-box makes sense in most case, but I
certainly wouldn't try to argue that what is done out-of-the-box if best in
all cases. For the hint not being shown in view mode, I can see how it might
be better to have the hint still in DOM but by default hidden with CSS, so
if one were to show it, they could do so by adding CSS.

I think however that there is no point in the PDF showing the dotted
underline for radio buttons or checkboxes. I've created an issue to change
this (see  #3649 <https://github.com/orbeon/orbeon-forms/issues/3649>  ).

<http://discuss.orbeon.com/file/t119778/Dotted_hhint_in_PDF.png>

Alex

-----
--
Follow Orbeon on Twitter: @orbeon
Follow me on Twitter: @avernet
--
Sent from: http://discuss.orbeon.com/

--
You received this message because you are subscribed to the Google Groups "Orbeon Forms" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To post to this group, send email to [hidden email].

Hi Alex,
  Hidden but present with the ability to make it visible via CSS is an
interesting idea. Currently (as far as I could see) the hints on controls
are not present in the html at all.

What about the inconsistency of the hints for controls not being present in
view mode but the hints for checkbox/radiobuttons still popping up in view
mode?

I would think these (and their underlines) should not be visible in view
mode by default but might be present and CSS enableable?

Any chance of this behaviour changing prior to 2018.1 release? I need to
have a story to tell our customer who has asked (although this is not a top
priority, having the release is more important to me).

thanks
brian...

--
Sent from: http://discuss.orbeon.com/

--
You received this message because you are subscribed to the Google Groups "Orbeon Forms" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To post to this group, send email to [hidden email].

Hi Brian,

Yes, it makes sense. So I made that change, and it will be in 2018.1. For
more on this, see the issue linked below, and you'll let me know if I missed
anything.

https://github.com/orbeon/orbeon-forms/issues/3652

Alex

-----
--
Follow Orbeon on Twitter: @orbeon
Follow me on Twitter: @avernet
--
Sent from: http://discuss.orbeon.com/

--
You received this message because you are subscribed to the Google Groups "Orbeon Forms" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To post to this group, send email to [hidden email].

--
You received this message because you are subscribed to the Google Groups "Orbeon Forms" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To post to this group, send email to [hidden email].

Hi Alexander,

In the HTML of the page you point to, on the `<form>` you have a class
`xforms-hint-appearance-full`, so it looks like you haven't set the hints to
show as tooltips. You can do so by adding the following property:

<property as="xs:string" name="oxf.xforms.hint.appearance" value="tooltip"/>

When testing this locally with a minimal XForms example I created, after
adding this property the tooltip shows as expected. The documentation says
the default value is `full` (see link below), and this has been the case for
a while, but is it possible that a while ago the default was `tooltip`, or
that the property didn't exist and `tooltip` was the only possibility?

https://doc.orbeon.com/xforms/controls/input

Anyhow, you'll let me know if setting the above property works for you.

‑Alex

-----
--
Follow Orbeon on Twitter: @orbeon
Follow me on Twitter: @avernet
--
Sent from: http://discuss.orbeon.com/

--
You received this message because you are subscribed to the Google Groups "Orbeon Forms" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To post to this group, send email to [hidden email].

--
You received this message because you are subscribed to the Google Groups "Orbeon Forms" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To post to this group, send email to [hidden email].

Excellent Alexander, and thank you for the confirmation.

‑Alex

-----
--
Follow Orbeon on Twitter: @orbeon
Follow me on Twitter: @avernet
--
Sent from: http://discuss.orbeon.com/

--
You received this message because you are subscribed to the Google Groups "Orbeon Forms" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To post to this group, send email to [hidden email].