Release 1.12.1 - #3660

the collision is faced when group-by-v2 plugin is used along w/ enabled detailView — if one expands one or more rows in a group into detailView mode & then clicks on tr.groupBy row to collapse this group, the source rows become hidden just as expected, but their detailView representations still stay visible & expanded

applied patch fixes the issue

the rigorous testing [on patch fiddle](#3598 (comment)) revealed the prefix `.bootstrap-table .table > tbody > tr.groupBy +` which has been initially applied just to follow the existing style is redundant &,  moreover, for this concrete case is harmful 'cause it brings the mess on selectors & leads to the fault of the whole patch scheme after all

as you can see https://jsfiddle.net/juliyvchirkov/jdwLp29e unprefixed rule achieves the goal as initially planned

Doco fix: Minor correction describing onCheckSome