If I understand it correctly, the issue is in the switch to object-based delivery of parameters into the dropdown module. Looking at the source code, around line 26 we see:
$.fn.dropdown = function(parameters) {
...
which is the point where the dropdown functionality is first announced so that you can call $('selector').dropdown();. Then aroudn line 50 we see:
settings = ( $.isPlainObject(parameters) )
? $.extend(true, {}, $.fn.dropdown.settings, parameters)
: $.extend({}, $.fn.dropdown.settings),
which is looking at the makeup of 'parameters' and deciding how to interpret it - basically if parameters is a JS object then it is used by merging into the dropdown defaults, otherwise the defaults are used alone.
Going back to your testing, in the case of:
$('.ui.dropdown').dropdown('show',{
maxSelections:2
});
you are passing in 2 arguments, and only the first is used in the $.fn.dropdown function, so the maxSelections option is ignored, as per your result.
In the case of:
$('.ui.dropdown').dropdown({
maxSelections:2
});
The parameter you have supplied is indeed a plain object, hence it has the desired result.
This is a technical explanation of what you are seeing of course, but it still leaves the question 'how would I find this in the docs?' I believe the docs have some catching up to do - I hope the FUI team get on top of that soon because the work they are doing is high quality and the docs are undermining their work, IMHO.
Also as a matter of opinion, I think the move to a JS-object parameter approach is the right course to steer. So whilst this might be a 'mind-breaking change' for anyone coming from a Semantic-UI background, it will offer a more standard approach when applied across all FUI components. I would expect to come across this change with all components over time.