[TYPO3] Bug, functional oversight or intended behaviour? Problem with HMENU.special.browse and prevnextToSection

[Peter]

When using HMENU.special.browse, items.first always refers to the first 
item in the current section and items.last always refers to the last 
item in the current section, regardless of the setting of prevnextToSection.

Consider the following:

mynav = HMENU
mynav {
   special = browse
   special.items = first|prev|next|last
   special.items.prevnextToSection = 1
   ....[menu config]...
}

In the event of the following tree:

+- 11
|
+- 12
|  +-- 201
|  +-- 202
|  +-- 203
|  +-- 204
|
+- 13
|  +-- 205
|  +-- 206
|
+- 14
|  +-- 207
|  +-- 208
|
+- 15
|  +-- 209
|  +-- 210
|  +-- 211
|  +-- 212
|
+- 16

When viewing page 203, first = 201 and last = 204 regardless of whether 
prevnextToSection is set. This leads to an inconsistent user experience, 
as the user can click "last" and then click "next" on what they thought 
was the last page.

Bug? Normal behaviour? Any workarounds?

Peter.