[bugfix] Prioritize jQuery UI scripts in "assets.javascripts" config in order to avoid initialization issues

[phansys]

I am targeting this branch, because this guards BC.

Changelog

### Changed
- Default load order of `assets.javascripts` at `Configuration::getConfigTreeBuilder()`
### Fixed
- ECMAScript error `jquery.js:250 Uncaught Error: cannot call methods on button prior to initialization;` while trying to use `$.fn.button()` (ref: https://github.com/twbs/bootstrap/issues/6094)

Todo:

• Check if changes made at 359ce81 can be reverted (using noConflict() instead).

[kunicmarko20]

I guess we can't know if this will break something else

[phansys]

I'm afraid we can't.

[jordisala1991]

#5047

we changed this a few PRs ago... does this PR revert the older one?

[phansys]

does this PR revert the older one?

That seems to be true. Then, I'll try to make some tests around noConflict() approach and will be back with the results. Thank you for pointing the previous change ;)

[jordisala1991]

Prevent accidental merge

[kunicmarko20]

and it looked familiar but I wasn't sure 😅

[phansys]

@verheyenkoen, are you sure the only way to fix the issue you've reported on #5047 is to change the order of the scripts? AFAIK, the embedded version of jQuery doesn't support noConflict() (Bootstrap does, see twbs/bootstrap#6094 (comment)), so with your PR, I'm not able to use features from button: jquery.js:250 Uncaught Error: cannot call methods on button prior to initialization;.
Thank you in advance.

[verheyenkoen]

@phansys I don't know. This is a fix I found. If it's no good I guess we have to revert it.

[phansys]

Ok, let me do some checks in order to determine how we could make both fixes to co-exist.

[phansys]

AFAIK, there is no way to solve both issues without reverting the changes at #5047 and using some of the alternatives proposed on SO (https://stackoverflow.com/a/20391739 by instance). Moreover, I don't know if the only bug that PR fixes is the visibility of the close button or if there are other issues covered by that modification.

[jordisala1991]

Any idea on how to deal with this one @greg0ire ?

[greg0ire]

Pick the lesser of the 2 bugs?

[jordisala1991]

Then, probably this bug is bigger than the other? @phansys the StackOverflow you linked covers the other bug report?

[jordisala1991]

Please edit the docs like the other PR: https://github.com/sonata-project/SonataAdminBundle/pull/5047/files#diff-e252be027e26148c11d971dc969f4be0R205

[phansys]

the StackOverflow you linked covers the other bug report?

I think not, because I don't know how to provide the button.noConflict() instance to $(selector).dialog().

In my particular use case, my app was using $(selector).button('loading'), $(selector).button('reset'), etc; and the change introduced in #5047 broke these calls.

Update at configuration.rst is done.

[jordisala1991]

We might merge this one after all

[kunicmarko20]

Merge it and wait for people to scream?

[OskarStark]

Merge it and wait for people to scream?

Yes 👍

[OskarStark]

Thank you @phansys