However, I also want to state that I think a user action to go next or previous should override "canGoPrevious()" and "canGoNext()" and allow the list to loop from first to last or last to first. If there are technical limitations at the moment--that is fine. But I think in the end the user should never be prevented from hitting next/previous.
It seems as though this is now fixed.
However, I also want to state that I think a user action to go next or previous should override "canGoPrevious()" and "canGoNext()" and allow the list to loop from first to last or last to first. If there are technical limitations at the moment--that is fine. But I think in the end the user should never be prevented from hitting next/previous.