Hi Natasa,
This is because Orbeon Forms prevents the value of read-only fields from
being changed by any "event" coming from a browser. If that wasn't the case,
a malicious user could run that `setValue()`, say from the Chrome Dev Tools,
and thus modify a read-only field.
What is your logic for running the `setValue()`? I'm asking as I'm thinking
that it might be more secure for that logic to be written in XForms and use
an `xf:setvalue`.
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].
--
Follow Orbeon on Twitter: @orbeon
Follow me on Twitter: @avernet