While member summaries are ordered in lexicaographical order in JavaDoc, member details have always been ordered in source order. The rationale for this is that there may be an inherent logic in the way members are ordered in source code, an example being methods getFoo and setFoo being declared next to each other.

This was non-contentious until the arrival of the page contents sidebar, which has made the non-lexicographical order of member details more visible.

A good solution would be to provide a control/button in the header of the sidebar that allows to switch between source and lexicographical order of member details.