Attachments

Activity

Starting with Active Choices v2.0, sandboxed Groovy scripts for Active Choices Reactive Reference Parameter will no longer emit HTML that is considered unsafe, such as <script> tags. This may result in behavior changes on Build With Parameters forms, such as missing elements. To resolve this issue, Groovy scripts emitting HTML will need to be configured to run outside the script security sandbox, possibly requiring separate administrator approval in In-Process Script Approval.

Ioannis Moutsatsos
added a comment - 2017-12-28 22:38 Starting with Active Choices v2.0, sandboxed Groovy scripts for Active Choices Reactive Reference Parameter will no longer emit HTML that is considered unsafe, such as <script> tags. This may result in behavior changes on Build With Parameters forms, such as missing elements. To resolve this issue, Groovy scripts emitting HTML will need to be configured to run outside the script security sandbox, possibly requiring separate administrator approval in In-Process Script Approval .

The <script .../> HTML tags do appear in the DOM but are not being executed. Even DOM elements referring to functions defined in these <script... /> blocks (i.e. onclikck="func();") fail with function not found.

I see the last comment (above, from 19-Feb-2019 by Ioannis Moutsatsos) states it had been fixed. I'm using the plugin from the main Jenkin repo.

Any suggestions how to bypass this?

Currently I'm writing the entire JS code in the onlick="..." event of the button I'm showing (which works).

Omri Sela
added a comment - 2019-06-13 14:30 I'm currently experimenting with AC v2.1 and facing the same problem.
The <script .../> HTML tags do appear in the DOM but are not being executed. Even DOM elements referring to functions defined in these <script... /> blocks (i.e. onclikck="func();") fail with function not found.
I see the last comment (above, from 19-Feb-2019 by Ioannis Moutsatsos ) states it had been fixed. I'm using the plugin from the main Jenkin repo.
Any suggestions how to bypass this?
Currently I'm writing the entire JS code in the onlick="..." event of the button I'm showing (which works).