v3.7.0

Supported markup change

The radio button control no longer supports data-initialize and $().radio() being bound to the div.radio class. This support has been removed. The radio (and checkbox in the future) control can only be bound to the label element now. This is a departure from the recommended markup provided by our documentation and by our Form Builder.

We wanted to support our documentation and our Form Builder that has been public for quite a while, but the team decided that having multiple binding options unnecessarily complicated the control and decided to fix binding to the label only so to stay consistent with the inline implementation.

This radio markup change is now documented.

I sincerely apologize for changing the recommended markup and will advocate limiting this kind of change in the future. Please update your radio and checkbox markup before upgrading. Otherwise, you will receive $().parent() element not found console errors.

Feature and bug fix release

There are "breaking changes" to undocumented public methods for tree and radio in this release. If you are only using methods that can be found in our documentation, then you have nothing to worry about.

New features

• Repeater disable methods and auto disable when loading #1235
• Add frozen column support to repeater list view. This feature is in beta. The implementation may change, but the API will be maintained. #1223

Bugfixes

• Make tree's openfolder only open folders instead of toggling them. This is a breaking change if you have using openFolder to toggle your folders instead of toggleFolder. #1145
• Radio button refactor. The following undocumented public methods have been removed from radio:
  setState, toggleContainer. Additionally, the radio and checkbox controls are now bound to the parent element with the respective .radio and .checkbox classes and no longer to the <input> element. #1195
• Add .hidden class to discloseVisible selector #1236
• Missed removing last occurrence of outline on checkbox #1228