param defined with f:param inside h:button or h:link has precedence over the same param defined in a faces-config navigation rule

Checking MYFACES-3313 I notice that param defined with f:param inside h:button or h:link has precedence over the same param defined in a faces-config navigation rule. The curious part is the code has this comment:

// In theory the precedence order to deal with params is this:
// component parameters, navigation-case parameters, view parameters
// getBookmarkableURL deal with this details.

It seems components parameters and navigation-case parameters are handled on the link, but still it is true that getBookmarkable should deal with the remaining stuff.