Is there an existing issue for this?

• I have searched the existing issues

What happened?

Today I upgraded my site to last version 10.2.0, and when try to open ckeditor options, im receiving an error "Options.js:19 Uncaught TypeError: $(...).buttonset is not a function". so ckeditor options window keeps blocked and is not possible to make any change.

Steps to reproduce?

1. I have installed version 10.1.2 for a new site
2. I have upgraded my site to new version 10.2.0
3. I placed a new html module in some page
4. I opened html editor, and then opened html editor options
5. Window for options is opened but keeps in waiting modal message.

Current Behavior

After open html options, new window keeps blocked (modal message), and is not possible to make any change for html module.

Expected Behavior

After open html options window, i should be able to make any change for the module. but is not possible for now

Relevant log output

Uncaught TypeError: $(...).buttonset is not a function
    at win.pageLoad (Options.js:19:23)
    at Sys._Application.raiseLoad (ScriptResource.axd?d=NJmAwtEo3IrguOqcsJYTA7BACCSXfpMS7HQ4xufQRcuEng71JsfC01jW7-Z6ARAJT_wY2yF_PLaWSxuHUbSOIfDfZdsztaA4M3rdRu4TiZnbRON66KKGq6bVLVj1Y0eVJtS-Hg2&t=5c0e0825:5:70713)
    at Sys._Application.initialize (ScriptResource.axd?d=NJmAwtEo3IrguOqcsJYTA7BACCSXfpMS7HQ4xufQRcuEng71JsfC01jW7-Z6ARAJT_wY2yF_PLaWSxuHUbSOIfDfZdsztaA4M3rdRu4TiZnbRON66KKGq6bVLVj1Y0eVJtS-Hg2&t=5c0e0825:5:70327)
    at b (ScriptResource.axd?d=NJmAwtEo3IrguOqcsJYTA7BACCSXfpMS7HQ4xufQRcuEng71JsfC01jW7-Z6ARAJT_wY2yF_PLaWSxuHUbSOIfDfZdsztaA4M3rdRu4TiZnbRON66KKGq6bVLVj1Y0eVJtS-Hg2&t=5c0e0825:5:71512)
    at HTMLDocument.a (ScriptResource.axd?d=NJmAwtEo3IrguOqcsJYTA7BACCSXfpMS7HQ4xufQRcuEng71JsfC01jW7-Z6ARAJT_wY2yF_PLaWSxuHUbSOIfDfZdsztaA4M3rdRu4TiZnbRON66KKGq6bVLVj1Y0eVJtS-Hg2&t=5c0e0825:5:71786)

Anything else?

I noticed version 10.2.0, replaced javascript library JQuery-UI from 01_13_03 to 01_14_01 then issue starting appear. Just as test, i replaced file jquery-ui.min.js from folder 01_13_03 to folder 01_14_01 and issue was resolved, but i think is not the correct way for now.

Affected Versions

10.2.0 (latest v10 release)

What browsers are you seeing the problem on?

Chrome

Code of Conduct

• I agree to follow this project's Code of Conduct