Why are you adding this only to those 2 layouts and not all layouts?

Can you create a tracker item on Joomlacode for this?

Actually, I would prefer an opt-in solution like was planned initially. If you look at the function you see that the default selector would be advancedSelect. But developers got lazy and just applied it to every select instead, breaking modules and templates and whatnot left and right. Doesn't matter if it's output from their component, it's applied to every select on the whole page.

That is the real issue. Changing the selector to something which allows to opt-out is only a workaround imho.

I agree, but since that is not backwards compatible, we unfortunately have to wait for 4.0. sigh We should keep a log of which snafus we want to fix in 4.0...

Imho we could do it mostly backward compatible for some views at least. I think I still have a PR somewhere with an idea for that and there are also some other PRs dealing with the same.
Also, it's not like something really breaks if chosen is not loaded.

@Bakual is this the issue? #2018

@betweenbrain Same issue, different idea to solve it, yes.
My own PR would be #1620 where the idea mainly is adding a default class to the list formfield so we don't have to edit 100+ XML files

closing in favour of #3721