When using keyboard navigation, I noticed that the highlighted element is always the fourth one when no elements are selected. I did some debugging and found that updateIndex and getNextElement are called four times upon the element's creation, incrementing this.index each time and resulting in the fourth element being highlighted.

I found that this change fixes the issue, but I wonder if there'd be scenarios where this would break intended behavior: