Bug with select1 and alert icons

I believe I've identified a bug specific to select components and the
use of the external xf:alert tag and the for attribute.  When you open
the attached in Orbeon, you should see the behavior that I am seeing
with Orboen 4.7CE.  I see 2 alert icons for the first question, and only
1 alert icon for the second.  The use case involves having a warning
tripped on form load, and the use of xf:alert tag outside of the
control.  I've attached a screenshot as well.  I'm guessing this
behavior is not by design.  If there is a better place to submit bug
reports to, please let me know.

Thanks,

--
_____________________________________________
Jeremy Nix
Senior Application Developer
Biomedical Informatics
Cincinnati Children's Hospital Medical Center
513-803-2764 / [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].

Thanks for reporting. It does look like a bug and I updated the issue with a simpler example and some comments.

Do you have a workaround for this, or is it a blocker?

-Erik

I do not have a workaround currently as I haven't focused heavily on
it.  I would not consider this a blocker, as my users have not
complained yet. :)  I did try to come up with a few workarounds, but no
such luck.  If you can think of any before a fix is in place, please let
me know.

I appreciate the help.

_____________________________________________
Jeremy Nix
Senior Application Developer
Biomedical Informatics
Cincinnati Children's Hospital Medical Center
513-803-2764 / [hidden email]

On 12/23/2014 02:56 PM, Erik Bruchez wrote:
--
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].

Got it. I can't think of a workaround either. It's probably an issue to fix in the form engine proper.

-Erik