This bug regards:

/en-US/text/scalc/01/12030200.html?System=UNIX&DbPAR=CALC&HID=modules/scalc/ui/sortoptionspage/

and the Data > Sort... options tab.

So, sorting can ignore / does ignore "boundary rows", and the page explains that those are empty row at the start or end of the sorted range. But - sorting does include empty rows that are  not on the "boundary", i.e. empty rows preceded and succeeded, possibly at a distance, by non-empty/non-excluded rows. For example, if we sort this range:

 |    A
-+---------
1|  hello
2| (empty)
3| (empty)
4| (empty)
5|  world
6| (empty)
7| (empty)

then row 6,7 are discarded, while rows 1 through 5 are included in the sort.

This is sort-of clear from the existing documentation. However - what happens if  we choose to include "boundary rows with comments", or "with images" - and add a comment to row 7 in this example? 

Option 1: Row 7 is now considered non-boundary, and thus row 6 is also a non-boundary empty row; the sort range is 1 through 7.

Option 2: Since row 6 is already a boundary row - the desire to include row 7 is not "strong" enough, and both rows 6 and 7 are excluded from the sort.

Whether you would expect option 1 or option 2 to be the case - it is not made clear what would actually happen, in the documentation. It just says:

> ### Include boundary column(s)/row(s) containing only comments
> 
> Range boundary columns (for sorting rows) or boundary rows (for sorting 
> columns) of a sorting range are not sorted by default if they are empty. Check 
> this option if boundary columns or boundary rows containing comments are also 
> to be sorted.

which does not distinguish between the two possibilities.