Skip to content
Merged
Show file tree
Hide file tree
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion core/src/main/resources/lib/form/radio.jelly
Original file line number Diff line number Diff line change
Expand Up @@ -38,7 +38,7 @@ THE SOFTWARE.
<st:attribute name="checked" />
<st:attribute name="value" />
<st:attribute name="id" />
<st:attribute name="onclick" />
<st:attribute name="onclick" deprecated="true">onclick handler. Deprecated; assign an ID and look up the element that way to attach event handlers.</st:attribute>
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

may be better to use class name as repeatable elements don't work properly with IDs from what I remember.

IDs are safe to use in standalone pages / configuration forms that won't be used in repeatable elements

<st:attribute name="title">
If specified, this human readable text will follow the radio, and clicking this text also
toggles the radio.
Expand Down
6 changes: 6 additions & 0 deletions core/src/main/resources/lib/form/readOnlyTextbox.jelly
Original file line number Diff line number Diff line change
Expand Up @@ -62,6 +62,12 @@ THE SOFTWARE.
If @field is specified, this will be inferred automatically,
which is the recommended approach.
</st:attribute>
<st:attribute name="onchange" deprecated="true">
onchange handler. Deprecated; assign an ID and look up the element that way to attach event handlers.
</st:attribute>
<st:attribute name="onkeyup" deprecated="true">
onkeyup handler. Deprecated; assign an ID and look up the element that way to attach event handlers.
</st:attribute>
</st:documentation>
<f:prepareDatabinding />
<input class="jenkins-input ${attrs.checkUrl!=null?'validated':''} ${attrs.clazz}"
Expand Down