Suppress/Set prefix for id of xforms controls?

[Jens Thorsten Stumpf]

Hi there,

in former versions I was able to do something like

   <xforms:input ref="remarks/@quality" id="remark-quality"/>

which yielded something like

    <span id="remark-quality" class="xforms-control xforms-input">
        <input id="remark-quality≡xforms-input-1" class="xforms-input-input" type="text" value="" name="remark-quality≡xforms-input-1">
    </span>

Since I'm using Orbeon CE 4.8 there seems to be a slight change in behaviour:

    <span id="xf-10≡xf-25≡remark-quality" class="xforms-control xforms-input">
        <input id="xf-10≡xf-25≡remark-quality" class="xforms-input-input" type="text" value="" name="xf-10≡xf-25≡remark-quality">
    </span>

Obviously the modified id is rather useless and can't be predicted outside of orbeon.

How can I return to the old behaviour which used the defined id without any computed prefix?
Though I think it is generally a good and valueable idea to make the fields unique I think there should at least be a choice to disable it on some controls or for a complete form: If one defines an id it's very reasonable to argue it is going to be used for any purpose - e.g. for styling.
It seems to me that an id has to be unique per definitionem - so anybody who violates this rule is on his own.

Regards,

Jens

[Erik Bruchez]

Jens,

We have a related issue:

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

It's not possible to return to the old behavior without addressing #1136.

-Erik

--
View this message in context: http://discuss.orbeon.com/Suppress-Set-prefix-for-id-of-xforms-controls-tp4659951p4659955.html
Sent from the Orbeon Forms community mailing list mailing list archive at Nabble.com.

[Jens Thorsten Stumpf]

Erik,

Thank you very much for your quick response!

I did a search for id and prefix but couldn't find the issue.
As far as I can see this ticket exists for 2 years - I guess the chances for being addressed/fixed (soon) are quite low...

Is there a chance to fix that myself (by reverting to the old schema or even implementing the described behavior) with not to much effort or will that provoke a lot of side effects? If it seems reasonable/doable, can you give me a short intro where to start?

Thank you very much for your quick response,

Jens

--
You received this message because you are subscribed to a topic in the Google Groups "Orbeon Forms" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/orbeon/v7L0AhxQlNI/unsubscribe.
To unsubscribe from this group and all its topics, send an email to orbeon+un...@googlegroups.com.
To post to this group, send email to orb...@googlegroups.com.

[Erik Bruchez]

Jens,

I wouldn't despair to fix it, but it is quite a bit of work, which is why we
haven't addressed it yet.

I would say there is little chance of managing to fix it yourself unless you
want to become the absolute Orbeon Forms guru (which we would welcome!),
because this touches the core of the XForms engine and id handling. It is
the internal allocation of ids, and then resolution of those ids, which is
impacted, and that can be quite tricky.

-Erik

--
View this message in context: http://discuss.orbeon.com/Suppress-Set-prefix-for-id-of-xforms-controls-tp4659951p4659959.html